I still use the momentary buttons on the Alpha and Bravo
I use Joystick Gremlin to manage the switches
The vJoy profile is effectively a virtual joy stick so it doesn’t need an “vJoy +” ; a vJoy button is just like anyother button that you assign but the vJoy button it self is pressed by Joystick Gremlin commands
It can take a while to get your head around it but when you do you’ll frickin love the flexability!
So in Summary
My Alpha profile only assings the yoke axis and momentry buttons to a MSFS function
My Bravo profile only assings the throttle quadrant axis’s and momentry buttons to a MSFS function
The vJoy profile is buttons that are fired off by Gremlin which is fired off by the alpha and bravo which mangages the all the on/off switches on the Alpha & Bravo
Tip
When testing; in Gremlin click on Tools > Input Viewer and then tick the “buttons and hats” for the Alpha, Bravo & vJoy Device and you will see how it works.
When you toggle on a swith on the Alpha (or Bravo) you will see permenant red light stay on in it’s input viewer BUT as you turn the switch on and off you will see a light flash on the Vjoy Device for just a fraction of a second. That is what prevents the heading bug as the vJoy only presses the button down for just a short moment
I’m not sure which screen shot but if it is mine then I am only showing the Bravo. I named it Complex Single + vJoy so that I would know it is used in conjunction with vJoy. What is not shown is my vJoy profile where I map both the Alpha and Bravo buttons to MSFS. I can grab a snap of that later today if you want.
The following images show my mappings for both Alpha and Bravo. The Alpha is mapped to vJoy 1 to 1. Meaning button 5 on Alpha is mapped to button 5 on vJoy. However, I added 40 to buttons I mapped from Bravo. So button 17 on Bravo would be 57 on vJoy for example. This might not line up with the xml you have so adjust your mappings as necessary.
I’m astonished such a simple bug as “don’t screw up the sim if a button is mapped as set” is still present after all this months… Still Asobo got paid to wait for customers to solve their shortcomings after buying 300$ hardware pieces, which work perfectly outside their software.
This is understandable but this doesn’t solve the problem of using the Honeycomb hardware with other programs which are using auto-detection for assigning switches:
It was really bad today as ALT was jumping by 2000 using the knob on the Bravo. I have tried using the fix in FS Tool but it doesn’t seem to be making any difference. I am trying to wait this out without going the additional software route as I am not keen on having to redo the 8 profiles I currently have on the Bravo. I just reverted to using the mouse clicks today.
Hi all
Just plunged in the honeycomb bravo throttle and none of the axis work.
I have the default selected
If I try and change them they become a switch (on or off)
If I check them in sensitivity it looks fine
but I cant get anything to work in the sim
Any suggestions?
You definitely need to make a custom profile make sure when you are programming the axis you don’t go into the detent because that is a button. Also make sure you have downloaded the driver off of honeycombs website. Also for the axis make sure you are programming them in the 100 thru -100 axis not throttle increased and decrease.
Thanks for this - I am going to try this today! One question, it looks like you mapped the throttle detent buttons on the Bravo within MSFS. These detents wont send continuous signals triggering the 100/1000 bug?
I don’t know as I have not mapped them to the auto pilot I use them as reverse thrusters sorry. Last I heard all of the buttons on bravo are continuously on. I’m sure the heading bug will be the same no matter where you map to it.
Yes these throttle indents do send a continuous signal so would cause the acceleration bug BUT when you use the throttle indent for their intended function (reverse thrust) you are never adjusting altitudes or the OBS dials anyway so it doesn’t matter.
BUT to be safe you should unmapp the throttle indents on the other throttle levers that you are not using; especially those where you have to pull them all the way down to put on the rubber covers
The other thing I see a lot of people over looking that triggers the acceration bug on the Bravo is the left hand rotary dial where you select alt, heading etc. That must be unmapped from the Bravo profile as well.
I think I have Gremlin and vJoy set up properly, but there must be something I’m missing. I set some bindings in Gremlin, but none of the inputs are recognized in MSFS under the vJoy control settings.
