Open iancclark opened 3 years ago
Figuring out which line is for which transport mode would be a good start
Sure. I set each section to a different preset (keyboard/custom/joystick/mouse) and found the following order: General Ship SRV On foot
I don't suggest you spend too much time on this, as it only breaks when bindings are changed, can be fixed by changing bindings in Horizons and Odyssey isn't really playable in VR yet. Perhaps just catch the "there are newlines in startpreset" and either split it and wrap a loop to populate controlBindingsPaths or coerce it to "Custom" like the blank case.
Thanks!
Oh, Ship and SRV get their own separate binding sets. That was unexpected.
If you use custom it's still all in one XML file. I attach my binds as an example.
I suppose this allows people to reset just one section to "standard" bindings leaving custom settings alone in other sections.
Odyssey seems to split the bindings by transport mode, and changes the "StartPreset.start" in such a way that Elite VR Cockpit's parser dies with:
Simply renaming the Odyssey StartPreset.start to something else (e.g. StartPreset.start.ody) should get you running with Elite VR Cockpit again.
New format: StartPreset.start.ody.txt
I've never built a Unity project, so I'm afraid I wouldn't know where to start with proving a patch. Happy to try if someone points me at a guide. Thanks.
Update: Not so sure this is down to StartPreset.start any more. It is still possible to fix by loading Horizons, making a change to bindings, applying and restarting Elite VR Cockpit. You can then (if you want to brave the Odyssey VR bugs) quit Horizons, leave EVRCP running, start Odyssey and play.