Smash-Crunch

What is the difference between the Aim Look and Aim Gun sensitivity in the calculator? I only see one option for horizontal or vertical Aim sensitivity in the options.

For Steam You can hit ~ to bring up the console in-game and use m_sensitivity 2.026499 to set it precisely for now. Obviously use your value instead of mine. edit: I don't know why I wasn't working before, but adding "+m_sensitivity 2.026499" with the quotes to the Steam launch options seems to work for me now.

So basically no one on PC will be using the default FOV that matches what console players see. So for (almost) every situation we should be using Relative at 0%? I mean, I don't know anyone who would be on this website that chooses to use the same FOV as what consoles are restricted to.

If Legacy and Relative with 0 Monitor Distance Coefficient are supposed to be the same, how come the calculator gives different values?

I found the Notepad++ Hex editor to be very buggy. It was adding an extra 00 byte between the 4 byte long chunks of the sensitivity values. It would also change the values I typed in after saving. For example E1 10 87 3F would change to 3F 10 3F 3F for no reason. If anyone reads this, I recommend using a different hex editor. There are some in-browser ones you can find on google that work well enough for this task. To re-iterate the steps: 1. Get your hex value from the sensitivity calculator 2. Open up the file with a hex editor 3. At the bottom of the file below the bit that says <..=..> there will be identical 4 byte long chunks separated by 42 05 4. Replace those 4 byte chunks with the hex value from the calculator. 5. Don't open up the "Look" options in the in-game settings, it might revert back. I recommend putting the in-game setting to max before doing all this. That way if you do it right the change will be immediately noticeable. It will also help when looking for the bytes that need to be edited because they will be 00 00 F0 41 at max value.

I don't understand why games like this have such limited options for sensitivity. The default 20 at 800 dpi is stupid fast. Anyone coming to this game with a background in CSGO is going to have a range from 1-5 to get close to their usual sensitivity (which is normally in the 30cm+ per 360 degrees range). This leaves you with choices 20 through 100 to have an even higher sensitivity than before. You would need to play at 100 dpi for 100 in-game sens to even be humanly usable. What are these developers thinking?

Name: ControlWebsite: https://www.epicgames.com/store/en-US/product/control/homeStatus: ReleaseRelease date: August 27, 2019Availability: Purchase The game has a slider from 0 to 100. I can't seem to find a config file, at least one that is in plain-text. For what it's worth, 10/100 seems to be just a tad too slow to match my 1.56 800 dpi 1920x1080 106.56 fov CSGO setting. 10/100 gives me 15cm/180 9/10 gives me 17 cm/180 and I'm aiming for 16cm/180 lol.

So is Viewspeed conversion not really relevant until the game gives more options to choose 2x, 3x, etc scope sensitivity? I'm trying to convert from my standard hand-measured 32cm/360 in most games and I don't think I quite understand Viewspeed and why it was getting such rave reviews when DNAMTE first introduced it.