DPI Wizard

No, %LOCALAPPDATA% is a variable in Windows that points to a system folder. You need to literally type or copy %LOCALAPPDATA% into the address field.

It's not located in the Steam folder, it's located at %LOCALAPPDATA%\cuisine_royale\downloads\online_storage\last\cuisine_royale\venus\. You need to change the sensitivity in-game first for the values to appear in the config file.

It's already updated, does it not work for you?

I think the best might be to convert as you usually do and try to "ignore" the outside view of the scopes. The issue is probably that you react to how the world is moving outside of the scope, and it seems to move too slow, but the movement inside the scope is correct.

Ideally your ADS should be based on the hipfire through a conversion, this way you get a consistent aim regardless of the zoom of your scope. In this case yes, but you shouldn't rely on being able to match scope for scope since most games won't allow you to do this. That should indeed feel about the same, you can always try to click the underlined sensitivity value to test this sensitivity in 3D Aim Trainer, it should be exactly the same as in the game if set up correctly. That's not correct. The issue with BF3 is that it does not apply the same factor to FOV and sensitivity, so everything changes when you change FOV. And it's not the same across all aims either, so nothing really lines up. Scale is great to match how games work. Say you in Apex set all the scopes to 0.7. You can replicate this in the calculator by setting it to MDV 0% (the default scaling of Apex) and scale 70% (which is essentially what 0.7 is): https://www.mouse-sensitivity.com/?share=6f2dcab9f58fe297ce9dc864922bf64d This way you can be sure that whatever you convert to will scale exactly the same. You can experiment with it to adjust how fast or slow scopes are based on the scaling you use. The difference between this and just adjusting the Monitor Distance percentage is that this affects all aims in a linear fashion, while monitor distance will affect scopes more when the FOV difference is larger. It doesn't technically transfer the sensitivity values as the calculations are done here on this site, but the FOV and 360 distance of the aim you click and your hipfire are transferred and used in the aim trainer.

Yeah, it's probably down to the way the scopes work.

Try again now! Rogue Company has an incredibly complex sensitivity, so it was slightly broken by a recent update but should be fixed now. Thanks for reporting!

Can you post your settings? This game does have a quite special scope integration in that the scope itself is zoomed in while the outside is not. So this might affect the perceived sensitivity.

BF3 has some inconsistencies when it comes to how the scopes scale, but this should get you the best result: https://www.mouse-sensitivity.com/?share=5dd2247ee7f966f5e9e714927b47070c If you find the scopes too slow, increase the scaling to MDV 100% first to see how that feels. As for the labelling of the Warzone scopes, this is very common in games actually. Names and actual magnifications are all over the place.

I prefer 360 distance for hipfire and MDV 0% for ADS and scopes. Some games that I don't usually play are very ADS heavy though, where you basically run around ADS'ing all the time, then 360 distance might make sense for ADS too.

You are converting hipfire to ADS, and the default setting in the calculator for that is MDV 0% which keeps the same tracking speed between aims. And since the ADS has a much narrower FOV you will get a higher 360 distance. If you select 360 distance instead for ADS, you will get the same distance.

My QQ account ain't verified or whatever (with a real name and Resident identity card number), so I can't play the game. Any way to fix that?

All these are added!

New parkour shooter added! View full update

Correct!

That's because you are using 360 distance, and this does not change based on resolution for this game.

Perhaps, I don't use that myself. And Vulkan have some built in support for it I think so it might be why it's working without Vulkan here.

Ok, cause I could definitely see an issue with Raw input on in the Vulkan version, it dropped a lot of reports from the mouse. It might be that this issue also is on the regular version in certain cases, I'm not sure.

I tested this a bit now, and it seems to be an issue with only the Vulkan version. Are you using Vulkan?

Horizontal resolution affects the sensitivity in this game, so be sure to enter the resolution you play with! View full update

Can you attach or send me your config file and I'll check. Stuff like this might be hardware related though, or how you set up the macro might be too fast for the game so it misses reports. Not uncommon, but if the macro is set extremely fast these missed reports won't be an issue when using a mouse. Also send a screenshot of the kovaak's setup.