'One or more actions are not bound to a key'

I had this issue for a bit. I found looking through the keyboard settings for each game the default settings will have a few red spots where fields are missing for each game. No idea why they didnt keybind all defaults

I was able to address this by doing the following:

  • Main Menu - Options and Career - Settings - Restore all to Default - Set my settings again, apply to all gamesAll i wanted to do was to up my framerate cap to 180 from 60, and I guess I changed some setting when playing CE or Reach, because trying to change this in Halo 2 it was being so fussy. Glad it’s fixed.

I’ve been getting this message saying that one of my keys in Halo 3: ODST isn’t bound and it’s preventing me from changing any settings at all.

I’ve gone through my controls, and everything is bound correctly. I’ve tried resetting my controls, but when I do, it then tells me that i have unbound keys in 2, 3, and ODST. I then go though and rebind anything that’s not bound, but after I’ve finished, it still tells me that something is unbound in ODST. Resetting ALL my settings to gives me the same result. No matter what I do, the game thinks that some control in ODST isn’t bound even though I’ve gone through all my controls in every game and double checked that all my bindings are correct. All I can do is discard my changes, but when I do that, it STILL tells me that something is unbound, but it will at least let me exit the settings menu. If I go back into the settings, it still tells me that something is unbound.

Who thought that it was a good idea to prevent people from changing their graphics or audio just because some some control isn’t bound?

> 2533274817860562;23:
> I’ve been getting this message saying that one of my keys in Halo 3: ODST isn’t bound and it’s preventing me from changing any settings at all.
>
> I’ve gone through my controls, and everything is bound correctly. I’ve tried resetting my controls, but when I do, it then tells me that i have unbound keys in 2, 3, and ODST. I then go though and rebind anything that’s not bound, but after I’ve finished, it still tells me that something is unbound in ODST. Resetting ALL my settings to gives me the same result. No matter what I do, the game thinks that some control in ODST isn’t bound even though I’ve gone through all my controls in every game and double checked that all my bindings are correct. All I can do is discard my changes, but when I do that, it STILL tells me that something is unbound, but it will at least let me exit the settings menu. If I go back into the settings, it still tells me that something is unbound.
>
> Who thought that it was a good idea to prevent people from changing their graphics or audio just because some some control isn’t bound?

I have the exact same issue. Reinstalling the game doesn’t help.

> 2535408117363337;24:
> > 2533274817860562;23:
> > I’ve been getting this message saying that one of my keys in Halo 3: ODST isn’t bound and it’s preventing me from changing any settings at all.
> >
> > I’ve gone through my controls, and everything is bound correctly. I’ve tried resetting my controls, but when I do, it then tells me that i have unbound keys in 2, 3, and ODST. I then go though and rebind anything that’s not bound, but after I’ve finished, it still tells me that something is unbound in ODST. Resetting ALL my settings to gives me the same result. No matter what I do, the game thinks that some control in ODST isn’t bound even though I’ve gone through all my controls in every game and double checked that all my bindings are correct. All I can do is discard my changes, but when I do that, it STILL tells me that something is unbound, but it will at least let me exit the settings menu. If I go back into the settings, it still tells me that something is unbound.
> >
> > Who thought that it was a good idea to prevent people from changing their graphics or audio just because some some control isn’t bound?
>
> I have the exact same issue. Reinstalling the game doesn’t help.

Deleting this file

%USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini

seems to work, however once I mess with odst keybinds the same problem comes up again. Very frustrating.

I too am getting an unbound message for ODST. Tried rebinding everything, and restoring to defaults. Nothing is working. Played fine a few days ago, but no go today.

> 2535408117363337;25:
> > 2535408117363337;24:
> > > 2533274817860562;23:
> > > I’ve been getting this message saying that one of my keys in Halo 3: ODST isn’t bound and it’s preventing me from changing any settings at all.
> > >
> > > I’ve gone through my controls, and everything is bound correctly. I’ve tried resetting my controls, but when I do, it then tells me that i have unbound keys in 2, 3, and ODST. I then go though and rebind anything that’s not bound, but after I’ve finished, it still tells me that something is unbound in ODST. Resetting ALL my settings to gives me the same result. No matter what I do, the game thinks that some control in ODST isn’t bound even though I’ve gone through all my controls in every game and double checked that all my bindings are correct. All I can do is discard my changes, but when I do that, it STILL tells me that something is unbound, but it will at least let me exit the settings menu. If I go back into the settings, it still tells me that something is unbound.
> > >
> > > Who thought that it was a good idea to prevent people from changing their graphics or audio just because some some control isn’t bound?
> >
> > I have the exact same issue. Reinstalling the game doesn’t help.
>
> Deleting this file
>
> %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
>
> seems to work, however once I mess with odst keybinds the same problem comes up again. Very frustrating.

Thanks, this worked :slight_smile:
I chose not to mess with the ODST controls until I need to, to avoid it happening again.

Anyone seen anything new on this?

Everything was fine, haven’t played in a couple months. Signed in and noted Halo 4 was released. Installed that and now have this key binding bug. The message is about Halo 3 ODST, but can’t save any changes. Have checked through all games, nothing is unbound. Have aligned settings across all games. Tried deleting the %USERPROFILE% file but no luck. Tried resetting ODST to defaults. No success. This seems to be a pretty amateur issue to get out the door. Agree with the previous posts about tying unbound keys to all the other settings (like video settings). Seems kind of dumb.

Super late to the party but I just went into PC settings and hit restore defaults and it fixed it

> 2533274963443531;27:
> > 2535408117363337;25:
> > > 2535408117363337;24:
> > > > 2533274817860562;23:
> > > > I’ve been getting this message saying that one of my keys in Halo 3: ODST isn’t bound and it’s preventing me from changing any settings at all.
> > > >
> > > > I’ve gone through my controls, and everything is bound correctly. I’ve tried resetting my controls, but when I do, it then tells me that i have unbound keys in 2, 3, and ODST. I then go though and rebind anything that’s not bound, but after I’ve finished, it still tells me that something is unbound in ODST. Resetting ALL my settings to gives me the same result. No matter what I do, the game thinks that some control in ODST isn’t bound even though I’ve gone through all my controls in every game and double checked that all my bindings are correct. All I can do is discard my changes, but when I do that, it STILL tells me that something is unbound, but it will at least let me exit the settings menu. If I go back into the settings, it still tells me that something is unbound.
> > > >
> > > > Who thought that it was a good idea to prevent people from changing their graphics or audio just because some some control isn’t bound?
> > >
> > > I have the exact same issue. Reinstalling the game doesn’t help.
> >
> > Deleting this file
> >
> > %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
> >
> > seems to work, however once I mess with odst keybinds the same problem comes up again. Very frustrating.
>
> Thanks, this worked :slight_smile:
> I chose not to mess with the ODST controls until I need to, to avoid it happening again.

Same problem, fixed worked for me too - thanks all at Halo Waypoint who have been on this topic, appreciated!

Deleting the GameUserSettings to basically hard reset the controls worked for me. But I basically can’t play ODST until this gets fixed. Wanted to do some firefight with some buddies tonight and I tried to finally set the key binds for ODST, but now I’m back to the bugged state of the keybinds and I’ll have to fully reset everything by deleting that file again. Which is a huge pain because now I have to go through each game again to set the bindings…

I have found a solution for the ‘ONE OR MORE ACTIONS ARE NOT BOUND TO A KEY’ bug in Halo 3 ODST in the MCC:
Editing the %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini
file is a workaround for changing the key bound in Halo MCC outside of the Hallo MCC settings screen .
You can open the ini file in Notepad.
When opened you will find a [/Script/MCC.MCCGameUserSettings] row
Underneath it there is the CustomKeyboardMouseMapping[0]= this is the keyboard mapping for Halo Reach
Scrolling further down to CustomKeyboardMouseMapping[4] you will find the keyboard mapping for Halo 3 ODST.
To change the walking forward and walking backward keys I had to adjust the:
GameKeyboardMouseMappings[19]=(AbstractButton=19,VirtualKeyCodes[0]=38 (up key)
GameKeyboardMouseMappings[20]=(AbstractButton=20,VirtualKeyCodes[0]=40 (down key)
From their respective 87 (W) and 83 (S) default settings respectively.

Other keys ( GameKeyboardMouseMappings[1] - GameKeyboardMouseMappings[70] ) can be changed here as well by changing the VirtualKeyCodes=. But I would suggest changing as much as possible in the Hallo MCC settings screen and save changes after changing a couple of key. Make as much changes as possible in the Hallo MCC settings. Afterwards you can open the GameUserSettings.ini file and copy key bounds to the CustomKeyboardMouseMapping[4] from the CustomKeyboardMouseMapping[0] Halo Reach, CustomKeyboardMouseMapping[1] Halo CE, CustomKeyboardMouseMapping[2] Halo2 or CustomKeyboardMouseMapping[3] Halo3:

CustomKeyboardMouseMapping[4]=(
GameKeyboardMouseMappings[0]=(AbstractButton=0,VirtualKeyCodes[0]=96,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[1]=(AbstractButton=1,VirtualKeyCodes[0]=50,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[2]=(AbstractButton=2,VirtualKeyCodes[0]=6,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[3]=(AbstractButton=3,VirtualKeyCodes[0]=5,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[4]=(AbstractButton=4,VirtualKeyCodes[0]=174,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[5]=(AbstractButton=5,VirtualKeyCodes[0]=34,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[6]=(AbstractButton=6,VirtualKeyCodes[0]=52,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[7]=(AbstractButton=7,VirtualKeyCodes[0]=46,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[8]=(AbstractButton=8,VirtualKeyCodes[0]=2,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[9]=(AbstractButton=9,VirtualKeyCodes[0]=163,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[10]=(AbstractButton=10,VirtualKeyCodes[0]=1,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[11]=(AbstractButton=11,VirtualKeyCodes[0]=107,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[12]=(AbstractButton=12,VirtualKeyCodes[0]=109,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[13]=(AbstractButton=13,VirtualKeyCodes[0]=67,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[14]=(AbstractButton=14,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[15]=(AbstractButton=15,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[16]=(AbstractButton=16,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[17]=(AbstractButton=17,VirtualKeyCodes[0]=67,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[18]=(AbstractButton=18,VirtualKeyCodes[0]=110,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[19]=(AbstractButton=19,VirtualKeyCodes[0]=38,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[20]=(AbstractButton=20,VirtualKeyCodes[0]=40,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[21]=(AbstractButton=21,VirtualKeyCodes[0]=37,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[22]=(AbstractButton=22,VirtualKeyCodes[0]=39,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[23]=(AbstractButton=23,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[24]=(AbstractButton=24,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[25]=(AbstractButton=25,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[26]=(AbstractButton=26,VirtualKeyCodes[0]=9,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[27]=(AbstractButton=27,VirtualKeyCodes[0]=9,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[28]=(AbstractButton=28,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[29]=(AbstractButton=29,VirtualKeyCodes[0]=0,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),

GameKeyboardMouseMappings[30]=(AbstractButton=30,VirtualKeyCodes[0]=102,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[31]=(AbstractButton=31,VirtualKeyCodes[0]=99,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[32]=(AbstractButton=32,VirtualKeyCodes[0]=90,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[33]=(AbstractButton=33,VirtualKeyCodes[0]=160,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[34]=(AbstractButton=34,VirtualKeyCodes[0]=105,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[35]=(AbstractButton=35,VirtualKeyCodes[0]=82,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[36]=(AbstractButton=36,VirtualKeyCodes[0]=70,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[37]=(AbstractButton=37,VirtualKeyCodes[0]=1,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[38]=(AbstractButton=38,VirtualKeyCodes[0]=160,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[39]=(AbstractButton=39,VirtualKeyCodes[0]=162,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[40]=(AbstractButton=40,VirtualKeyCodes[0]=46,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[41]=(AbstractButton=41,VirtualKeyCodes[0]=49,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[42]=(AbstractButton=42,VirtualKeyCodes[0]=50,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[43]=(AbstractButton=43,VirtualKeyCodes[0]=192,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[44]=(AbstractButton=44,VirtualKeyCodes[0]=2,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[45]=(AbstractButton=45,VirtualKeyCodes[0]=164,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[46]=(AbstractButton=46,VirtualKeyCodes[0]=88,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[47]=(AbstractButton=47,VirtualKeyCodes[0]=90,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[48]=(AbstractButton=48,VirtualKeyCodes[0]=67,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[49]=(AbstractButton=49,VirtualKeyCodes[0]=111,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[50]=(AbstractButton=50,VirtualKeyCodes[0]=39,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[51]=(AbstractButton=51,VirtualKeyCodes[0]=37,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[52]=(AbstractButton=52,VirtualKeyCodes[0]=13,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[53]=(AbstractButton=53,VirtualKeyCodes[0]=69,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[54]=(AbstractButton=54,VirtualKeyCodes[0]=32,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[55]=(AbstractButton=55,VirtualKeyCodes[0]=160,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[56]=(AbstractButton=56,VirtualKeyCodes[0]=164,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[57]=(AbstractButton=57,VirtualKeyCodes[0]=82,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[58]=(AbstractButton=58,VirtualKeyCodes[0]=70,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[59]=(AbstractButton=59,VirtualKeyCodes[0]=2,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[60]=(AbstractButton=60,VirtualKeyCodes[0]=2,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[61]=(AbstractButton=61,VirtualKeyCodes[0]=69,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),GameKeyboardMouseMappings[62]=(AbstractButton=62,VirtualKeyCodes[0]=71,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[63]=(AbstractButton=63,VirtualKeyCodes[0]=67,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[64]=(AbstractButton=64,VirtualKeyCodes[0]=88,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[65]=(AbstractButton=65,VirtualKeyCodes[0]=70,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[66]=(AbstractButton=66,VirtualKeyCodes[0]=51,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[67]=(AbstractButton=67,VirtualKeyCodes[0]=71,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[68]=(AbstractButton=68,VirtualKeyCodes[0]=76,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[69]=(AbstractButton=69,VirtualKeyCodes[0]=38,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0),
GameKeyboardMouseMappings[70]=(AbstractButton=70,VirtualKeyCodes[0]=40,VirtualKeyCodes[1]=0,VirtualKeyCodes[2]=0,VirtualKeyCodes[3]=0,VirtualKeyCodes[4]=0))

I used Excel to compare the VirtualKeyCodes[0] key settings between different CustomKeyboardMouseMapping[0] Halo Reach to CustomKeyboardMouseMapping[6] cross game playlist.

Hope this helps out my fellow Halo fan’s

Had to make some graphical setting adjustments to MCC HALO 3 ODST.
When changing the AbstractButton=19,VirtualKeyCodes[0] and AbstractButton=20,VirtualKeyCodes[0] back to 87 and 83, the
‘ONE OR MORE ACTIONS ARE NOT BOUND TO A KEY’ error disappeared and I could change the settings again in the setting menu and save them.
Afterwards left the game and changed the AbstractButton=19 and 20 to 38 and 40.

try deleting this file if you’re on pc %USERPROFILE%\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings.ini and input.ini

Same. anybody got a solution?

same problem here

i’m having this same issue. it’s locked me into the settings. I can’t even change my -Yoinking!- sensitivity for halo reach because it’s throwing a tantrum, telling me that i have unnassigned controls for halo 1, 2, 3, 4, which i don’t even own.

I don’t care if I have unassigned keys 343, will you please let me play the game?

Hi, everyone.
Like all of you I’ve had problems with this rebind issue. I’ll give you a reprint of a Steam post on the problem that I put up just a while ago. I hope it helps you get to playing:

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.