well, my Saitek rig is recognized by Windows, in Xplane everythings works fine. Do i need special driver setup for msfs, if yes, may i asked for a valid link?
Youâll want to start at this link, select each product, then click support, then downloads. I recommend you click âshow all downloadsâ to make sure you get the latest 64 bit driver, I donât really trust the âdefaultâ download it shows in some cases, you need to see all of them to pick the correct latest. Some of the links donât take you right to the donwloads, you just have to search a bit, I think the yoke driver is a bit hidden, but you can always ask for a specific link and I can find that.
I specifically got a PCIe USB 3.1 expansion card with 4 slots, each with a dedicated USB controller for this reason. The UI for the expansion card makes disabling power management a breeze.
Look at my program list, Microsoft flight sim plugin and Direct output are the ONLY two you need. Direct output is the older version of Microsoft flight sim plugin. Notice the versions. If you need help finding them let me know. You need to try to uninstall all third party apps besides these two. Even the ones for XPLANE. they are fighting each other.
Just got my computer back from repair and also having to reinstall again so havenât had a chance to check if Logitech has released its Pro Flight panels driver update for FS 2020. Has anyone got these â â â â â â things working without having to rely on third-party utility gimmickery?
its best to start from scratch⊠uninstall all drivers⊠remove all devices. then install the two drivers. Microsoft Flight sim Plugin and Direct Output then plugin your devices one at a time until you see them recognized in devices. reboot and make sure they all show up in devices before starting MSFS 2020. DO NOT CHANGE USB ports once working. it causes issues. I hope this helps. I went through some very frustrating times getting these to work. I feel your pain!!
You all may be right, I did see the Dev post this before:
âDirectOutput is needed for the Flight Instrument Panel only. If you have one of those then you will need to also install the drivers from the support page . The other panels donât actually require any drivers.â
Dunno. I have the drivers loaded, but I always have (for FSX) and updated them as need. Everything works fine for me. Hope he gets it worked out.
You may be right there. I actually have 4 FIPâs may have been why I added direct output. Those times of troubleshooting and trying different things were so frustrating lol. All panels are working âgreatâ now. Kind of⊠some work arounds with the avionics switch, but looks like they are going to fix that with next update.
Also, Note here that he mentions PANELS donât require any drivers. So Iâm still saying the yoke, pedals, and throttles probably need the drivers.
Hi All,
Yes, I was talking purely in the context of the panels. If you have the Yoke, rudder pedals, Trim wheel etc. then you should install the drivers for those items. I donât know why @kleinekrabbe20 is having the issue he is when everything works in X Plane (so we know everything is fine). Does MSFS detect buttons/axes etc. when you try and reassign them in the options screen?
Re: the Multi Panel increments issue I was speaking with the Honeycomb team at the weekend and theyâre looking into this on their end as well. If I hear anything further Iâll let you know.
Appreciate you keeping us updated on this!
Still canât get radio panel to work in the A320 it seems to work in GA planes but not the airliners, any suggestions on possible fixes? Mars online flying a bit harder
Itâs strange as transponder works but as soon as I try and dial a frequency in com, I get nothing
Only in the A320? Could be also due to bugs as this oneâs affected pretty heavily. Did you try the A32NX Mod? I use it and have no issues with the radio panel.
I will try other airliners shortly, but yes the flybywire project, ive been using since the day it became available
I have finally got MSFS to recognise my multi and radio panels plus my FIP. However when I start MSFS they al show up and immediately disappear. The same lines appear in the ICMlog every time but it has me beaten at the moment.
It is
"10:42:00 Status=700 TCP FSX/FS2020/ESP/P3D TCP Setup & Initialization
10:42:00 Status=701 TCP Create socket OK
10:42:00 Status=701 TCP Derived FS-SC Endpoint IPAddr=127.0.0.1 Port=500
10:42:00 Status=701 TCP Connecting to FS-SC TCP ServerâŠ
10:42:02 Status=701 TCP Connect to FS-SC Server failed 10061 WSAECONNREFUSED
10:42:02 Status=701 TCP Interogate Registry for FSX SC Local Port#
10:42:02 Status=701 TCP Read Local FSX SimConnect Reg Key failed 2 No connection could be made because the target machine actively refused it.
10:42:02 Status=701 TCP Abort on initialization failure - TCPrecv inoperative
10:42:02 Status=957 ICM Initialize TCPrecv failed 1 0 ICM terminating 0
10:42:02 Status=957
10:42:02 Status=957 ICM TERMINATION exit on error or test mode
10:42:02 Status=957 ICM exit processing - flags exitstg=0 w32exit=0 exitflag=1."
Any help would be greatly appreciated.
Hello,
Am I the only one struggling to light up the panels in some planes like the Longitude & A320 for example from a dark & cold cockpit ? When Iâm flying from a runway itâs working because everything is already up and running but when Iâm from a GATE cold & dark itâs never displaying whateverâŠ
Any tips guys ? ![]()
Thanks !
I had to go to the controls page and set up a button for Avionics 1 ON. I think we are all having the same issue. Let me know if you need more detail on how to do that exactly
You may check your Windows internet access permissions.
I use SpadNext and that solved all my problems. I use the radio panel, the multipanel and the switch panel. They all work as intended and with all the aircraft. I tried in the past on all the other sims with the Logitech software and it didnât work. The same problem happens with MSFS. Make yourself a favor and use SpadNext. It will get rid of your problems. ![]()
Iâve been using it for ages, with XP, and now this.

