Overclock.net › Forums › Components › Mice › Thoughts on the G203?
New Posts  All Forums:Forum Nav:

Thoughts on the G203? - Page 7

You can't "divide" a pixel. That's the problem with Morier's oversimplified presentation. You need to throw that notion out entirely, otherwise you won't be able to understand how stuff works beyond a black box conception.

What he meant when he said dividing is merely referring to taking a convenient scale for delineating counts relative to the size of the image. The scale is completely arbitrary, there is nothing special about delineating it such that it happens to coincide with a natural division of their pixels compared to delineating it to a natural division of the whole array.

Higher CPI --> more jitter, due to lower certainty. There is no magical "native" numbers in between.
Quote:
Originally Posted by daniel0731ex

You can't "divide" a pixel. That's the problem with Morier's oversimplified presentation. You need to throw that notion out entirely, otherwise you won't be able to understand how stuff works beyond a black box conception.

What he meant when he said dividing is merely referring to taking a convenient scale for delineating counts relative to the size of the image. The scale is completely arbitrary, there is nothing special about delineating it such that it happens to coincide with a natural division of their pixels compared to delineating it to a natural division of the whole array.

Higher CPI --> more jitter, due to lower certainty. There is no magical "native" numbers in between.

The scale cannot be completely arbitrary because you still have a definite two-dimensional array of pixels. No matter what you do, you cannot change the numbers of pixels in the array. Therefore, any downscaling or upscaling must be done withing the limits of the array.
It's arbitrary because the subpixel position information you get out of the correlation process outputs information that scales with the specific nature of the tracking surface (assuming you're not using outright interpolation which would eliminate native pixels as a concept entirely), not the resolution of the sensor. And you absolutely must use this subpixel position information no matter what your DPI is because otherwise you're going to have extremely bad SRAV (the sensor would lock to speeds corresponding to integer numbers of sensor pixel motions per frame).

And once you have subpixel position information there's no loss allowing it to be output to the PC.

The g203's sensor design is interesting: it seems to adjust the framerate specifically so that each frame has an integer number of motion samples, but it still has some kind of subpixel motion detection, otherwise it would have very bad SRAV at high-ish speeds where its framerate is pinned, and we know it doesn't.
Edited by wareya - 8/9/17 at 9:12am
Quote:
Originally Posted by wareya

It's arbitrary because the subpixel position information you get out of the correlation process outputs information that scales with the specific nature of the tracking surface (assuming you're not using outright interpolation which would eliminate native pixels as a concept entirely), not the resolution of the sensor. And you absolutely must use this subpixel position information no matter what your DPI is because otherwise you're going to have extremely bad SRAV (the sensor would lock to speeds corresponding to integer numbers of sensor pixel motions per frame).

And once you have subpixel position information there's no loss allowing it to be output to the PC.

The g203's sensor design is interesting: it seems to adjust the framerate specifically so that each frame has an integer number of motion samples, but it still has some kind of subpixel motion detection, otherwise it would have very bad SRAV at high-ish speeds where its framerate is pinned, and we know it doesn't.

So if you find a DPI setting that doesn't make use of the magnifying lens, that doesn't upscale or downscale anything from the pixel array, you get very low max tracking speed ?
I'm not a mouse savvy guy, as in I don't know all the technical detail however I would like to say this, Playing with the G pro on 800 DPI feels far better than 1600/2400 DPI, now you might take it as anecdotal evidence, however I actually went to the logitech support website and asking them what the native DPI for the G Pro is, and they said it's the default after clicking the reset button. So basically 800 DPI. I can play a hell lot faster and more accurate on 800 DPI compared to 1600 DPI. However I still have have suspicions that the person who replied to me on the forum is just a lazy bum(should not be likely cause its a logitech staff member), can't really for 100% verify that 800 > 1600 on the G Pro.
https://community.logitech.com/s/question/0D53100006OEJ09CAH/
Any thoughts as to whether its legit or not?
Edited by VioleDota - 8/9/17 at 10:00am
Quote:
Originally Posted by VioleDota

I'm not a mouse savvy guy, as in I don't know all the technical detail however I would like to say this, Playing with the G pro on 800 DPI feels far better than 1600/2400 DPI, now you might take it as anecdotal evidence, however I actually went to the logitech support website and asking them what the native DPI for the G Pro is, and they said it's the default after clicking the reset button. So basically 800 DPI. I can play a hell lot faster and more accurate on 800 DPI compared to 1600 DPI. However I still have have suspicions that the person who replied to me on the forum is just a lazy bum(should not be likely cause its a logitech staff member), can't really for 100% verify that 800 > 1600 on the G Pro.
https://community.logitech.com/s/question/0D53100006OEJ09CAH/
Any thoughts as to whether its legit or not?
is it possible to choose one stable led color on G203?
on reviews I can only see options with breathing / color cycling and off.
Quote:
Originally Posted by Nomei

is it possible to choose one stable led color on G203?
on reviews I can only see options with breathing / color cycling and off.

yes, ofc you can do that
Hi, I'v been using the g203 for about month now, my fav mouse yet, and I'm trying to optimize everything. One thing I read about the mercury is that you should be using it below 1600. Is that really a concern? (I use it @ 1600 now)
not really, it's just the higher the dpi you use it at, the more obvious surface compatibility problems will be. at 3200dpi you might have parts of your mousepad where it looks like you're moving two pixels at a time instead of one, even though the sensor really is operating at 3200dpi instead of 400 or 800. i use 1200dpi.
New Posts  All Forums:Forum Nav:
Return Home
Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Thoughts on the G203?