Error checks on .binds files

[M. Kowalsky]

Before I ask in the official forums, does anyone here know if there are any flags we can set either at startup or in a config file to turn on debugging information about the XML parsing of the .binds controller files?

I've edited mine manually, and of course must have missed a closing anchor or messed-up a keyword and my customized config file doesn't show up in the in-game list next to the others.
I've already got VerboseLogging set to 1 but it's just for the netlog.

Any other ideas to check the validity of the xml ?

[Flip]

Paste its contents into an online xml validator, like this one for example: http://www.xmlvalidation.com

It should find the error(s) for you.

[M. Kowalsky]

Thanks for the tip, but it didn't detect any error on my file.

Hmmm, yes, I've put the file in the correct directory, with all the other .binds files
It is named with a .binds extension and doesn't have a weird name
It starts with

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<Root>
   <MouseXMode Value="" />


...what else could be wrong?

[Flip]

All the other .binds files? There's only one in my directory:

C:\Users\[username]\AppData\Local\Frontier Developments\Elite Dangerous\Custom.binds

Plus StartPreset.start.

[M. Kowalsky]

Hmm, ok that's interesting.
My directory C:\Users\...\AppData\Local\Frontier Developments\Elite Dangerous only contains

Code: Select all

573741 <- Directory
Options <- Directory
AppNetCfg.xml
TelemetryCache.log


Maybe you still have bits leftover from the Alpha or Beta? I've installed the game only a couple of weeks ago, straight into 1.04 IIRC

Instead, I put my file into C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1010\ControlSchemes
It contains about a dozen .binds file for various controllers (HOTAS, pad, joysticks, etc)

Thing is, I also put in there some files downloaded from the forums, like "T.Flight Hotas X Crab setup v5.36.binds" (from here) and they were picked up and worked fine in-game.

Anyway, I went through my file again and I think I've spotted a couple of places where I have some conflict.
It's a bit late now so I'll check that again tomorrow

Thx

[Flip]

Sorry, fucking Windows didn't copy the whole path. That should have been:

C:\Users\[username]\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings\Custom.binds

[M. Kowalsky]

Yeah, I just found it.

And in there, I also found the answer to my original question: a LoadErrors.log file containing some clues:

Code: Select all

There where errors when loading preset file: My T-Flight Hotas X.binds
Failed to find GUID for device: {Keyboard}
Failed to find GUID for device: {Keyboard}
Failed to find semantic: RadarRangeAxis


Well, I'll deal with that in the morning...

[Flip]

Good luck!

[Zieman]

Before I ask in the official forums, does anyone here know if there are any flags we can set either at startup or in a config file to turn on debugging information about the XML parsing of the .binds controller files?

I've edited mine manually, and of course must have missed a closing anchor or messed-up a keyword and my customized config file doesn't show up in the in-game list next to the others.
I've already got VerboseLogging set to 1 but it's just for the netlog.

Any other ideas to check the validity of the xml ?

I see you found the LoadErrors.log

I'd recommend opening the offending file and one of the existing presets side by side in NotePad++ (for example). Side by side comparison has helped me to catch a few stupid user errors in my own bindings file, and NotePad++ does a good job at detecting missing brackets & stuff.

All the other .binds files? There's only one in my directory:

C:\Users\[username]\AppData\Local\Frontier Developments\Elite Dangerous\Custom.binds

Plus StartPreset.start.

There's a bunch (the pre-set configurations) in
<Your E: D Install Dir>\EDLaunch\Products\FORC-FDEV-D-100X\ControlSchemes

[M. Kowalsky]

Got it to work now, thanks all