3366 mice have different framerates: maximums are either ~8500 or ~11500 - Page 5 - Overclock.net - An Overclocking Community

Forum Jump: 

3366 mice have different framerates: maximums are either ~8500 or ~11500

Reply
 
Thread Tools
post #41 of 52 (permalink) Old 03-04-2019, 02:52 AM
Not a Linux Lobbyist
 
the1freeMan's Avatar
 
Join Date: Jan 2013
Posts: 1,137
Rep: 41 (Unique: 32)
Uuuuh.. what frame rate is this? @qsxcv

[sorry for "attached thumbnails" got tired of reverse engineering the ocn editor]

btw same g403, different plots with reboots an unplugging (last one was on win7, others on 10). Firmware 108.1.12 . Newer versions state "clock tuning optimizations"..
Attached Thumbnails
Click image for larger version

Name:	g403-random timings2.png
Views:	34
Size:	94.7 KB
ID:	256982  

Click image for larger version

Name:	g403-random timings1.png
Views:	17
Size:	96.5 KB
ID:	256984  

Click image for larger version

Name:	g403-random timings.png
Views:	20
Size:	108.8 KB
ID:	256986  

Click image for larger version

Name:	g403-proper-timing.png
Views:	22
Size:	92.4 KB
ID:	256988  


"a bad joint can't be that bad right?" -q
the1freeMan is offline  
Sponsored Links
Advertisement
 
post #42 of 52 (permalink) Old 03-15-2019, 09:45 PM - Thread Starter
lololol
 
qsxcv's Avatar
 
Join Date: Feb 2014
Posts: 4,243
Rep: 365 (Unique: 152)
[email protected] signature...

first one can't tell since framerate in the fast part is a multiple of 1000. i'll guess 9000 based on the below...
2nd one: around 9040
3rd: around 9060
4th: around 9250

the reboot shouldn't affect anything. basically the framerate is completely dependent on the sensor's clock speed.
it might just be the mouse warming up or something... the clock speed in pixart sensors is not very stable

Quote: Originally Posted by Kommando Kodiak View Post
Lets get the Hero sensors analyzed too.

The other day I was wondering what the crystal oscillator was for on the GPRO pcb whether it was for the sensor or the rgb leds -- could that be limiting the voltage to the sensor thus maintaining operating frequency that peaks at 8k frames?
no i'm almost certain it's srom related. or some register that i never noticed. or literally different hardware.

the crystal is for the mcu

the sensor clock speed is set by some internal (i.e. inside the sensor) reference. for pixart/avago sensors, this isn't very stable and it drifts depending on temperature and whatever all the time by several percent. see the1freeman's framerates i listed above as an example.

too busy to check forums as regularly
pm me if i forget to respond

Last edited by qsxcv; 03-15-2019 at 09:49 PM.
qsxcv is offline  
post #43 of 52 (permalink) Old 03-16-2019, 09:14 PM
New to Overclock.net
 
WindInSummer's Avatar
 
Join Date: Apr 2014
Posts: 34
Rep: 1 (Unique: 1)
Quote: Originally Posted by qsxcv View Post
also:
i dare anyone to try to find a post before this thread was created, claiming different tracking feel between mice in those two categories (e.g. between g pro and g303)
i certainly cannot tell a difference but maybe someone else was able to in the past
Shape is so different, but I think I felt a difference between the G509 and G403. Both feeling great though, but and maybe it is unique but comparably the G509 had more of that soft glassy smooth responsive sublime feeling, of the IME 3.0. Using them in that order, the G509 for a short period. But the G403 wasn't far behind. And all of that stuff may not even relate to framerate MLT-04 had one dpi etc., I have always just thought the framerate may have been one reason the IME 3.0 felt so unique.
WindInSummer is offline  
Sponsored Links
Advertisement
 
post #44 of 52 (permalink) Old 04-01-2019, 12:13 AM
http://kuaa.net
 
Join Date: Mar 2019
Posts: 2
Rep: 1 (Unique: 1)
Quote: Originally Posted by Axaion View Post
Pro intellimouse seems much lower than IME 3.0, even with the 3.0 at 125hz, it ticked to 100 counts, where the pro at 450 DPI ticked to 80

Regardless, heres the Pro at 16k dpi, seems to be effective 13.4k DPI however.
I tried qsxcv's calculation by myself.
Your data is showing about 6200-6300 fps.
Kim Sunjun is offline  
post #45 of 52 (permalink) Old 04-01-2019, 06:13 AM
►¿¿¿
 
Axaion's Avatar
 
Join Date: Nov 2011
Location: Denmark
Posts: 2,036
Rep: 49 (Unique: 42)
So about half of what they claim, shocking.

-.-
(14 items)
CPU
3700x
Motherboard
Crosshair VII Hero
GPU
MSi GTX 970 Gaming 4G
RAM
G.skill FlareX 3200Mhz CL14
Hard Drive
SX8200 Pro 1TB +30 TB Spinning Rust
Power Supply
Seasonic SSR-1000TR
Cooling
Dark Rock 4 Pro
Case
Fractal R6 (Dont buy, terrible HDD trays)
Operating System
Win 10 Pro x64
Monitor
Viewsonic VX2268wm
Keyboard
SteelKeys 6G
Mouse
Pro Intellimouse
Mousepad
QcK Heavy/Artisan Zero XL FX
Audio
Craptive AE-5
▲ hide details ▲
Axaion is offline  
post #46 of 52 (permalink) Old 04-01-2019, 01:59 PM
http://kuaa.net
 
Join Date: Mar 2019
Posts: 2
Rep: 1 (Unique: 1)
I compiled a small python script that automatically calculates the estimated frame rate. I hope it'll be helping someone who's interested in this topic.
Download the Script.zip and extract. It also includes some sample MouseTester log files (G502 at different CPI levels)

You may use Jupyter notebook (Script_notebook.ipynb) or the python script (Calculate_framerate.py).
It runs on python 3.6+. Pandas, Numpy, Matplotlib are required.

Do one fast swing to the right horizontally on MouseTest (I used v1.5.3), save it to a log, and feed it to the script.

-------------
Usage:
$ python Calculate_framerate.py [MouseTester log file].csv
-------------
Results:
Cutting the data xCount > 959.3333333333334
72 datapoints are collected
Calculated ratio between high/low 1.0909417312711738
62 datapoints are measured in 61.02122614120299
One report consists of 11 or 12 frames
726 frames are processed in 61.02122614120299
USB report rate (Hz) = 1000.0
The best estimated FPS = 11705

[Graph: G502_12000.png]

-------------
The program first detects the peak in xCount movement and does thresholding at 2/3 of the max value.
It then splits the datapoints into high/low set (the upper graph).
It calculates the ratio between high and low set, and matches it with the possible sampling counts ratio.
Finally, it estimates the FPS.

You can visually verify the match between low/high set (the lower graph). The low set (red) is multiplied by the calculated "ratio". The two sets should be perfectly overlapped.

==> All of the procedure follows qsxcv's original post, but it's just automated.

================================

I tested the program with two G502s I have. Here are the estimated framerates.

G502 Proteus Core:
[email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

G502 Proteus Spectrum:
[email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

Check the attached pdfs for the details.
Attached Thumbnails
Click image for larger version

Name:	G502_12000.png
Views:	4
Size:	34.9 KB
ID:	262734  

Attached Files
File Type: zip Script.zip (236.7 KB, 16 views)
File Type: pdf G502_proteus_spectrum.pdf (216.3 KB, 7 views)
File Type: pdf G502_proteus_core.pdf (212.5 KB, 5 views)

Last edited by Kim Sunjun; 04-02-2019 at 06:03 AM.
Kim Sunjun is offline  
post #47 of 52 (permalink) Old 04-04-2019, 03:46 AM - Thread Starter
lololol
 
qsxcv's Avatar
 
Join Date: Feb 2014
Posts: 4,243
Rep: 365 (Unique: 152)
nice, i've had that in mind for a long time but never got around to making it
actually what i had in mind was to remake mousetester and do a lot of things automatically, but life gets in the way

btw if you want to test your script more, a long time ago i made a mock data generator that outputs mousetester-type csv: https://www.overclock.net/forum/24401063-post387.html
(lol this was like a month after i first used python)

Quote: Originally Posted by Kim Sunjun View Post
I tried qsxcv's calculation by myself.
Your data is showing about 6200-6300 fps.
no it's 7200-7300

see attached images for scaling the red dots by 7/6 vs by 8/7

(i'm surprised... isn't ime pro 3389? my deathadder elite.... oh shieeeeeet it's also this low: https://www.overclock.net/forum/375-...-info-etc.html can't believe i didnt notice when i made those plots)
Attached Thumbnails
Click image for larger version

Name:	76.png
Views:	16
Size:	53.0 KB
ID:	263186  

Click image for larger version

Name:	87.png
Views:	15
Size:	52.9 KB
ID:	263188  


too busy to check forums as regularly
pm me if i forget to respond

Last edited by qsxcv; 04-04-2019 at 03:54 AM.
qsxcv is offline  
post #48 of 52 (permalink) Old 04-05-2019, 02:03 AM
►¿¿¿
 
Axaion's Avatar
 
Join Date: Nov 2011
Location: Denmark
Posts: 2,036
Rep: 49 (Unique: 42)
Yep, Pro IME is 3389, its also 'advertised' as 12000 FPS

With my luck, mine could be faulty however, so if someone else would do a swipey swipe swipe, thatd be great!

iirc i was swiping it around 5.5m/s according to mousetester in my picture

-.-
(14 items)
CPU
3700x
Motherboard
Crosshair VII Hero
GPU
MSi GTX 970 Gaming 4G
RAM
G.skill FlareX 3200Mhz CL14
Hard Drive
SX8200 Pro 1TB +30 TB Spinning Rust
Power Supply
Seasonic SSR-1000TR
Cooling
Dark Rock 4 Pro
Case
Fractal R6 (Dont buy, terrible HDD trays)
Operating System
Win 10 Pro x64
Monitor
Viewsonic VX2268wm
Keyboard
SteelKeys 6G
Mouse
Pro Intellimouse
Mousepad
QcK Heavy/Artisan Zero XL FX
Audio
Craptive AE-5
▲ hide details ▲
Axaion is offline  
post #49 of 52 (permalink) Old 05-06-2019, 09:45 AM
Not a Linux Lobbyist
 
the1freeMan's Avatar
 
Join Date: Jan 2013
Posts: 1,137
Rep: 41 (Unique: 32)
Quote: Originally Posted by Kim Sunjun View Post
I compiled a small python script that automatically calculates the estimated frame rate...
Quote: Originally Posted by qsxcv View Post
nice, i've had that in mind for a long time but never got around to making it
actually what i had in mind was to remake mousetester and do a lot of things automatically, but life gets in the way

btw if you want to test your script more, a long time ago i made a mock data generator that outputs mousetester-type csv: https://www.overclock.net/forum/24401063-post387.html
(lol this was like a month after i first used python)



no it's 7200-7300
@Kim Sunjun

Did you fix the script?

"a bad joint can't be that bad right?" -q
the1freeMan is offline  
post #50 of 52 (permalink) Old 05-06-2019, 04:43 PM
New to Overclock.net
 
IAMSTERDAM's Avatar
 
Join Date: Aug 2013
Posts: 88
Rep: 4 (Unique: 4)
*** why 3389 is so bad on IE PRO 7200-7300 fps?
i have new ie pro and dm1 rpo s - dm1 - feels faster and smoother and more responsiveness.. is that fps diffrences?
use 400dpi on both mice...
i have old IE 3.0 6000fps and 9000fps
9000fps feels very nice
qsxcv - logitech mouses have the best fps sensors?
interesting results Glorious Odin but 3360.. predicted

Last edited by IAMSTERDAM; 05-07-2019 at 08:27 AM.
IAMSTERDAM is offline  
Reply

Quick Reply
Message:
Options

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off