MSFS2020 G1000 default controller profile empty

N4niner206

New member
Hello,

I just got two FlightSimBuilder G1000 units and have them configured as PFD and MFD. Most of my install has gone normally, but Im having an issue with MSFS2020 loading the controller profiles. Here is an overview of the setup steps I've done:

- Installed the latest (V1.15) FlightSimBuilder Launcher (Hub). Following install, I was prompted to further update FlightSimBuilder Launcher to V1.16, which I did. That all seems to have gone normally.

- The very first time plugging in the two devices, a firmware update was prompted. I unplugged each device and then plugged each G1000 in separately to allow the firmware to complete. This only happened the first time, and seemed to work fine and have not had to repeat those steps since.

- The two G1000 units are recognized as monitors and I have no issues popping out the displays from the aircraft - they look great. No issues there.

- I launch FlightSimBuilder Launcher and see "PFD: OK" and "MFD: OK". The drop-down boxes are also reflecting #1 as G1000 PFD and #2 as G1000 MFD. Sim Connection shows as "Waiting". (See "FSB Launcher.jpg" attached)

- I start up Flight Simulator. FlightSimBuilder Launcher recognizes "MSFS is running" and Sim Connection changes to "Is Starting". Note that it never goes past "Is Starting", but that may be normal. (See "Starting.jpg" attached)

- The first time MSFS2020 is run with the new devices plugged in, a message appears saying "A new controller device has been detected, but we were unable to set it up with a control preset. Go to "Customized controls" and create a custom control layout. For more information, please visit forums.flightsimulator.com" then lists the two devices in red with their appropriate names. (see "no default profile.jpg" attached). If I select "Keep Default", the profile is empty without any bindings. If I select "Customize", it creates a duplicate empty profile without any bindings that I can assign manually.

- When going to "Control Options" within MSFS2020, the two devices appear as "FLIGHTSIMBUILDER G1000 MFD" and "FLIGHTSIMBUILDER G1000 PFD" as I expected. However there are no assigned controls, the descriptions and graphics are blank. (See "empty profiles.jpg" attached)

- I did notice that when using "Dev Mode" "SimConnect inspector" function in MSFS2020, it seems to recognize when button presses and knob clicks are occurring. When pressing a button or turning a knob, the "Count" rapidly increases accordingly. This makes me think that the controller inputs are getting through. This is without any button bindings set. (See "simconnect inspector.jpg" attached). Additionally, it does seem that I am able to manually set buttons in the controls options, making me think that there is perhaps just a control profile missing for the devices?


Now, I've spent the last two days trying anything I can think of. I've uninstalled and re-installed various versions of FlightSimBuilder Launcher (V 1.12, V 1.14, V 1.15 and updated to V 1.16. All encounter the same issue. I've also taken the painful steps of uninstalling and re-downloading/reinstalling MSFS2020 to no avail. My results remain unchanged. A couple of questions...

1) Is there a way to just get some pre-built controller profiles installed?

2) Is it normal that the "Sim connection" status never goes beyond "starting"?

3) Could my issues be related to the firmware update that was prompted? If so, is there an easy/safe way to roll back to a previous firmware version?

I appreciate any help that can be provided... I'm really stuck and frustrated, but hope this is a simple fix. I recognize that there are other similar threads on here, but attempting the suggested remedies in those threads has not been successful for me.
 

Attachments

  • no default profile.jpg
    no default profile.jpg
    143.2 KB · Views: 2
  • fsb launcher.jpg
    fsb launcher.jpg
    108.8 KB · Views: 2
  • starting.png
    starting.png
    420.4 KB · Views: 2
  • empty profiles.jpg
    empty profiles.jpg
    278.9 KB · Views: 2
  • simconnect inspector.jpg
    simconnect inspector.jpg
    30 KB · Views: 1
Last edited:
For what its worth in case anyone else encounters this... it turned out that my Communities folder was missing the flightsimbuilder-wasm folder. I took a copy off my other computer and it fixed everything. If you encounter similar symptoms to what I described, highly suggest you make sure that folder is present, and - if so - consider re-installing the contents from a backup (if you can) to make sure nothing within it is corrupt/damaged. Good luck!
 
Back
Top