Can I get the version before the one on the website? The current version does not work on my system for some reason. I fires up but freezes and does not see my MCP2. Previous version had no issues. Like a dummy, I deleted it. 

What bridge? For the VRI MCP? Sorry, but I don't keep previous versions of the hobby projects. Are you using the latest AAO?

Did you try the Brdige in Plugin Mode? Save the VRItoLorbyAAOBridge.exe and the Json.dll to "\Documents\LorbyAxisAndOhs Files\Plugins\VriBridgePlugin"

If you do that, you don't have to start it yourself anymore, AAO will do it automatically. And you don't have to concern yourself with the WebAPI Port anymore either

Anyway, sounds more likely that there is a conflict with another driver or tool that also tries to access the VRI device. What you are seeing are the typical symptoms of the VRo software and/or FSUIPC interfering.

Edited April 29, 20233 yr by Lorby_SI

6 hours ago, Lorby_SI said:

What bridge? For the VRI MCP? Sorry, but I don't keep previous versions of the hobby projects. Are you using the latest AAO?

Did you try the Brdige in Plugin Mode? Save the VRItoLorbyAAOBridge.exe and the Json.dll to "\Documents\LorbyAxisAndOhs Files\Plugins\VriBridgePlugin"

If you do that, you don't have to start it yourself anymore, AAO will do it automatically. And you don't have to concern yourself with the WebAPI Port anymore either

Anyway, sounds more likely that there is a conflict with another driver or tool that also tries to access the VRI device. What you are seeing are the typical symptoms of the VRo software and/or FSUIPC interfering.

For the VRI MCP. Don’t have fsuipc or whatever that VRo thing is installed. Tried it in both standalone and via the plugin method by putting it in the proper folder folder in the Documents folder. In both cases. After being started is just freezes up. I can click on the green light button and it does come on. I have the VRI MCP profiles from Gunseli loaded and can select the aircraft. 
 

it worked fine before but I have since gotten a new computer. I backed everything up and I put everything back in. Got AAO running just fine using the hardware change menu feature and all my templates back in with no issues.

The VRI Bridge, once started via either method, will not display on the MCP2. Further, I cannot turn close the Bridge program. It goes to not responding and I can’t even shut it down via the Taskmanager. It literally takes having to restart the computer to shut down your VRI Bridge program. Have no idea what is going on. I tried plugging the MCP2 into a different USB port and that did not work either. For now I’m just not using it anymore.

5 hours ago, B777ER said:

For the VRI MCP. Don’t have fsuipc or whatever that VRo thing is installed. Tried it in both standalone and via the plugin method by putting it in the proper folder folder in the Documents folder. In both cases. After being started is just freezes up. I can click on the green light button and it does come on. I have the VRI MCP profiles from Gunseli loaded and can select the aircraft. 
 

it worked fine before but I have since gotten a new computer. I backed everything up and I put everything back in. Got AAO running just fine using the hardware change menu feature and all my templates back in with no issues.

The VRI Bridge, once started via either method, will not display on the MCP2. Further, I cannot turn close the Bridge program. It goes to not responding and I can’t even shut it down via the Taskmanager. It literally takes having to restart the computer to shut down your VRI Bridge program. Have no idea what is going on. I tried plugging the MCP2 into a different USB port and that did not work either. For now I’m just not using it anymore.

I'm sorry, but I've never heard of something like this before. "Not responding" just means that it is busy. In this case probably busy processing errors because it can't or isn't allowed to access the VRI device.

I can only imagine that something is wrong with the way that the COM ports are set up for the VRI device. Unfortunaltey I don't have any VRI hardware myself, so I cannot test or verify. The testers for the Bridge are usually very active, so I have to assume that I would know if there was an internal problem. For the record: when installing it as a plugin, you don't get to start or stop the bridge program. AAO is supposed to do that.

Did you try with a fresh configuration too? Or has that been ported over from your old computer as well?
When in doubt, delete this and start over:
C:\Users\...\AppData\Local\Lorby-SI\VRItoLorbyAAOBridge.exe_Url_* (all of those folders)
C:\Users\...\AppData\Local\LORBY_SI\VRIBridge

In that last folder there are also logfiles that you could look at. But from the sounds of it, there won't be relevant data in them.

Edited April 30, 20233 yr by Lorby_SI