I am using the Bridge to connect to the VrInsight Airbus FCU. I have programmed buttons and saved as a Template. However when I reopen the button numbers have changed and either nothing works or a different switch operates on the aircraft. I am very confused.  Any ideas would be very helpful

That woudl happen when the Bridge program can't save its config file:
C:\Users\...\AppData\Local\LORBY_SI\VRIBridge

Are you using Plugin or Stand Alone mode?

2 hours ago, Lorby_SI said:

That woudl happen when the Bridge program can't save its config file:
C:\Users\...\AppData\Local\LORBY_SI\VRIBridge

Are you using Plugin or Stand Alone mode?

Plugin

Try stand alone, at least once.

I think that I know what this is (it is a bug in the Bridge program of course). When in Plugin mode, AAO is too eager to shut down the Bridge, so it doesn't get a chance to save its database file. 

This can be fixed in the plugin protocol, but that requires a AAO version.

The work around is at the moment to either use one of the ready-made profiles from flightsim.to

VRInsight MCP Combo II (Boeing) Templates & Display profiles (for AAO) for Microsoft Flight Simulator | MSFS

And/or create at least one display profile of your own. Once you do any adition action or change to a different display profile, the database will be saved, including the button configuration.

Also, when you run the plugin in stand alone mode, and create your button layout, then the file will be saved when you shut down the bridge normally.

Actually - I have to take that back. I don't know why this should happen to you. Trouble is, that I don't have any VRI hardware, I have to deal with the Bridge program "blind" (it was made blind as well, by request from another person).

In this case I was wrong with the analysis. The bridge has hard coded IDs for the buttons, they don't depend on saving the profile at all.

The only reason for the behaviour that you describe would be errors in the serial communications protocol betweem the Bridge and the VRI device. The bridge has been made for the Boeing variant, so I cannot guarantee that it will work (well or at all) with the Airbus MCP. Could something else be interfering, any other piece of software that is also trying to talk to the device at the same time?

Edited July 15, 20241 yr by Lorby_SI