I have all taken from the beginning:
I run MSFS2020 the panels are powered on.
once MSFS lace up I launch a flight
in a CMD window launches it from the plug-in installation directory the command LogiMicrosoftFlightSimulator.exe -r.
nothing happens, I then do LogiMicrosoftFlightSimulator.exe -r -f ditto
in order to validate the operation of the panels, I run the LorbyAxisAndOhs_MSFS program all working
I specify that the original installation of MSFS was done by DVD and not steam
Thanks for your help
Thanks a lot for letting me know! I am indeed running an honeycomb yokeā¦ Iāll try to unbind all the switches and give it another try!
1 Like
Altitude should adjust in steps of 100. If itās doing anything else then you may have changed the step parameters with another program (for example, SPAD can do this I believe). The panel just displays what Flight Simulator tells it to so the glitch is most likely an issue with the data that itās getting from SimConnect. You should report that to MS/Asobo.
@PrecastApollo69 Installation source shouldnāt matter - as you can see from the status readout we still install the plug-in where we need it to be. Weāll look into what might be causing the plug-in to prevent running for you and get back to you if we find any potential answers.
Itās almost certainly down to them using a Honeycomb yoke. If so, itās a known bug.
Yeah I thought that was causing the altitude adjustment to go the other way - adjusting in the 1000s. Can it go the other way as well?
Yes youāre right the only solution is to unbind all the switches (the ones located to the body not on the yoke itself) and bind them again by using FSPCUI7
It seems to affect both the HDG bug, CRS for all I know but I havenāt read anyone report that, and ALT in 1000ās rather than 100ās. Iāve taken to calling it the x10 bug.
No, I mean Multi-Instrument LCD panel, that displays many different gauges (speed, altitudeā¦)
Did you install the driver for the Instrument Panel from the support site? Itās the one panel that does need a driver installed - all the others do not.
Ok. Now everything is working. Thank you
Yes, but still black screen.
Have you tried different USB ports?
Wasnāt there a USB2 only constraint on the FIPs? Iām sure I read that somewhere.
1 Like
Maybe this could help with black screen problems.
1 Like
No, itās never that straightforward, to be honest. USB implementations are definitely not all created equal due to the huge number of combinations of different MOBOs and components and then PSUs that can be running them. Itās entirely possible to find instances where a device will work better on a USB 3.0 port than a USB 2.0ā¦ and vice versa.
Then add USB hubs or PCI USB cards into the mix and it gets even harder to track!
DarkAngelās tip might help as well.
1 Like
Yes. I tryed different USB and black screen registry fix too, but still the same. Multipanel is working awesome, instrument panel is black 
Yeah, Iām having the same issue with the instrument panel. Iāll experiment more tonight.
When the plug-in isnāt running does the FIP display the different Flight products or is it always blank? If itās always blank then somethingās wrong with its installation.
If you go into Device Manager, click the View button at the top and change the view to Devices by container, does your Flight Instrument Panel device have all the same entries as this?
1 Like
Iām aware that wrong DME should be a simulator issue more than a driver problem. Altitude now is OK (steps of 100) and HDG and CRS are perfect in steps of 1 degree.
Itās another world with panels working, I couldnāt fly without them anymore.
Thanks
I am assuming from your message that you had HDG, ALT & CRS issues with the selector only adjusting the display in 10ās and 1000āsā¦can I ask how you fixed this please?
Thanksā¦