-1 is for WMO only.

in_mouse does not exhist anymore

seta in_mouseMode "win32(Raw)"
always Raw. no need for other setting.

that funnender site works well, just make sure your entering all the shit you need to..
there is an 'in-game resolution width' field.

ffs

yes it does?

Don't set that.
Actually I'm not even sure if you can (not on PC tto check atm), and if it changes then it wouldn't do anything. That's used to report what it has been set to, like r_lastvalidrenderer.

Set in_mouse, then call in_restart, then In_mousemode will read as the current mode.

wait so if in_mousemode is raw no matter what i change in_mouse to it will always be -1?

The g400s usb plug can malfunction just like the g400 did, that might be your problem. Just search/look on http://forums.logitech.com - also if your running windows 8/10 you are probably not actually using 500/1000 poll rate - mouserate.exe

the problem may come from low DPI and high display resolution. If your mouse has too low DPI it may produce mouse movement skips depending on your display resolution.

Anyway there is a formula that may suggest minimal required DPI:

resolution width * pi * 2.54 / (Turn per 360 in cm * tan(FOV/2)) = minimum DPI.

You didn't write your m_yaw/m_pitch so I've used default 0.022 and assumption that you have 26cm distance per 360 turn with cl_mouseaccel disabled to calculate minimum mouse DPI setting:
(1920*3.14*2.54)/(26*tan(103*3.14/360))=468

So it comes that 400 is too low for 1920x1080. You need to try higher DPI at first.

On the desktop, sure.

Ingame mousemovements don't translate to a change of the pointer location on a 2d grid though, but to a change in view angle in a 3d environment.
You're not skipping pixels ingame.

On in_mouse -1 your effected by your OS.

Windows 8 especially had DPI scaling issue that M's eventually offered a fix for.
The ' MarkC mouse fix' registry settings should only effect in_mouse -1 and yoill notice they have specific versions for resolution.

So any OS change, mouse driver change, and resolution change is most likely going to mess you right up, its one of the main reasons everyone recommends you swap to raw input, work out the match for your old cm/360, if its not perfect tweak it a bit or just adapt, and them be happy it won't change unless your mouse CPI changes

Unless you are on Logitech. Some Logitech drivers seem to mess everyone up with unexpected CPI changes or something.

Whats dpi scaling bug in win8 in a few words?

https://support.microsoft.com/en-us/kb/2907016

The MarkC fix seems to effect in_mouse "2" as well. I'm not sure why, because from my understanding in_mouse "2" is supposed to be raw input (the mouse talking directly to the game without any windows interference) but there's definitely a noticeable difference for me when I apply the mouse fix and take it off with raw input selected. Without the fix enabled, the mouse movement feels a little loose. With it enabled, it feels more rigid.

Which is what you would expect using the mouse fix, but not while using in_mouse "2". It's not placebo either as I have repeatedly tested this and it certainly changes the feel of the mouse movement. I'm just not sure why...

Especially considering you have to take the time to reboot, or at least log out/in for the fix to take effect at all, and that you are likely expecting an effect, and that as it should actually effect your movement within windows, you will be changing how you're moving your mouse as you navigate your OS, so you'll be in a different mindset/used to slightly different movement as you load up the game.

Until someone does double blind tests with a large number of users, or at the least very carefully accurately measures cm/360 both horizontally and vertically and acceleration with a bunch of different mice (as I'm not beyond thinking some just don't do raw properly somehow, after all some don't seem to work in raw mode at all), and finally but as a minor consideration in the circumstances, I can't detect any real change myself - I'm going to consider this placebo.

Maybe I am missing something here, but I am reading that you can't get same feeling, it's not surprising when you consider the changes:

dpi
mouse hz
screen hz
resolution
mouse weight
sensor position
lift off distance

My advice is to set in_mouse 2, put settings close to what you have calculated (but measure dpi of g400s because my old one was 415 and will make some difference to accel and feel), use that as a baseline and adjust till it feels 'ok', then stick with it for a week and adjust to it. I think the ec2 evo at 450dpi setting had some lag on movement, g400s will not have this, it can account for a lot of what feels wrong imo.

gl with it ))

It's fair to say you simply can't have the same feeling as before with this many changes. Will the changes be worth it in the end? Time will tell.

What about r_lodbias? i have it set to 0 since i had raphas config and have most of his settings. I switched to in_mouse 2 lately. Thank you for leting me know about the g400s true dpi vs advertised. I tried to check but it wasnt a reliable check i will double check though.


I was hitting about 480 with my zowie on wood so that might help in calculating for sure

so should i change lodbias? to what? i have keel

lodbias changes the lod (level of detail) of models.
-2 = always highest detail
2 = always lowest detail
0 = should pick detail depending on how far away the model is (lower detail geometry if they're further away)

that's all, not sure why you're bringing it up in a mouse thread really.

edit: oh, though it seems to default to -2 now, that may be another reason why people on old hardware are having a few more FPS issues now.