Unable to change any Settings (->key binding bug?!)

[gr0w]

Anyone else having the bug that you cannot make any changes to settings (graphics, audio, controls, ...) whatsoever? Whenever I make a change and want to go out of the menu I get a popup telling me that at least one action is not bound to a key.
Plottwist: All actions are bound to keys, all of them. I re-assigned all keys, tried completely different keys, for BOTH CE & Reach. Setting everything back to standard is also not working.

[Butterhai]

yes, audio is all over the place for me or outright not working and when i try to change the settings i cannot save any changes because of this unbound bs

and to any whiners out there complaining about those who experience issues, go eat a coorporate dique and stfu

[UniOfLife87]

yeah, I have the same key binding problem

[UniOfLife87]

I found the issue, in the menu where you can enter the keys you also need to select the game. however if you change bindings it changes in all games I guess so you need to make sure all keys are used in all your games

[gr0w]

Originally posted by Préd@toR1987:

I found the issue, in the menu where you can enter the keys you also need to select the game. however if you change bindings it changes in all games I guess so you need to make sure all keys are used in all your games

As I wrote in my OP, I paid attention to this. But still, nothing works.
What did work was to delete the %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
Next time the game booted up all settings were resetted, and I could make changes. But once I changed the mouse sensitivity the same error occured -_-

I guess I will wait for a patch?

[Potates]

I've been having the same issue, this is gonna be MCC on Xbox One all over again. 343 realy needs to pull it's ♥♥♥♥ together.

[HaggardMelon]

Not sure if this will help everyone, but it worked for me. Set the bindings on Halo 2 the way you want them. Then go into the bindings for Reach, make sure the binding for "Fast Forward" towards the bottom of the list isn't null. I randomly saw that and assigned it a key. Now I'm good to go. Hope this helps!

[Chris Chameleon]

Originally posted by jwuori1635:

Not sure if this will help everyone, but it worked for me. Set the bindings on Halo 2 the way you want them. Then go into the bindings for Reach, make sure the binding for "Fast Forward" towards the bottom of the list isn't null. I randomly saw that and assigned it a key. Now I'm good to go. Hope this helps!

Thank you, this worked for me. This was driving me nuts, now I can play Halo 2 how it was meant to played, Original Graphics!

[Spinaap]

This really helped, weird fluke, but a simple solution :-). Thanks!!!

[stonewales]

having the same problem with keys but just with halo 4

[DACV]

Originally posted by gr0w:

Originally posted by Préd@toR1987:

I found the issue, in the menu where you can enter the keys you also need to select the game. however if you change bindings it changes in all games I guess so you need to make sure all keys are used in all your games

As I wrote in my OP, I paid attention to this. But still, nothing works.
What did work was to delete the %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
Next time the game booted up all settings were resetted, and I could make changes. But once I changed the mouse sensitivity the same error occured -_-

I guess I will wait for a patch?

I tried that too but as soon as i change a key in odst keyboard settings it gives me the keyboard error but only in odst.
every other game has all keys bound including odst and it still says odst has a key unbound.
frustrating especially since i play all games previous to odst with no problems

[Ryloon]

Originally posted by DACV:

Originally posted by gr0w:

As I wrote in my OP, I paid attention to this. But still, nothing works.
What did work was to delete the %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
Next time the game booted up all settings were resetted, and I could make changes. But once I changed the mouse sensitivity the same error occured -_-

I guess I will wait for a patch?

I tried that too but as soon as i change a key in odst keyboard settings it gives me the keyboard error but only in odst.
every other game has all keys bound including odst and it still says odst has a key unbound.
frustrating especially since i play all games previous to odst with no problems

im having the same exact issue with only odst being a problem even though all binds are accounted for and no conflicts.

[PeachCheekz]

I had the same problem. It would let me changed my resolution. How I fixed it is I went into keyboard bindings and there were some missing for all games. Just bind the keys and you’re good to go. The ones that need binding glow red.

[Nasty]

I hope this helps but I was playing odst on MCC pc and had the same bug. I noticed that it only happens when i bind the "zoom in" and "zoom out" actions with the up and down arrow keys. Not sure if the game doesn't like the arrow keys bound to any actions in general, or if it is from those specific actions. but i fixed the bug for myself by binding those specific actions to other keys.

[Tinkicker]

From what I've seen and tried myself, the problem revolves around the up and down arrow keys. Doesn't matter what you assign to them, there will be an error. Reassigning directions to the arrow keys is common for left-handed people (myself included). Why ODST doesn't like changes to the up/down arrow keys is a mystery, but I've gotten around it by mapping my directions to the 8/4/5/6 number keys on the right-hand numeric keypad. This may seem odd, but the five key (at least on my number pad) has a small nub on it that helps me find it in the dark, kind of like the F and J keys.

A couple of problems with this:
1) Had gotten used to night vision on number pad 4 so relocated it to the N key...having to retrain muscle memory.
2) If you're playing on a keyboard with no number pad, you either need to get a full size keyboard or a USB number pad. These pads are cheap and all over Amazon/eBay. I have one I bought a couple years ago for number entry on a smallish laptop, and I verified that it works fine for this purpose. I think mine was $7-$9 on eBay.

I'm really disappointed Microsoft hasn't already patched this glaring issue. It has occurred on every keyboard I've tried on my desktop and also on my Acer E15-575G laptop, so I know it's not really a hardware problem.

I hope this helps someone. Gotta' go kill some Covenant now.

[pim]

Originally posted by Tinkicker:

From what I've seen and tried myself, the problem revolves around the up and down arrow keys. Doesn't matter what you assign to them, there will be an error. Reassigning directions to the arrow keys is common for left-handed people (myself included). Why ODST doesn't like changes to the up/down arrow keys is a mystery, but I've gotten around it by mapping my directions to the 8/4/5/6 number keys on the right-hand numeric keypad. This may seem odd, but the five key (at least on my number pad) has a small nub on it that helps me find it in the dark, kind of like the F and J keys.

A couple of problems with this:
1) Had gotten used to night vision on number pad 4 so relocated it to the N key...having to retrain muscle memory.
2) If you're playing on a keyboard with no number pad, you either need to get a full size keyboard or a USB number pad. These pads are cheap and all over Amazon/eBay. I have one I bought a couple years ago for number entry on a smallish laptop, and I verified that it works fine for this purpose. I think mine was $7-$9 on eBay.

I'm really disappointed Microsoft hasn't already patched this glaring issue. It has occurred on every keyboard I've tried on my desktop and also on my Acer E15-575G laptop, so I know it's not really a hardware problem.

I hope this helps someone. Gotta' go kill some Covenant now.

I think I was able to brute force it... I changed all settings for all games EXCEPT directions for ODST, then backed down to save.
Then, I changed lateral movement to directionals keys, then left. Then, I changed back key and the bug occured... BUT, as I selected "cancel changes made", and then came back, the move backwards key was still binded to the back key.
Same process for the forward key. I have yet to check if they are indeed registrered ingame, but in the menu they're how I wanted them... Even though the bug is still in effect...

TLDR : modify ALL the settings you want BEFORE touching the move forward and backward keybinds, then leave settings to save everything. THEN bind up and down on ODST and select the "cancel changes" option when exiting...