VRInsight Console and Bridge Command 5.x on Windows

[forum_admin]

Hi, I'm aware various people have been having problems with the VRInsight console and Bridge Command 5.x. Irrlicht (the game engine used) was only checking the first 6 joystick axes on windows. I've changed this and recompiled the Irrlicht dll.

I think that I have a fix for this problem, and I'd appreciate any testing.

Instructions:

Download the updated Irrlicht.dll from https://github.com/bridgecommand/bc/raw/53ce73607349fea17b0a2e60a2563a62923a04d3/Irrlicht.dll and replace the Irrlicht.dll in your installation.

Use the settings editor to make the following settings

port_throttle_channel=3
stbd_throttle_channel=2
rudder_channel=1

Any feedback if this is working would be much appreciated.

[Sven]

Hi,
I am not a user of bridgecommand yet.
In case I download bridgecommand and buy the console for a more realistic control, would there still be these issues to sort out?
Is there any other ship console that works better?
Thanks
Sven

[forum_admin]

I haven't heard of any issues with the VRInsight console after this fix.

I'm not aware of anyone else making another equivalent console, but it's relatively simple if you want to set up your own: https://www.bridgecommand.co.uk/Doc/makethrottle.php

[forum_admin]

Just as an update, this is now included in main Bridge Command release, so you don't need to download the updated dll.

Based on reports from users, one of the following settings should work:

port_throttle_channel=8
stbd_throttle_channel=7
rudder_channel=6

or

port_throttle_channel=3
stbd_throttle_channel=2
rudder_channel=1

Ship console users - please let me know what works for you!

[ship-bzh]

Thanks for the 5.6.1, working out of the box now with VR Insight !!

[Guido]

In BC 5.7 VRinsight is working great! How to address the buttons I made red? There is no number available.

[forum_admin]

Hi, can you check with https://gamepad-tester.com? You should see the button state change when you press each button. Note that this will show buttons from 0 upwards, whereas Bridge Command uses button numbers 1 upwards. So if you find on gamepad-tester that it is B10, you would need to use the setting 11 in Bridge Command.

I hope this makes sense! Please post back if it doesn't (or if you get it working!)

[Guido]

Great tool!
The red buttons use "AXIS 9"
Default value: 3.28571
Left: 0.71429
Right: -0.42857
Up: -1.00000
Down: 0.14286
How to configure in the ini-files?

[forum_admin]

Hi, what do you want to map these to do? I suspect I may need to implement something special for this, depending on how you want these buttons to work.

[Guido]

As you described with https://gamepad-tester.com you could see what happens when you press a button. This was what happens when you press the "red" buttons.

I would like to map the next settings to it:
joystick_button_look_left = "AXIS 9, 0.71429"
joystick_button_look_right = "AXIS 9, -0.42857"
joystick_button_look_up = "AXIS 9, -1.00000"
joystick_button_look_down = "AXIS 9, 0.14286"

I'm not familiar with programming in c++. I'm more familiar with c#. This is a good reason to learn ;-) 

[forum_admin]

Thanks, that's clear. Because it's 'pretending' that these control a joystick axis, not normal joystick buttons, I'll have to program something to detect cases like this.

In case you want to look yourself, it's in the event receiver, from this point: https://github.com/bridgecommand/bc/blob/master/src/MyEventReceiver.cpp#L737

[Guido]

I'm going to give it a try ;-)