Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

1.7.14.0 + FSUIPC = fix for Honeycomb 10-deg hdg + trim

Featured Replies

As the 1.7.14.0 patch fixed the simconnect, FSUIPC 7 beta now seems to be working without causing massive FPS drop. This means FSUIPC can be used for assigining 2-position "always-on" and 5-position magneto switches on the Honeycomb Alpha Yoke or any other control device using "aways-on" switches. If such switches are assigned via FSUIPC and not via the sim buttons assignments menu, the following issues can be eliminated:

  • heading bug jumping in 10-degree increments/decrements (instead of 1-deg)
  • altitude bug jumping in 1000 ft increments/decrements (instead of 100 ft)
  • and most important: exaggerated elevator trim inputs, making the plane barely trimmable.

Using FSUIPC also allows setting:

  • taxi lights on/off
  • landing lights on/off

commands which are non-fuctional via the the sim assigments menu (a bug in the sim).

FSUIPC also gives much more calibration options for the axes compared to the crippled calibration/sensitivity interface of the sim (especially for the controls like brake pedals, without the center position).

FSUIPC can normally handle 32 buttons (the limit of the Windows API), LUA script must be used to assign buttons above this limit - in the case of the Honeycomb Alpha Yoke:

  • magneto left,
  • magneto both,
  • starter,

are above the limit. Here is the instruction how to use the LUA script (no programming required):

https://forum.simflight.com/topic/90277-input-from-buttons-32-127-not-recognized/?tab=comments#comment-546980

The momentary switches on the Alpha Yoke itself (the moving part of it = the actual yoke) can be still assigned within the sim itself (without causing the 10-deg/trim issue), especially to handle the views, as the FSUIPC is not yet capable to handling all the view options introduced in the MFS 2020.

Edited by Steku

  • Replies 35
  • Views 9.1k
  • Created
  • Last Reply

Nice, I wish I knew how to do it though! I’ve an alpha yoke, and short of assigning buttons in MSFS menu, I’ve no idea how to do all of that stuff above! 

Edited by Ianrivaldosmith

Good news! Happy for you guys who have the honeycomb. Just want to say, though, that I have successfully bound and used the taxi and landing light switches on my x52 since launch. It works fine, and so do the navlights, strobes etc etc. Maybe it is a Honeycomb specific issue?

Andreas Stangenes

http://www.youtube.com/user/krsans78
Add me on gamertag: Bullhorns78

Actually I don't have this issue any more in 1.7.14. It seems to be fixed.

  • Author
28 minutes ago, Andreas Stangenes said:

I have successfully bound and used the taxi and landing light switches on my x52 since launch. It works fine, and so do the navlights, strobes etc etc. Maybe it is a Honeycomb specific issue?

In my case the nav and taxi on/off assignments are not functional via the sim button interface. Are you using "on/off" commands (non-functional) or "set" command (which works properly in my case, but I wanted to have taxi/nav lights on separate Saitek Throttle Quadrant with momentary switches - set command not suitable, on/off needed instead).

Edited by Steku

  • Author
18 minutes ago, RALF9636 said:

Actually I don't have this issue any more in 1.7.14. It seems to be fixed.

After applying the patch I still experience the 10-deg/trim issue (tested in C172 classic) on Honeycomb Alpha Yoke, if any commands are assigned to "always-on" switches in the sim interface. By the way, FSUIPC provides so much flexibility when it comes to buttons, axes calibration etc. - I will use it instead of the in-sim assignments. 

Edited by Steku

3 minutes ago, Steku said:

After applying the patch I still experience the 10-deg/trim issue (tested in C172 classic) on Honeycomb Alpha Yoke, if any commands are assigned to "always-on" switches in thrle sim interface. By the way, FSUIPC provides so much flexibility when it comes to buttons, axes calibration etc. - I will use it instead of the in-sim assignments. 

Strange, I didn't have the issue anymore in the C152. 

Sure, nothing against FSUIPC. Glad we can finally use it.

17 minutes ago, Steku said:

In my case the nav and taxi on/off assignments are not functional via the sim button interface. Are you using "on/off" commands (non-functional) or "set" command (which works properly in my case, but I wanted to have taxi/nav lights on separate Saitek Throttle Quadrant with momentary switches - set command not suitable, on/off needed instead).

ah, no I am using the toggle function actually. 

Andreas Stangenes

http://www.youtube.com/user/krsans78
Add me on gamertag: Bullhorns78

4 hours ago, Steku said:

As the 1.7.14.0 patch fixed the simconnect, FSUIPC 7 beta now seems to be working without causing massive FPS drop. This means FSUIPC can be used for assigining 2-position "always-on" and 5-position magneto switches on the Honeycomb Alpha Yoke or any other control device using "aways-on" switches. If such switches are assigned via FSUIPC and not via the sim buttons assignments menu, the following issues can be eliminated:

This is great news. I also just posted an issue about not being able to get the taxi and landing lights to function reliably so perhaps this was the issue. 

NOW I just need to find the right tutorial on how to do all this again as I've been away from FSUIPC since v4 back about 10 years ago. It all looks extremely complicated to my older brain now. 

i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.

8 hours ago, RALF9636 said:

Actually I don't have this issue any more in 1.7.14. It seems to be fixed.

The issue is back again, no idea why it was gone yesterday.

So I will also use the solution via FSUIPC.

On 9/3/2020 at 3:14 AM, Agrajag said:

This is great news. I also just posted an issue about not being able to get the taxi and landing lights to function reliably so perhaps this was the issue. 

NOW I just need to find the right tutorial on how to do all this again as I've been away from FSUIPC since v4 back about 10 years ago. It all looks extremely complicated to my older brain now. 

Did you figure it out? I am trying to, having never ever used FSUIPC ever......

1 hour ago, Ianrivaldosmith said:

Did you figure it out? I am trying to, having never ever used FSUIPC ever......

Nope. Tried and failed. Not the most intuitive product ever released. It's an extremely useful product, once you get past how it works.

i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.

6 minutes ago, Agrajag said:

Nope. Tried and failed. Not the most intuitive product ever released. It's an extremely useful product, once you get past how it works.

Currently loosing the will to live whilst I battle through it now......

17 minutes ago, Ianrivaldosmith said:

Currently loosing the will to live whilst I battle through it now......

I tried simply using FSUIPC to take over the ALT and BAT switches and thought I had it, but they didn't work. Worse, I couldn't get the back tow working as before until I told FS to re-use the default setup for the Alpha.

i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.

3 minutes ago, Agrajag said:

I tried simply using FSUIPC to take over the ALT and BAT switches and thought I had it, but they didn't work. Worse, I couldn't get the back tow working as before until I told FS to re-use the default setup for the Alpha.

I have managed to set it all up in FSUIPC now, I just cant get the extended lua script to work for the buttons passed 33+ 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.