Comment by Matheus28
For shooter games, raw input is preferred. You want the same amount of mouse movement to move your camera the same amount every time.
In those type of games, you aren’t controlling a cursor, so there’s no “expected behavior”.
For shooter games, raw input is preferred. You want the same amount of mouse movement to move your camera the same amount every time.
In those type of games, you aren’t controlling a cursor, so there’s no “expected behavior”.
It's more complex than that. There's no right answer and therefore every answer is wrong :(
For more critical observers, you're right: raw input is preferred. However, most users (casuals) expect similar settings as their OS. It's probably best left up to the user to decide, but to default things to the OS legacy settings. A more advanced player will know to tune the settings while the less advanced just want to launch and go.
No. He's right. No fps gamer expects the game camera speed to "match" mouse movement speed. Raw input-> mouse DPI * in game sense = effective dpi. Everyone has their own preferred edpi. This was you can change mouse or computer or in different games, you always get consistent movement.
Everyone plays fps games. This includes people who wouldn't consider themselves "fps gamers". Users who care about mouse input will go into the settings to target the 'correct' settings for them.
For everyone else, there's the OS values.
We're not having the same argument, but I didn't clarify in my initial post properly: It's best to launch your app for the first time with the default OS settings. Let the "power users (fps gamers)" tune settings that enable raw input.
I'd argue that linear camera movement with mouse _is_ the expected behavior for FPS these days.