War Thunder

On 8/15/2017 at 2:35 PM, MightyHunteR said:

The file is not in my folder 

They moved things around a bit, I've updated the path and filename and added in-game calculations as well

10 hours ago, JustCauseWhyNot said:

The sensitivity doesn't seem right. I am using it on linux, but using aimlabs mouse sens converter and setting the sens to mouseSens:r=0.026 when it gives 1.026 as sens feels much better. If I set 1.026 it's nutty fast, but 0.026 feel right.

What exactly is your conversion? Can you link it using the purple share button?

And I just checked now to verify, and the calculations are correct for Windows at least. Note that the calculation is for 3rd person view only. When you zoom in to aim, the sensitivity has so much negative acceleration due to the turning speed limitation that calculating the sensitivity for it will not work.

10 hours ago, JustCauseWhyNot said:

 Also do you know what mouse smoothing does?

Smoothing will artificially smooth out the mouse movement over several frames, causing both lag and inaccuracy.

47 minutes ago, JustCauseWhyNot said:

I'm using aimlabs site to set `mouseSens:r=*` I test it in game by using ruler to measure how many cm's moved to the in game compass that has 0-360 indicators. But I'm coming back because using either 1.14 or 0.14 for setting the sens to 45cm/360 is also off.

Aimlabs (and pretty much all the other calculators) have just copied the work I have done. 1.14 is the in-game sensitivity, which is impossible to set to that precision. I see that it doesn't go lower than 5% now, so I've updated that.

45 minutes ago, JustCauseWhyNot said:

If I use this formula, and set the sens to 0.02281 on a native linux client. If I move my mouse from the bottom of my 50cm mousepad to keep it straight the ing game compass starts at N and ends around 315. Where's if I set 0.026 that results closer to 45cm, and pretty close to 50cm.

It might very well be that the Linux client is different, I have only verified the calculations for the Windows client.

2 minutes ago, JustCauseWhyNot said:

You can't set it to 1.14 in the control panel, but if converted to whatever the `mouseSens:r=` value is then it'll accept it.

Yeah, it's directly converted the config file value, but with better precision.

2 minutes ago, JustCauseWhyNot said:

Should I open a bug report to the devs, or is there a way to figure out the difference?

Hard to say, it might be because of optimization issues and negative acceleration or something, or it might just be that it actually is different. This game is quite hard to accurately measure because the aim tilts upwards more and more the faster you move.

2 minutes ago, JustCauseWhyNot said:

What do you mean? Does setting values in in between ex: 0.02 and 0.03 actually work? It seems to have in my testing.

It does indeed work, I've updated this along with the minimum in-game value now. So the config value is now much more accurate.

2 minutes ago, JustCauseWhyNot said:

Also what do you mean by this? What is that, and I'm assuming it's something that plagues warthunder.

Negative acceleration basically means that the game misses/drops packets from the mouse, resulting in a movement shorter than it should me. Settings such as DPI and polling rate might also affect this.

1 minute ago, JustCauseWhyNot said:

Would higher dpi/polling rate cause more or less drops?

More, a lot of games struggle especially with polling rates over 1000 Hz, some even struggle with 500 Hz.

I just tested War Thunder on PC now though, and there's no issue with up to 1000 Hz. I did not test above that.

2 minutes ago, JustCauseWhyNot said:

That's good to know. I don't have a higher polling rate mouse atm. Thank you, and sorry you had to install wt lol.

I've got about 1200 games installed, it was already patched and ready to launch 

2 minutes ago, JustCauseWhyNot said:

Wow. How much storage does it take?

About 20-25 TB.