Halo: Reach Settings file for more precise sensitivity and higher FoV

[Southpaw]

This file allows you to adjust settings for Halo: Reach, such as sensitivity settings beyond the tens place in a decimal, such as allowing 1.65 rather than just 1.6 or 1.7. It also allows you to go beyond the default max FoV of 120 (Multiplier) up to 150. Make sure to set GameUserSettings file to "Read Only" by right-clicking it and pressing properties. Check the "Read Only" box, then apply, and you're good to go.

File path:
C:\Users\YourUsername\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings

[fortunate reee]

16 minutes ago, devil_FPS said:

This file allows you to adjust settings for Halo: Reach, such as sensitivity settings beyond the tens place in a decimal, such as allowing 1.65 rather than just 1.6 or 1.7. It also allows you to go beyond the default max FoV of 120 (Multiplier) up to 150. Make sure to set GameUserSettings file to "Read Only" by right-clicking it and pressing properties. Check the "Read Only" box, then apply, and you're good to go.

File path:
C:\Users\YourUsername\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings

how did you managed to put the same post up 3 times?

 

also dpi wizzard even mentioned that he tried doing that and that the game ignored those values either way, if they fixed that that is nice

generally following and posting your comment on the respective thread saves you some time 

 

Edited December 7, 2019 by fortunate reee

[Southpaw]

I attempted to post it, but it just kept buffering and would flat out deny the gateway, so I guess when that issue solved it self, it all of the posts that I attempted at once. Trying to delete the others.

The config editing did work for me. Not sure what DPI Wizard is referring to, or perhaps they've allowed it since that last respond.

[DPI Wizard]

2 hours ago, devil_FPS said:

I attempted to post it, but it just kept buffering and would flat out deny the gateway, so I guess when that issue solved it self, it all of the posts that I attempted at once. Trying to delete the others.

The config editing did work for me. Not sure what DPI Wizard is referring to, or perhaps they've allowed it since that last respond.

Still the same issue here. The value you enter is not read by the game. For instance if you have it to 1.6 in-game, exit and set the sensitivity in the config file to 1.312272 (which is 12345 counts for a 360) and save it, enter the game and check the 360. It is still what 1.6 would indicate. And if you change any setting in the game, like change the FOV and apply the change, you'll see that the config file sensitivity is changed to 1.300000.

[Southpaw]

I haven't found this to be the case. After setting the file to Read Only, any change I make within the game hasn't altered the GameUserSettings file. I just attempted what you stated by changing my sens from 1.485 (displayed in game settings as 1.5, of course) to 1.7 and saved the changes. I closed the game, checked the file, and it still showed 1.485. Launched the game again, and my sens was still being displayed as 1.5. Not sure why this isn't happening for you, so I'm going to stream this in a little bit and send the VOD in case you'd like to see my PoV.

[DPI Wizard]

17 minutes ago, devil_FPS said:

I haven't found this to be the case. After setting the file to Read Only, any change I make within the game hasn't altered the GameUserSettings file. I just attempted what you stated by changing my sens from 1.485 (displayed in game settings as 1.5, of course) to 1.7 and saved the changes. I closed the game, checked the file, and it still showed 1.485. Launched the game again, and my sens was still being displayed as 1.5. Not sure why this isn't happening for you, so I'm going to stream this in a little bit and send the VOD in case you'd like to see my PoV.

Try this:

• Make the config file writable.
• Start the game and set the sensitivity to 10 and apply.
• Exit the game.
• Open the config file and change the sensitivity from 10 to 0.1.
• Save and make it read-only.
• Start the game.
• Go into a game without checking the in-game settings. You now either have a really fast sensitivity (10) if the sensitivity wasn't applied from the file (it will show 0.1 in-game still), or really slow (0.1) if it was applied.
• On my system it's fast and whatever I put in the file is not applied, only visually in the menus.

[Southpaw]

I apologize for the cutting out, new mic and I haven't adjusted the noise gate threshold to compensate. You still get the gist of what I'm saying.

Edited December 7, 2019 by devil_FPS

[DPI Wizard]

7 minutes ago, devil_FPS said:

I apologize for the cutting out, new mic and I haven't adjusted the noise gate threshold to compensate. You still get the gist of what I'm saying.

Thanks for the video! Really not showing it working though, since the numbers are so close, the sensitivity difference is only 1%. Try what I wrote and see if it still works.

You need to measure exact counts with Kovaak's or something to make sure the correct sensitivity is applied. Set it up like this and it should do a perfect 360 with 1.485:

 

For 1.5 replace in/rev with 10.8.

[fortunate reee]

19 minutes ago, DPI Wizard said:

Thanks for the video! Really not showing it working though, since the numbers are so close, the sensitivity difference is only 1%. Try what I wrote and see if it still works.

You need to measure exact counts with Kovaak's or something to make sure the correct sensitivity is applied. Set it up like this and it should do a perfect 360 with 1.485:

 

For 1.5 replace in/rev with 10.8.

i just watched a  solid 9 mins of "it is this way because it is the way that it is "     would rate this movie 5/7

 

 

 

Edited December 7, 2019 by fortunate reee

[Southpaw]

29 minutes ago, fortunate reee said:

i just watched a  solid 9 mins of "it is this way because it is the way that it is "     would rate this movie 5/7

 

 

 

Just showing how it works, as I stated, it's a demonstration.

[Southpaw]

4 hours ago, DPI Wizard said:

Thanks for the video! Really not showing it working though, since the numbers are so close, the sensitivity difference is only 1%. Try what I wrote and see if it still works.

You need to measure exact counts with Kovaak's or something to make sure the correct sensitivity is applied. Set it up like this and it should do a perfect 360 with 1.485:

 

For 1.5 replace in/rev with 10.8.

I attempted this, and it appears you were correct. The sensitivity doesn't alter due to the config file, but at least I was correct about the FoV lol.

Thanks for working this out with me, I hope they allow more precise settings in the future.

Edited December 8, 2019 by devil_FPS

[Skwuruhl]

9 hours ago, DPI Wizard said:

Still the same issue here. The value you enter is not read by the game. For instance if you have it to 1.6 in-game, exit and set the sensitivity in the config file to 1.312272 (which is 12345 counts for a 360) and save it, enter the game and check the 360. It is still what 1.6 would indicate. And if you change any setting in the game, like change the FOV and apply the change, you'll see that the config file sensitivity is changed to 1.300000.

I just used cheat engine to set sensitivity to your given value and used AHK to verify it took exactly 12345 counts to do a 360. This persists between restarts but will get reverted if you change settings, just opening them doesn't do anything. This applies to any settings, even graphical options.

Be sure to use the disabled anti-cheat version if you do this.

Unfortunately FOV is stored as an integer so it can't be edited with decimals using this method. In any case the calculator could benefit from a memory editor mode for MCC (as could BL3 btw, it's also possible there)

Edited December 8, 2019 by Skwuruhl

[DPI Wizard]

6 hours ago, Skwuruhl said:

In any case the calculator could benefit from a memory editor mode for MCC (as could BL3 btw, it's also possible there)

Good point, added Memory Editor to both.

[DPI Wizard]

9 hours ago, devil_FPS said:

 but at least I was correct about the FoV lol.

Setting the FOV does work indeed, even beyond 120

It does ignore the decimals though, but that's a minor issue.

[Pyroxia]

Wow this is awesome but I'm scared about one thing. 4 years ago my friend vac banned in cs go because he used cheat engine. I dont know how can we deactivate anti-cheat in steam is it really possible?

EDIT:Ah I found how can I do.

Edited December 8, 2019 by Pyroxia

[Skwuruhl]

23 hours ago, DPI Wizard said:

Good point, added Memory Editor to both.

One thing to note with BL3: 10 sensitivity in the menus is only 1.0 in memory iirc

[DPI Wizard]

59 minutes ago, Skwuruhl said:

One thing to note with BL3: 10 sensitivity in the menus is only 1.0 in memory iirc

Aye, updated.