what is this whole thing about raw input going directly to the mouse and not being affected by windows setting that everyone keeps on saying? how, if not by the operating system can a mouse get its values from if its not written in the operating system on how the mouse movement is translated? it has to be written some place doesnt it? i never understood raw input... isnt there a setting in the operating system that tells the mouse movement how to be translated other than the registry settings and the windows control panel applet?

usb dll? anyone care to explain... i always wondered about that. i know quake can override windows settings with in_mouse 2, but it has to get values from some place...

Contrary to popular belief, raw input is not obtained 'directly' from the mouse in the way that you have suggested.

The game still has to ask the operating system to provide it with mouse input; it does this via the Raw Input API. The key feature of this API is that it promises not to scale, filter or otherwise modify the data it receives from the mouse - it just passes it on to the game as is. This is what is meant by 'directly'.

that was basically what i questioned, i even heard some people say that it does adress driectinput as well. i went on thinking if i can trash direct input completely from the operating system so that it has no part of the operating system at all... it seem the raw input is just another method (api) just like direct input. secondly, it was developed as a "rawer" type of input... i just wonder, whats underneath both of them, how does the operating system actually calculate mouse movement at its core...

thought if i could build a os that has the rawest form of input and cut every link in between, which is basically just designed to hold all the new features of the bunch of advanced 3rd party accessories that you can connect to your os. was thinking linux but read up on that and they got the same problem as windows... even when building your own distro you basically have to chose what option you have to go with, then there comes things like preference and what you actually in your own knowledge believes what is the most "right" implementation...

i have tried a bunch of things, in some ways those reg's that is "confirmed" to disable any trace of acceleration doesnt always result in what feels the best for you on a personal level, i think its more about preference and even if we find the optimal solution to have it like we think would be the best it might not end up as the best solution when it comes to actual performance.

The OS doesn't 'calculate' mouse movement. The mouse *measures* the movement, and then the OS asks for the results of these measurements at regaular intervals (polling rate). The raw input method is the rawest input, since it doesn't manipulate these measurements (counts), it just passes each sample to each application that is requesting raw input. The OS doesn't attempt to interpret or convert the measurements in any way. With other APIs, such as directinput, there is a certain amount of re-interpretation of the raw data, although this applies more to keyboard and gamepad input than mouse input.

The registry entries only apply to the desktop pointer scaling, it doesn't apply to raw input.

The whole point of an OS is that the applications *don't* access devices directly, otherwise every application would have to know how to access all possible devices that are ever created. The OS provides a standard by which applications can ask for input (via an API), and then the OS deals with device-specific interfacing, the details of which are provided by the device manufacturer via a driver, which is also standardised.

ok, so the mouse calculates the movements and sends it off to the api? in this case rawinput...

the mouse has a certain sensitivity value to it to start with without being connected to the interface... if you change the sensitivity in your windows mouse applet then you are changing the properties of it system wide or per application depending on which api its running and its no longer running on the properties of the mouse, that is what i mean with os calculations...

when you boot your system some part of the operating system tells it to behave like that, you dont actually change the values in your mouse... when you lower the sensitivity per application you cut even with odd numbers and are no longer running on the properties of the mouse... right?

maybe not a problem... but are there any api's or input methods that doesnt recalculate mouse output this way and leaves the mouse as it is? 1to1.... how do i find the sensitivity of the mouse to start with?

hi. seems you know what are you talking.
I have geforece m540gt in notebook. If I set settings in nvidia control panel @ adjust image settings , to QUALITY I get a lot lower sense in Quakelive. What can effect it? I am a bit lazy to check all settings one by one, but if you won't know, I will try to do that some evening. With ballanced and performance, sense seems like it should be. maybe its some antialiasng settings. I use it , to get nice grafix with 640x480 in quakelive.