When Honeycomb Alpha Yoke is connected and it's "sticky" 2-position switches are assigned, various bugs manifests themselves (10-deg heading bug increments, 1000ft alt setting increments, exaggerated trim inputs). Do you know if this issue can be solved by not assigning the commands to the "sticky" buttons in the sim interface, but via the FSUIPC 7 "Buttons & Switches"?

Pete Dowson, the FSUIPC author is explaining that usage of FSUIPC causes massive FPS drop due to the bug Asobo introduced in the release version of simconnect (was working properly in beta). So seems like the usage of FSUIPC will not help until the patch fixing simconnect will be released (in a week?).

FSUIPC forum

Oh dear, I was hoping for "tweaking free" experience, for more flying than playing with offsets, calibration. Setup of the new sim is like building kit airplane, more time in tha hangar than in the air. But there is some pervers fun in this...

Edited August 28, 20205 yr by Steku

I just ordered a Honeycomb Yoke and hope those issues are manageable. I am counting on Spad.Next to be able to overcome any of these issues as they crop up.

For now (until the simmconect bug is removed allowing FSUIPC use) the only option I know for Honeycomb Alpha Yoke is to unbind all the commands from the 2-position switches and magneto switch, otherwise trim control will be exagerated. 

2 minutes ago, Steku said:

For now (until the simmconect bug is removed allowing FSUIPC use) the only option I know for Honeycomb Alpha Yoke is to unbind all the commands from the 2-position switches and magneto switch, otherwise trim control will be exagerated. 

 

 

23 hours ago, Steku said:

When Honeycomb Alpha Yoke is connected and it's "sticky" 2-position switches are assigned, various bugs manifests themselves (10-deg heading bug increments, 1000ft alt setting increments, exaggerated trim inputs). Do you know if this issue can be solved by not assigning the commands to the "sticky" buttons in the sim interface, but via the FSUIPC 7 "Buttons & Switches"?

Pete Dowson, the FSUIPC author is explaining that usage of FSUIPC causes massive FPS drop due to the bug Asobo introduced in the release version of simconnect (was working properly in beta). So seems like the usage of FSUIPC will not help until the patch fixing simconnect will be released (in a week?).

FSUIPC forum

Oh dear, I was hoping for "tweaking free" experience, for more flying than playing with offsets, calibration. Setup of the new sim is like building kit airplane, more time in tha hangar than in the air. But there is some pervers fun in this...

I have been a regular here since launch and this is the first I’ve heard of this stuff. And I have the yoke with all buttons assigned and can’t say I’ve noticed any strange behaviour. But maybe I’m not looking for the right thing. 
Can you please let me know where has this been discussed? 
 

I'm happy to report, that I (with the assistance of John Dowson) was able to assign all the Honeycomb Aplha Yoke 2-position "always-on" switches and the magneto switch via the FSUIPC 7 beta. As I no longer have any commands assigned to these switches in the sim direclty, the 10-degree haeading bug issue and the exagarated trim movement is gone.

See this thread:

https://forum.simflight.com/topic/90277-input-from-buttons-32-127-not-recognized/

However, due to error is simconnect, FSUIPC usage is currently causing massive FPS drop - this issue shoud dissapear as soon as Asobo will fix simconnect (the patch expatect in few days?). We will see if Asobo will also fix the "always-on" buttons issue direcltly, but I wouldn't expect this very soon. Moreover FSUIPC offers much more, it also allows handling buggy Nav and Taxi light commands, proper axis calibration and much more.

6 hours ago, Virtual-Chris said:

I have been a regular here since launch and this is the first I’ve heard of this stuff. And I have the yoke with all buttons assigned and can’t say I’ve noticed any strange behaviour. But maybe I’m not looking for the right thing. 
Can you please let me know where has this been discussed? 

If your Honeycomb Alpha Yoke with all the buttons assigned works correclty, without causing the heading bug to jump in 10-degree increment (intead of 1 degree) you are just lucky. This bug also causes trim jumping in big increments rendering it unusable. On top of that - altitude bug jumping in 1000 ft increments instead of 100ft.

Please search this forum, you will find several reports of issues with Honeycomb Alhha Yoke, and other controls using "always-on" switches.

Edited August 29, 20205 yr by Steku

I also have a Honeycomb, but I have not experienced any such issues either.

I also have a Honeycomb, and I HAVE experienced all mentioned issues too. It sucks, for a second after starting a flight I can change my heading 1° at a time, then its only every 10° and altitude no 100s. To be listed as a supported joystick and not have this fixed yet is shameful.

 

On 9/14/2020 at 12:14 AM, shadow133 said:

I also have a Honeycomb, and I HAVE experienced all mentioned issues too. It sucks, for a second after starting a flight I can change my heading 1° at a time, then its only every 10° and altitude no 100s. To be listed as a supported joystick and not have this fixed yet is shameful.

 

 

This problem happens when a button or switch that is mapped is constantly in a pressed state (Held on).

 

The Honeycomb has multiple on/off switches that could be bound to lights etc. However, whenever you do so, this problem happens. As soon as your release all buttons or switches from their constantly pressed state to off state things return to normal.

Another thing you'll notice is when you're in the settings for the controls, if one of the buttons is in a pressed state, and you press other buttons/switches... they will NOT flash like they normally do on the mapping screen. Nothing flashes while the pressed buttons stays lit.

I think this problem not only causes the 10/1000 intervals but also other problems such as forced full trims etc.

I don't have the honeycomb yoke but I have a home-made switch box and I use a Leo Bodnar board and same thing happens when I have one of the switches flipped to ON (lights). I can only use buttons that are momentary on/off for now. Not switches.

so either unbind those switches or use them as on/off meaning, use as toggle instead of set states.

 

Edited September 16, 20205 yr by n19htmare

Was this fixed in the latest patch?

57 minutes ago, Ianrivaldosmith said:

Was this fixed in the latest patch?

I do not control heading or altitude through the Honeycomb.  Heading still jumps by 10.  Altitudes always worked properly.

i always controlled trim through the Honeycomb and it never jumped uncontrollably- not an issue as far as my setup goes.

Not fixed, as a matter of fact a lot stopped working since last patch. The deal breaker for me now is that the AP immediately chases down the altitude selector on the CJ4, even when altitude is already captures. Its impossible to fly until they decide to hire a pilot to do some quality control and actually fix things.

BUG or FEATURE?

I don't have MSFS yet but from the various accounts I have read, I wonder if this is a feature, not a bug. In my cockpit I use rotary controls for heading bugs etc., and I program a SHIFT key to modify the behaviour to jump in 10-degree increments. In other words, if you hold down the SHIFT key while turning the knob, you get 10 degrees. If you don't hold it down, you get single degrees.

Knowing that this is a common idiom, I would suggest people search the MSFS menus and documentation to see if MSFS has such a SHIFT function, and then check whether it has been automatically assigned to one of the Honeycomb switches.