Hahaha it really does doesnt it.![]()
New controller detected: āMr Punchyā
Engage V.A.T.S.I.M. mode only to reveal you have a 0% chance to hit, and get a critical miss on your approach.
Where did you get the 150 drivers? When I get them of logitech site, its 124 thats installedā¦
I had lorby installed and the logitec driver. Uninstalled lorby and now the flight panels work again
I updated MSFS2020 to the latest, everything ok so far, notice the Saitek Flight Panels works without using the previous fix. They have incorporated the Logitech fix into the sim, no need of Lorby or Spad for this purpose, all switches in the Honeycomb yoke work fine for me.i will keep testing with more complex GA planes, I donāt do heavies.
Hello Can someone help me? my switch panel does not work despite being plug in. i start the game and start a flight, as soon as iām on the tarmac i start the plug in but nothing happens, no switch works.
did you download logitech newest firmware ?
Iāve installed the current driver / plug-in
Any news from Microsoft or Logitech on getting the avionics switch working?
Thanks, but its the one I used before. Found an FTP server full of old Saitek drivers, installed the latest and finally got my FIP on with ads! Thats the first time, after at least 5 hours of trying. Havenāt tested with MSFS yet, but Iām confident.
Worst workaround ever though - Iām VERY disapointed with Logitech support here!
Having installed the latest update for FS2020 and using the 8.0.281.0 plugin for my Logitech Multi Panel, I am still having problems with the HDG, CRS, ALT & CRS selector moving the display in 10 or 1,000 increments (rather than 1 or 100)ā¦
One thing to mention is, when I start FS2020 up, and select my airport and aircraft to fly, and click on the yellow Fly button, it takes me to the airport, and at that point, my selector works in 1 and 100 increments, so everything looks perfectā¦
But, there is still a final yellow āLetās Flyā button to hit (which puts you in the cockpit), and after I hit that one, the selector then changes from working correctly to then going back to changing the display in 10 and 1000 incrementsā¦so something is happening between the initial fly screen (where you arenāt in the cockpit yet, and it works great), to going into the cockpit, and the issue appears at that stageā¦
Oh, and i am using my Logitech Multi panel in conjunction with a Honeycomb Alpha Yokeā¦
Any thoughts please?
Thanksā¦
Maidens1 you have saved me!! 8.0.150.0 is exactly what I needed. I was previously running 8.0.281.0 with only my Switch, Multi, and Radio panels working. Now with 8.0.150.0 my FIPs now work without any third party addons. Now I can get busy customizing them. Thank you so much for this link. Now we just need MSFS to make available the G1000 softkeys and associated knobs⦠fingers crossed!
You are welcome, it was good fight! ![]()
I have exactly the same problem. When I change to another plane and then back again, it sometimes works.
I havenāt tried switching planesā¦Iāll see if that makes a difference, thanks
Hi,
When I start up any plane, the multi panel doesnāt display any valves, it only shows the letters. I also canāt change any AP functions! The only way I can get it to work is if I start a flight from the runway with the plane already started automatically! Had anyone got any suggestions on how to fix this issue?? Thanks in advance!!
Let me repeat this, I have the latest MS patch installed, I have no special driver or software for my Saitek Flight Panels (Multi, Switch, Radio) I place myself @ KBOI in a SR 22, ALL my panels are lit up, change Altitud, the Garmins shows it, change Frequencies, the Garmin shows it, I turn everythin OFF, Panels go off. I turn everything ON with my Saitek Switch Panel, everything is ON again. The drivers are inside the Sim.
Yesterday I flew for 2 hours under the same circumstances. So what is going on?
Before patch #2 my Saitek Radio panel would work anytime the battery switch was on after starting cold & dark.
After patch #2 it no longer works if I start cold & dark. Even after I manually start the engine it still does not work. I discovered I have to use the engine auto-start (Ctrl-E).
After that it seems to work fine and works like prior to patch #2. I havenāt gone much further then this so I donāt know if anything else adverse happens over time.
It also works fine if I start on the runway with the engine running⦠I suppose since this is basically an engine auto-start process.
Iām going to submit a bug on this⦠but at least there is a workaround.
Edit: so far this only seems to affect the C152 planes.