Odyssey Bindings Error?.

Saltyseadog

Saltyseadog
Fired up Odyssey today after a couple of days to find that my Odyssey binds file wasn't installing. When I checked the binds file in the options folder I found an "Error" file. I installed my back up file and the game started fine after that. On opening the error file I found the following info:
There where errors when loading preset file: Odyssey.4.0.binds
There are multiple entries of binding "MouseGUI" Only the first will be used
There are multiple entries of binding "MouseGUI" Only the first will be used
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Failed to find GUID for device: 046DC216
Click to expand...
Any of you clever chappies know what it means and how to avoid it in future?.
 

STRONTIUM DOG

STRONTIUM DOG
sounds like it did not recognise the device for a brief moment like a power issue still that's a wild guess...……………………….
whilst the device was in this state it sought to overwrite your bind file to correct it creating an error in the bind file
by you using your old bind again " when the device was seen by windows ok" it corrected the device not seen error imo
and is basically the reason for the bacup binds in my guide....
why your device or devices was not initially seen is anyones guess...……………
(and is the reason why the statement check that your devices are recognized by windows first(tested) in mentioned guide)
if windows does not see the device ok first the game def wont...………...
 
Last edited:

metatheurgist

metatheurgist
Not how I'd put it. I might say they didn't "load"; install implies you somehow directly transferred your bindings into the game.

ED will reset your bindings to a default setting if it can't find a controller specified by your "custom" bindings, it will not "load" them. This may be explained by the "can't find device" by GUIID message.
 

STRONTIUM DOG

STRONTIUM DOG
9 out of ten cats know this is usually caused by starting the game without(forgetting to plug) a controller plugged in and having a custom bind setup (a power issue will have the same effect as not being plugged in obviously)
if using custom binds all devices MUST BE plugged in & RECOGNIZED BY WINDOWS FIRST before the game is launched
else it will create errors in the bind file...……………………….(hence the strongly advised back up)
peeps using default context binds probably wont get that error even if they do forget to plug in to play


if you do start the game then remember you forgot to plug in DO NOT VISIT THE CONTROLS SECTION OF THE GAME
simply quit the game plug in then restart thus preventing the game trying to correct " missing" control issues by rewriting your custom binds file which will be doomed to fail because according to windows the device is missing ie unplugged or unpowered
 
Last edited:

Saltyseadog

Saltyseadog
I think what has happened was that previously when I haven't played for a few days, sometimes it triggers the X56 throttle bug on mine so I have found the solution to this is to re-calibrate/re-set my X56 and Logitech F310 running the joy.cpl option in Windows and then reboot my PC. When I did this yesterday iirc I did the joystick, throttle, F310 in that order and this might have possibly had some sort of impact. Anyway I was playing tonight and everything loaded up fine again so consider it closed from my side. The only reason I posted was due to the amount of "multiple entries for MouseGUI as I very rarely use the mouse at all in Odyssey.
 
You must log in or register to reply here.
Back
Top Bottom