Saitek Flight Panels

I have not heard any comments from Logitech, Alpha, Asobo or MSFS. Are they ignoring that there is an issue? There are thousands of these panels attempting to be used with this software. This is NOT a minor issue.

This is the first time we’ve decided the game manufacturer should be responsible for all the peripherals. In the past, the peripheral manufacturer was the one responsible for drivers and programs to enable their products. Let’s get after Saitec and GoFlight about this; not Asobo. Let’s push on Asobo to get the SDK and SimConnect working so the manufacturers can do their job.

1 Like

Just to put the record straight.
Saitek/Logitech are not to blame here! They have already released new drivers for the panels [switch, multi and radio] that enable them to work perfectly with MSFS 2020.

The problem is the Honeycomb yoke, or more specifically, the drivers for it.
These drivers leave switches permanently ā€˜polling’, and it is this that is interferring with the operation of other periferals!

The panels work just fine!

2 Likes

Hi again - from the above should I take it that even if I were to try SPAD.NEXT then I will not be able to use both my Saitek Radio Panels together (which is what I would like to do)?

If the problems for Saitek panels (of any form - i.e. FIPs or Radio or Multi or Switch) are all caused by the Honeycomb Alpha yoke, then SPAD.NEXT would not necessarily help me out?

Thanks in advance again, Alasdair

Hi.
To be clear, I can only vouch for the proper operation of the multi, switch and radio panels in conjuction with the Saitek/Logitech yoke.
However, as far as I know, the AFC Honeycomb yoke is the only controller causing any problems.

To try to answer your specific questions:
I have never tried to use two radio panels concurrently, so I did not know that this was problematic until you pointed it out! Assuming that you are using the latest drivers,
eg. this:

https://download01.logi.com/web/ftp/pub/techsupport/simulation/MSFS_Plugin_x64_Software_8.0.290.0.exe

I cannot suggest anything. Although if you look for a link to ā€˜Tr1cky’ [in this thread] you might contact him and let him know.

As far as SpadX being the solution to this, again, I don’t use it so I don’t know!
I do know that you can ā€˜trial’ SpadX before you buy it. Perhaps you should check out their forums to see if this is a known issue.

To sum up then:
Download and install the latest drivers and see if that ā€˜fixes’ it.
Contact Tr1cky and see what he has to say.
Check out the SpadX forums for a possible ā€˜fix’.
Try SpadX out to see if the two radio issue is ā€˜fixed’.

I am sorry I cannot be more …directly helpful here.
Post back here and let us all know how you get on.

Regards.

I checked last night and I am running the latest drivers provided by Tr1cky.

For the most part my multi-panel works fine. Occasionally it will lock up and become non-responsive. I’m not sure if that’s a disconnect between the multi-panel and Simconnect, or the MSFS software itself.

Running two radio panels has always been a problem, but when I run one it seems to be okay, with only the occasional glitch.

Although I now have the Honeycomb Bravo throttle quadrant installed, I expect to continue to use the multi-panel more often than not. The advantage of the backlit LEDs and the large display makes the autopilot functionality on the bravo throttle the inferior choice. Not to mention the text is so small on the throttle quadrant that I can barely read it while flying. Still, the throttles work a treat.

Jim-Sim

1 Like

Hi Jim-Sim,

Thanks for the info.

I’m glad in a way that I’m not the only one having problems trying to run two Saitek radio panels!

I have the Bravo TQ coming soon - well, that is assuming deliveries continue now they have at long last started - latest news I have from Amazon.co.uk is that it is now expected to be 23 December (was originally told it would be late October).

Did you also have to remove the mapping of all the switches on the TQ to get the Saitek AP alt and heading increments to behave?

Regards, Alasdair

No, so far I’ve just been flying to places 10 degrees at a time. :grin: (kidding)
But I haven’t unbound anything on the Alpha or Bravo yet… I kinda see that as a last ditch effort. It’s not that big of a problem for me.

I’m hoping that Honeycomb get their act together with the next release (which includes LED implementation on the Annunciator panel). Honestly though, I’m not holding my breath… the first implementation of the Bravo Presets was horribly wrong… they should be embarrassed. I assume Honeycomb has some oversight of the preset that Asobo includes in the release updates. If not, then it must be some third-grader at Asobo that set up the default. I mean, even the engines were backwards (2-1 instead of 1-2).

But then again… in the last update, Asobo messed up the keyboard arrow key bindings for the cockpit camera… which was working correctly since the beginning. It’s almost like there’s nobody actually checking things out before they hit the button to publish the updates. Three steps forward, two steps back.

Jim-Sim

Got an eye on the Logitech Switch panel, just wondering if this issue was resolved or should I hold off on the purchase?

I have a single Radio Panel, and I’m the running MSFS Plugin 8.0.290.00. Everything is working correctly except ADF tuning. I can change the 100’s digit, as well as the decimal digit, but not the two in between. Is there a fix for this issue?

I also have an Alpha Yoke & Bravo throttle, could they be causing a problem due to the ā€˜always on’ buttons?

If you are using a Saitek/Logitech yoke all the panels [Switch, Multi and Radio] are
working fine. If however you have an Honeycomb yoke, I would hold off until AFC fix the drivers for it.

I believe that the current Logitech driver does not support 2 radio panels, maybe if you use them in different positions all the time, not sure. X-Plane uses a driver written by Sparker that allows the use of 2 radio panels, this I’m sure, because the original Saitek drivers did not support 2 of them. I find that when using PlanG or Littlenavmap you can set your frequencies from the map, they will do it for you, making the use of 2 radio panels less important.

Thanks. Decided to go for a streamdeck instead, those Logitech modules are out of stock.

Anyone notice a loss of performance in the simulator when installing/using the radio panel? I’ve read reports of some people getting stuttering when the plug in the panels…

I don’t see how you would replace the radio panel with the stream deck, those are just switches for commands you pick. Unless I’m totally wrong.
The sim helps a lot with frequencies, also Littlenavmap and PlanG, they would even set your frequency for the ILS, so maybe the radio panel is not that important in MSFS2020

I don’t have any issues like that with any of the Saitek panels.

1 Like

Fairly certain it’s doable since I’ve already mapped basic radio controls to the throttle, digging into the Comms controls menu in-game there looks like a fairly broad range of inputs to bind.

Nope. No stutter.

Jim-Sim

1 Like

I have no problem using the switch panel.

1 Like

My Saitek switch panel pretty much works. My comm panel lights up. Dial rotates frequency numbers but they won’t switch over to active (on left). Saitek Yoke, rudder pedals and Cessna trim wheel all work. CHThrottle works good too.
My GoFlight MCP and 2 switch panels (all from FSX days) are terrible (with GoFlights latest drivers and Spad.next). Tried to map in Spadnext but didn’t seem to take. Perhaps I’d have better luck using FSUIPC7 instead of Spad.