G1000 Hardware. Issues with MSFS2020 and MSFS2024

Pelmo

Pelmo

New member
Hello everyone,

I am experiencing persistent issues with my Flightsimbuilder G1000 hardware setup, and I’m hoping someone can help. Here are the details of my setup and the problem:

Setup​

  • I own two G1000 units: one configured as the PFD and the other as the MFD, along with the central Audio Panel module.
  • All three devices are recognized by my system.
  • I installed the drivers using the latest version of the Flightsimbuilder Launcher (v1.13.0). When I launch the software, it confirms that all devices are connected and marked as "OK."
  • I use both MSFS 2020 and MSFS 2024, but the hardware only works reliably with MSFS 2020.

The Issue​

Most of the time, after starting the Flightsimbuilder Launcher and launching MSFS 2020 or MSFS 2024:

  1. I load an aircraft with a G1000 (e.g., the DA42 by COWS), place it at a parking spot, and enter the cockpit.
  2. I use the ALT GR + left mouse click combination to place the PFD and MFD screens onto my hardware.
  3. Once I power on the G1000 using the master switch, the hardware often does not interact with the simulator. None of the buttons or knobs on the hardware work.
In approximately 6–7 out of 10 attempts, I encounter this issue. To resolve it, I have to exit the simulator, return to the desktop, and either reboot or fully shut down my PC. A simple restart is often not enough.

Attempts to Fix​

  • I have formatted my PC and performed a clean installation of the operating system, but the issue persists.
  • I have uninstalled and reinstalled the Flightsimbuilder software, removing all related folders before reinstalling, but this didn’t help.
  • I installed FSUIPC7 as recommended to better manage peripherals in MSFS 2020/2024, but I have not configured it since I am unfamiliar with its use.
  • I checked the FSUIPC7 log file and found a "WARNING Joystick ID is duplicated in Registry" for the MFD (Joystick ID = 7) and my Thrustmaster HOTAS Warthog throttle (Joystick ID = 6). I suspect this duplication might be causing the problem, but I don’t know how to fix it.

Additional Info​

I have attached a screenshot of the FSUIPC7 log file showing the warnings for duplicate Joystick IDs.

Questions​

  1. Could the duplicate Joystick IDs in the registry be causing the issue? If so, how can I resolve this?
  2. Has anyone else experienced similar problems with Flightsimbuilder hardware and MSFS 2020/2024?
  3. Is there a way to configure FSUIPC7 to prevent conflicts between peripherals?
  4. FSUIPC7.log.jpg
Thank you in advance for your help!
 
Hi Pelmo,

Thank you so much for providing all of the details — they’re really helpful. We’ve noticed that a small number of users are experiencing issues with MSFS 2024. As we investigate whether this is a bug within MSFS 2024 or something that requires an adjustment on our end in the launcher, the information you've shared so far is invaluable.

Could you also provide a log file from the Launcher? You can find it in the following location:
%LocalAppData%\FlightSimBuilder\FlightSimBuilder Launcher
Just copy and paste this path into your File Explorer to access the log.

Lastly, could you try one more test for us? Please launch MSFS 2024 first, start your flight, and then launch the FlightSimBuilder launcher. Let us know if that resolves the issue.

Thanks again for your help!
 
Thank you for your response and suggestions.

I’ve conducted four tests based on your advice, and here are my findings:

  1. First Test:
    I launched the FlightSimBuilder Launcher first. I clicked on “Install Again,” then “Configure Again,” and finally selected MSFS 2024 before launching the simulator. Surprisingly, once I was at the ramp and ready to start the flight session, the G1000 hardware worked perfectly for the first time. I conducted a test flight around the airport, and both the PFD and MFD functioned without any issues.
  2. Second Test:
    I followed the same procedure as above but selected MSFS 2020 instead. Once again, everything worked without any problems.
  3. Third Test:
    Following your suggestion, I launched MSFS 2024 first. After loading into the ramp and getting the aircraft ready (with the G1000 hardware not functioning initially), I launched the FlightSimBuilder Launcher. This time, the hardware started working as expected.
  4. Fourth Test:
    I repeated the same process with MSFS 2020 (launching the simulator first and starting the flight session before launching the Launcher), and the hardware functioned correctly in this scenario as well.
Based on these tests, it seems that the most reliable method is to launch the simulator first, start the flight session, and then open the FlightSimBuilder Launcher when the aircraft is ready on the ramp. I’ll continue testing in the coming days, but for now, I plan to use this sequence to ensure consistent functionality.

I’ve attached the requested log file for your reference.

Thank you again for your help, and let me know if there’s anything else I can assist with!

Best regards,
Pelmo
 

Attachments

Thank you for the update. It looks like maybe it wasn't initially installed for both MSFS 2020 and MSFS 2024 and that was the reason it didn't work in MSFS 2024. We will try some additional testing to see if we can recreate it.
 
I am having the same issue. I just don't have 2024. But when I start 2020 I can pop out the screens but the buttons and knobs do not work. Everything was fine prior to the latest update. Like you said, the only thing that will fix it (sometimes) is a reboot. I will try starting MSFS first then load the FlightSimBuilder Launcher to see if it will fix the issue.
 
You must log in or register to reply here.

Similar threads

F
COMM panel lights and button
Replies
3
Views
33
Administrator
Administrator
E
Titlebar remover tool for popout windows
Replies
2
Views
50
eiketre
E
Administrator
Forum is now Live!
Replies
2
Views
44
Administrator
Administrator
T
FSB GNS 530 3D Printed stand STL query
Replies
1
Views
21
Administrator
Administrator
Back
Top