| Topic Review (Newest First) |
| 01-07-2020 01:52 PM | |
| r0ach |
Quote:
Originally Posted by ashr
@qsxcv
I decided to use my G303 again and noticed immediately that it felt much sharper than the G Pro. I know you said you couldn't tell the difference but I'm just curious now why both mice feel so different to me, could it really just be the shape of the mice causing this? edit: If you want to cover all the bases, ripping off the mouse feet Logitech started installing around the sensor itself seems to consistently make them control better for me, so you can't really compare one mouse to another until you do that. |
| 10-29-2019 06:30 PM | |
| qsxcv |
tranquil: yea sorry i mean like counts registers (from which the mcu reads via spi), not the raw data. the1: i doubt it |
| 10-29-2019 08:37 AM | |
| the1freeMan | Could the reason for the 70% clock simply be stability? I plotted my g303 the other day and it gives different plots every time. Kinda like the early fw g403 and the revel too actually. |
| 10-29-2019 07:04 AM | |
| TranquilTempest |
Quote:
Originally Posted by cdcd
Does this only apply for the highest framerate mode? In practice, what would the difference between a frame rate of 15000 with the data registers being updated every other frame and a frame rate of 7500 with the data registers being updated every frame be?
Though "data registers" is ambiguous. If you're talking about the registers the MCU reads from that's one thing, but if you're talking about the registers the image data is stored or processed in, that's effectively the same thing as reducing framerate. |
| 10-29-2019 06:48 AM | |
| cdcd |
Quote:
Originally Posted by qsxcv
but for whatever reason, in the highest framerate mode, the data registers update only every other frame, so as far as mousetester plots are concerned, it appears as ~7500.
i suspect 3310 does something similar. can't be bother to check right now. |
| 10-28-2019 10:31 PM | |
| qsxcv |
Quote:
Originally Posted by qsxcv
there's some register that controls framerate?
Quote:
Originally Posted by qsxcv
clock tuning:
registers 0x3d and 0x4f control the clock frequency of the sensor in run and rest mode, respectively toggling on the msb of one of the registers (e.g. writing 0x96) causes the 3366's pin 14 to output a square wave with frequency related to the bottom 5,6,or 7 (not sure) bits of the register (see second sheet of the google doc above). the g502 adjusts the value of the register until the square wave frequency is as close to 1000hz as possible. usually the adjustment is quite coarse and the final values are off by 20hz or so. to disable the square wave toggle off the msb of whichever register had it on. changing the register's lower bits while the msb is 0 doesn't do anything. i think all the clocks in the sensor scale proportionally, and indeed 70% is close to the ratio in the title 8500/11500. semi-related but posting here for reference: strictly speaking 3389's max framerate (~15000 or so) is higher than 3360/3366's. i checked on scope attached led pin. but for whatever reason, in the highest framerate mode, the data registers update only every other frame, so as far as mousetester plots are concerned, it appears as ~7500. i suspect 3310 does something similar. can't be bother to check right now. |
| 06-19-2019 08:37 AM | |
| ashr |
@qsxcv
I decided to use my G303 again and noticed immediately that it felt much sharper than the G Pro. I know you said you couldn't tell the difference but I'm just curious now why both mice feel so different to me, could it really just be the shape of the mice causing this? |
| 06-18-2019 02:56 PM | |
| qsxcv |
more puzzles... i found that i wrote this in one of my emails in 2016: Quote:
I'm even more confused. when I load srom 0x08 on the g502 board, the framerates are all too low (by ~30%). no idea what's going on there. I took srom 0x08 from a g303, which was for sure getting normal framerates.
3 possibilities: hardware differences between different 3366s there's some register that controls framerate? srom differences + me not being careful? |
| 05-06-2019 05:43 PM | |
| IAMSTERDAM |
*** 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 |
| 05-06-2019 10:45 AM | |
| the1freeMan |
Quote:
Originally Posted by Kim Sunjun
I compiled a small python script that automatically calculates the estimated frame rate...
Quote:
Originally Posted by qsxcv
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 Did you fix the script? |
| This thread has more than 10 replies. Click here to review the whole thread. | |
| Posting Rules | |