ArturDCS is already thinking ahead to the MultiPanel. As this was designed to emulate civil aircraft, we're looking at how best to apply it to DCS modules. You can use several panels of the same type and have different mappings on each except Radio Panel which is fully programmed by DCSFlighpanels Rightmost number on lower LCD row (0x0-0x9, 0xA above will darken the digit position, except 0xEE which will show a dash) Is there something I have missed? Please help, no fun flying now that I have gotten used to my setup… EDIT2: After some googling I came over another device driver and tried it. It seems to work: https://drivers.softpedia.com/get/KEYBOARD-and-MOUSE/LOGITECH/Logitech-Flight-Instrument-Panel-Driver-8-0-124-0-64-bit.shtml

Restarted computer between each attempt, all different combinations of uninstalling drivers, unplugging FIPs before driver installation etc. Use the left rotary encoder or the S5/S6 buttons to show another card on various tabs or zoom into the galaxy map.I just upgraded to a new PC from an old where everything worked fine and for some bizarre reason, the FIP panels are not recognized by Windows on my new PC. Tried to create this panel, for controlling MFD. Activate Developer Mode : Chrome -> "Settings" -> "More Tools" -> "Extensions", and move the "Developer mode" slider in the top right corner. b]Close down DCS, delete all logs under C:\Users\\Saved Games\DCS\Logs => restart DCS and post dcs.log and dcs-bios.log Open DCS Script folder [drive:\Users\\Saved Games\DCS\Scripts]. Create it if it doesn't exist.

SOLVED: Did a clean install of Windows and they work now. First installed the latest Driver from 2017 and then the MSFS plugin. The Switch Panel functionality has been great from the get-go and remains so. He has already released a version of FlightPanels that precludes the need of a special driver and we now have use of the LED indicators. :thumbup: Leftmost number on lower LCD row (0x0-0x9, 0xA above will darken the digit position, except 0xEE which will show a dash) DCSFlightpanels communicates with DCS using DCS-BIOS, the brainchild of [FSF]Ian. [FSF]Ian has been very helpful in answering questions and helping out during the development process. His contribution to DCS will change the user experience from now on for a lot of us. If you get the chance then say "thanks" and give him some positive rep!

Compare up to 4 products

EDIT: I have powered HUBs, both USB2 and USB3. I also started Spad.next as administrator. The only warnings Spad.next displays is about the missing device drivers. And now for The Big Kahuna -- The Saitek Radio Panel. :) ArturDCS has functionality working for the A-10C AM, FM and ILS radios. We're still testing and working out bugs, but it's going to work! I think ILS landings will forever be a part of my missions now (kind of been ignoring that in the Warthog). Edit: This was just to note progress. Other radios, e.g. UHF, and other modules are being worked on. DCS-BIOS, if you are using DCS-BIOS then make sure the setting DCS-BIOS json location points to the correct folder. Usually the default setting is correct but if you are using DCS openbeta then you will have to change this.

Any data from HWInfo can (optionally) be displayed. This also works when Elite Dangerous is not running. There is a Toggle Window menu option in the tray icon context menu. This option mirrors the FIP display, that is being controlled by the HOTAS hat switch, to a window for use in VR. Toggle between 15 different displays, or utilize additional units to create a larger configuration which simultaneously displays multiple panels. Twin dials and a set of hotkeys simplify switching between various readouts. I have the pleasure of working with ArturDCS as a tester on his FlightPanels V2.0 project. As was mentioned in earlier posts, he is now making use of DCS-BIOS. The progress is exciting and I'd like to give users a heads-up of what's coming (with ArturDCS's permission).When I start Spad.next, it says “The FIP with Serial MZXXXXXXXX could not be found. This is most likely because the Saitek FIP Drivers are not installed.” It displays this message for each of my 6 FIPs. The other Logitech products work fine.

Related: