Ever since Halo 2 came out on MCC on Steam, every single time I launch the game, my controls get reset. I reset to default and then change it but it resets when I launch the game. I tried deleting the GameUserSettings.ini file and it somehow made it worse by making me need to redo ALL the controls for all the games, not just the one I was playing. I verify the integrity of the game files and it still happens. Nothing I do fixes it and itās becoming really damn annoying to do every single time I launch the game for any reason. Is there anything else I can do to fix this?
Iām not 100% on this but it seems to happen to me whenever I dare to bind the Halo 3 Forge controls - next time I run the game, itāll be back to all Halo 3 default keys (and reset my gamepad settings too), not just the Forge keys. We need to submit a support ticket about this. I tried doing that in the Halo 3 Flight but then it magically stopped resetting my controls after I wrote up a whole page about itā¦ and then after I closed that submission page out of confusion, it happened again.
I guess try binding only what you need to play campaign and matchmaking and avoid touching Forge or Theater where possible, see if that improves things any.
EDIT: I FIGURED IT OUT.
Every single time, if I bind āCreate Object / Object Propertiesā to āMouse 2ā, the game I set that for will reset entirely.
See if you experience the same: Change your gamepad scheme to a non-default setting (this is to see very quickly if a reset has occurred, it doesnāt matter if you use one), then go set your āCreate Object / Object Propertiesā key to āMouse 2ā. Save that and close the game. Open it back up, see if the game you did that for is back at the default gamepad (and everything else) settings.
Iāll be submitting a ticket about this. You should do the same if it turns out to be the same for you.
> 2533274814512101;2:
> I guess try binding only what you need to play campaign and matchmaking and avoid touching Forge or Theater where possible, see if that improves things any.
I tried only doing the main controls and leaving forge and it didnāt work but when I changed a forge control, it stayed to what I changed it to but only forge
> 2533274879295224;3:
> I tried only doing the main controls and leaving forge and it didnāt work but when I changed a forge control, it stayed to what I changed it to but only forge
Huh. Iām guessing thereās one specific command the game isnāt liking somewhere along the line (for me it was setting a specific Forge command to Mouse 2). I guess the only thing left you can do is, one-by-one, change settings and relaunch the game until you figure out which one is causing it to reset. Man, thatās awful, and Iām sorry youāre dealing with this.
Iām having the same issue and itās absolutely infuriating. I think it may have something to do with the game occasionally registering your keybind attempts for menu navigation instead of assigning it to a setting, as the X key is also used to reset keybinds to default.
Oddly enough, on each restart all my settings are reset except for Halo: CEās keybinds. It also clears all my gamepad settings (except for Halo: CE) as well as global mouse and keyboard settings (such as crouch behavior and mouse sensitivity). Iām still attempting workarounds as I refuse to work with the ludicrous default KB+M controls.
Edit: As stated before me it is, without a doubt, a result of reassigning Forgeās keybindings. Which key exactly, if any specifically, Iām not sure of. Guess Iāll just be Forging with an Xbox One controller until a bug fix is released.
Addendum: I am able to reproduce the bug by reassigning Create Object / Object Properties to āEā, however this may be specific to my case as this repro only occurs when other keybinds have already been changed. The easiest workaround for me is to change controls as I see fit but leave that particular option alone.
Thanks for posting this - Iāve been having the same infuriating problem. But it has nothing to do with setting the āForgeā controls (at least for me). After going through the painstaking task of rebinding one key at a time and restarting the game I figured out that binding ANYTHING to the X keyboard button seems to cause the problem. I wanted to use X for āSwitch Grenadeā but itās not worth the trouble of having all the key bindings reset every time I launch the game.
Microsoft needs to get their sh** together. This is such a blatant issue that should have come up in basic quality control testing.
> 2533274989480812;6:
> Thanks for posting this - Iāve been having the same infuriating problem. But it has nothing to do with setting the āForgeā controls (at least for me). After going through the painstaking task of rebinding one key at a time and restarting the game I figured out that binding ANYTHING to the X keyboard button seems to cause the problem. I wanted to use X for āSwitch Grenadeā but itās not worth the trouble of having all the key bindings reset every time I launch the game.
>
> Microsoft needs to get their sh** together. This is such a blatant issue that should have come up in basic quality control testing.
Itās curious - I have X set to crouch and it works fine. Apparently itās a different command, different key, per person. Every unique setup seems to have at least one specific thing it hates.
Yāall need to submit tickets on the support section about this, each with your own specific reset triggers. This Iāve already done with mine, including a video of it in action per-game.
I lost a whole night of gaming fighting not Covenant and the Flood, but the menu 
. That is one serious bug that should have been fixed by now. In Steam I did verify integrity of files. Then I reset the defaults one game at a time. I could only get it back to normal by religiously doing it in this order and
it took multiple tries. Forget changing the key binds! Just make some custom Razor and Logitech profiles I say.