HELP! Returning old codger needs a few pointers.

WARNING! All 4 binds selections MUST point at the SAME custom file for your profile to work.

Well I bit the bullet and Loaded Odyssey. Couple of things to relate to you all, I previously used vJoy for my Virpil Gear (which worked flawlessly in Horizons) -im now letting Virpil handle the 32x whatever splits for buttons.

I let Elite do its thing and recreate what it could from my ver3 Binds File. I managed the missing control bindings for "activate shutdown field neutralizer" and plonked an [L ALT] for all of the Galaxy Cams Keys to eradicate some dups it had found.

Now got the error message at the top of this plea for assistance and so far haven't a bloody clue how to address it. I'm able to and manage to use Notepad++ to read and edit my files so a clue as to where to look for the offending references would be appreciated.

(Reason for long absence, operation at the base of my spine, even with cushions couldn't sit on my office/gaming chair for very long - working up slowly to getting used to the new pain)

Appreciate any pointers.
 
I can't say for sure but i think what it means is when you launch the game and go into options, make sure all four binding categories (general, ship, foot, srv) are pointed to "custom"
 
I had 3 of them for virpil and one for generic and I'd get that complaint in voice attack but I did eventually just copy my custom keybind for onfoot to also be virpil and all is happy now.
Never had the game complain or not work while I was too lazy to do change.
 
WARNING! All 4 binds selections MUST point at the SAME custom file for your profile to work.
.....

Is that only if you use "custom"? I ask because some time ago I had the On-Foot as an xbox360 controller and the other three were to my renamed file (i.e. not "custom") and I never had any issues. So - is this new or is it just when using "custom"?
 
Not sure about this "all 4 must be pointing to custom" - cause I don't on mine.

Got a VKB HOTAS (Omnithrottle/EVO pair) and an Xbox One Elite controller - and all but On Foot are "custom"

the key I'd say is make sure when you load up that all devices you configured prior are exactly where it was prior to last time you run it - or it will dump your config.

Thankfully it keeps a backup of sorts - provided you don't overwrite it. - which is why I keep a backup duplicate in-case it happens.

Sometimes my controller goes "missing" because windows does things - so its a hard lesson I learned.

PS: Also make sure to map your controller "interact button" to the "UI Panel Select" on the General Controls - or you will not be able to hand in things on-foot - real P I T A that took me hours to solve.
 
Well i gave up when copying custom became so bulky, had only just got my head around voice packs. Too much to redraw all the schemes again. Something i learned was the controller inputs must be consistently in same inputs and on at launch.
 
the key I'd say is make sure when you load up that all devices you configured prior are exactly where it was prior to last time you run it - or it will dump your config.
This is correct. When I replaced my CH Pro Pedals with Turtle Beach VelocityOne Rudder Pedals, the only way I could keep my other control bindings intact was to delete the yaw bindings for the CH Pedals ingame, then shut down the game, then disconnect the CH Pedals, connect the VelocityOne Pedals, restart the game, then select the new pedals as the yaw binding. Note: every single binding (axis and button) associated with the old peripheral in every game aspect (ship, SRV, on foot), must be deleted ingame from the bindings menu before removing the old peripheral and connecting the new one (don’t miss any!) otherwise the game will dump your whole config.
 
Or you can just go in and do a grep/replace on the bindings file if you know the internal name of the new controller and the name of the old controller (and it has a similar control set). I've done this a few times.
 
This is correct. When I replaced my CH Pro Pedals with Turtle Beach VelocityOne Rudder Pedals, the only way I could keep my other control bindings intact was to delete the yaw bindings for the CH Pedals ingame, then shut down the game, then disconnect the CH Pedals, connect the VelocityOne Pedals, restart the game, then select the new pedals as the yaw binding. Note: every single binding (axis and button) associated with the old peripheral in every game aspect (ship, SRV, on foot), must be deleted ingame from the bindings menu before removing the old peripheral and connecting the new one (don’t miss any!) otherwise the game will dump your whole config.

... or just connect the new controller (in my case it was a VKB Omnithrottle) and re-assign each of the buttons / axes used by the old controller (CHProThrottle in my case). On restarting the game after disconnecting the old controller if the options sections has issues you know you missed something so shut down, reconnect old gear, switch on and select the old bindings file name* in the drop-down list and fix your error. Would be much quicker for pedals LOL.

* If you have not renamed your bindings, then sorry but using "custom" is jobbie.
 
Back
Top Bottom