Plugins never were officially supported; so if a plugin is giving you an issue, either deal without the plugin or gtfo.

Sure, VO rebinding stuff can be annoying, but just be glad you have any plugins at all. Would be much easier for GS to just say "ok, plugins are giving us a headache so we disabled them".

Also calling VO stupid because you are using unofficial third party plugins is stupid. Stop using them if they annoy you so much.

[edit]

I would like to add that my current config is around 10 years old. I've used many many different controllers, computers and even phones, yet my binds have never been over written in the way you suggest. A simple copy/paste of my wgaf and I'm ready to roll, even on a new device.

In this case no it didn't involve a plugin ... all the plugins loaded without incident.

The point of this is that the behaviour of VO is wrong... VO should not make a change to a players setup without asking first. (even if a plug crashes) The exception being the initial creation of the ini and wgaf files and the installation of a new piece of hardware.

BTW Yoda - Plug ins became an official part of VO the moment Guild included Lua in the program. Nobody expects Guild to solve problems caused by plug ins but I do expect a certian amount of consistant behaviour out of the interface....

Lets try this in a different way. I set up a clean ini and wgaf file and saved a copy _ i will email them to you if you want. I then started VO, let it reach the login screen and quit. These are the changes it made in my files (I havent made a line by line comparison yet)

added in wgaf at log in screen
bind ChordXY help_joystick
bind ChordYB Jettison
bind DPadUp +StrafeUp
bind DPadDown +StrafeDown
bind DPadLeft RadarNextNearestEnemy
bind DPadRight RadarNextFront
bind ThumbLeft +Turbo
bind ThumbRight +Brakes
bind L1 +Shoot2
bind R1 +Shoot1
bind Start +zoom
bind JoyButtonA FlyModeToggle
bind JoyButtonB Activate
bind JoyButtonX missionchat
bind JoyButtonY say_channel

Changes to the wgaf

[Saitek Cyborg X (/dev/input/js0)] <- changed (Loaded as js0)
JOYBUTTON0=+Shoot1
JOYBUTTON1=Activate --- added
JOYBUTTON2=missionchat -- added
JOYBUTTON3=FlyModeToggle
JOYBUTTON4=Activate
JOYBUTTON5=+Shoot1 -- added
JOYBUTTON6=Quit
JOYBUTTON7=+zoom -- added
JOYBUTTON8=+Turbo -- added
JOYBUTTON9=+Brakes -- added
JOYBUTTON10=RatPay
JOYBUTTON11=RatPay
JOYBUTTON12=RatPay
JOYBUTTON13=+Shoot3

[Saitek Cyborg X (/dev/input/js1)] <- original
JOYBUTTON0=+Shoot1
JOYBUTTON1=
JOYBUTTON2=
JOYBUTTON3=FlyModeToggle
JOYBUTTON4=Activate
JOYBUTTON5=
JOYBUTTON6=Quit
JOYBUTTON7=
JOYBUTTON8=
JOYBUTTON9=
JOYBUTTON10=RatPay
JOYBUTTON11=RatPay
JOYBUTTON12=RatPay
JOYBUTTON13=+Shoot3

[Logitech Logitech Extreme 3D (/dev/input/js1)] <--- Loaded as Js1 and changed
JOYBUTTON0=+Shoot2
JOYBUTTON1=Activate -- added
JOYBUTTON2=RadarNextFrontEnemy
JOYBUTTON3= --- removed
JOYBUTTON4=RadarNextNearestEnemy
JOYBUTTON5=RadarNextFront
JOYBUTTON6=Quit
JOYBUTTON7=+zoom --- added
JOYBUTTON8=+Turbo -- added
JOYBUTTON9=+Brakes -- added
JOYBUTTON10=
JOYBUTTON11=

[Logitech Logitech Extreme 3D (/dev/input/js0)] <--- original
JOYBUTTON0=+Shoot2
JOYBUTTON1=
JOYBUTTON2=RadarNextFrontEnemy
JOYBUTTON3=RoidScan
JOYBUTTON4=RadarNextNearestEnemy
JOYBUTTON5=RadarNextFront
JOYBUTTON6=Quit
JOYBUTTON7=
JOYBUTTON8=
JOYBUTTON9=
JOYBUTTON10=
JOYBUTTON11=

My bind of J to jettison was wiped out as well....I assume when VO did - bind ChordYB Jettison

It seems like the best solution here is for you to change the ownership of your config file and deny write access to the user which runs the VO process. It doesn't seem realistic that the devs are going to add special functionality to the config file update behavior for your very specific edge case of two flight sticks getting wonky when VO crashes due to a plugin related crash.

Sadly I cant change the file to read on;y. A number of my plugs write information to the config.ini for thier own configurations. I do keep my wgaf on write protect but VO still changes the values it uses in - game rendering that tactic rather ineffective.

BTW this is not just when a plug crashes. This happens every time VO loads and its not an edge case either. While It does appear to mainly affect joystick users with dual sticks being the worst case some of the changes are keyboard related and could be affecting even those poor souls who have no sticks.

Here's a dumb question, but does the problem persist if you disable all plug-ins? (i.e. could it be a plug-in that's actually overwriting your binds and not the VO client?)

Yeah I have tried it with out plug ins.... and yes same results
Its the VO loader that is making the changes.

We are still talking about this? yeesh, just make a plugin that fixes it yourself.

Because this is such a random problem that only you seem to experience, could it be malware on your PC? I use a two stick setup too sometimes, I use random controllers that I find in the bin at work and I use an Android/PC/Mac client too. Never had the problem you are describing.

Maybe you should try on a freshly loaded PC? I've never had my devices switch ID like you seem to, and I have never ever had my config rewritten unless I delete it. Maybe you should use vo's built in /save and /load commands to enforce a config that you find nice on every load.

Just make a plugin to /save your binds once happy, then /load it when you login. Really should not be hard. But please please show me these other people that are having problems because apart from you; there are not any.