@FusedSpoon Are your units updated to the latest firmware, and do you need a specific “commandMapping.ini” What units are you using? I have the GNS430, GNS530, GFC500 autopilot, and the GMA350 audio panel, and everything works as it should, it is just the way you have to start the interface since SU9.
RSG mentions it is making good progress. Very good to hear! It will take a little while longer to iron out all the issues. So our patience is asked a while longer, but will be rewarded in the end.
I’m all for letting folks who are building this have the time and resources they need. With that in mind, I have been doing that with this sim for over two years.
CTD’s CHECK! Fix one thing, break 4, CHECK! Take my thousands of dollars in gear and render it useless, CHECK! Be told that it’s NOT THEIR PROBLEM? CHECK! That reason can only be that there is no money in repairing it. Just the facts.
So what thousands of dollars of gear do you have that is rendered useless? Just curious
RSG G1000 Suite. Home cockpit gear that is set up FOR the G1000 / Honeycomb gear. My cockpit panel has the units built in and three monitors in front. The way I use it now is without the G1000, no cockpit, just revert to using the 2D panels in the sim.
I don’t have the gear that you do, though some day I hope to, so it is hard for me to troubleshoot your situation. But did you try the way I start everything up, by manually starting the RSG interface AFTER you are loaded in the sim, sitting in the cockpit? I do have sim crashes if I am not in a flight with the RSG interface running, but if I shut down the interface before returning to the sim’s menus, then I don’t get crashes. It is a pain in the butt, but at least I’m able to use the gear until a permanent fix is available.
I get your pain, really I do. I can’t quite afford the G1000 suite, and what I do have I value as much as you do. But being offensive to the developers of the sim and of the gear doesn’t help get the problems fixed, nor does pointing fingers. Being cooperative and providing details on what you are experiencing and any information about how you might try to resolve the issues on your end, whether they are successful or not will help everyone to get closer to a fix. I’m sure Asobo is looking in to the matter, not ignoring it. They want us to have a good experience with our systems, especially since more and more of their customers are building home cockpits and elaborate systems, and if these simpits stop working, they will lose more and more customers. I’m quite certain they don’t want that. And since these issues with RSG, and other hardware came out with this SU9, I’m sure they are looking into it just as hard as RSG. Some of us beta testers did identify this issue as soon as the beta was made public. We didn’t miss it. It just hasn’t been resolved yet. I’m sure a fix will be available soon.
The workaround I am using is: 1.Start Task Manager. 2. Open Windows Explorer, go to your Community/Realsimgear/Bin folder and rename the Realsimgear.exe file ( I name it Realsimgear.exe.orig). This will stop it from launching automatically when you start MSFS. 3. Start MSFS, start your flight. Before takeoff…do step 4. 4. Rename Realsimgear.exe.orig back to Realsimgear.exe. Double-Click it and start Realsimgear. At this point, everything works properly for me. 5. When you finish your flight, use Task Manager to kill the Realsimgear program BEFORE you go back to the Main Menu in MSFS. I did this several times today and everything worked fine. A pain, yes, but it works until someone gets it fixed. P.S… I use the GNS 530. I can’t attest to any other hardware with this method. I have multiple monitors which is convenient for running task manager and Windows Explorer on a second or third monitor.
1 Like
I first made a backup of exe.xml, then edited the exe.xml and removed the RSG entry (this stops it from auto-starting with the sim). Then I start my flight. Once I’m in the cockpit I start RSG with the icon I have in my taskbar. Fly. Once I’m ready to leave the cockpit, use Task Manager to shut down RSG, then exit the sim as usual. This way I don’t have to keep renaming the file each time I fly.
Sounds good too. I know some ppl are not comfortable renaming or editing files. The point is…none of us should have to do any of this. For the $ we give them…stuff should work.
3 Likes
very true!
Nope. These are not facts, but an opinion. And that’s a fact. I am running an incredible amount of peripherals with no issues since logitech started releasing stable drivers in nov ‘20.
13 fips, 2 radio panels, multi panel, switch panel, backlit information panel, honeycomb alpha bravo, logitech rudder pedals, realsimgear gns430/530, gtn750.
I am bragging back a little to you to show that it’s in no way trash for everybody. The sim has always run smoothly for me.
My analysis: you are frustrated and fuming. That won’t help your situation. Many people here are willing to help you out if you have specific issues. Just post the specifics and most of the time there’s other simmers who know what to do.
1 Like
RealSimGear released a solution. I’ve posted it here.
7 Likes
I have the G1000 RSG suite and CTD continues with 1.6.1. Here is what I did:
Completely deleted my SSD drive (only one I have at moment). Reinstalled Windows 11 fresh. Updated my TUF Gaming x570-Plus Wifi Bios to latest stable, updated my Ryzen 9 3900X processor chip driver, all Windows updates and fresh install of MSFS 2020 Deluxe.
Starts and runs like a charm. No issues.
Plug in my RSG USB and power.
Ran RSG 1.6.1 setup. Displays are showing correctly.
Start MSFS 2020 - RSG Device Interface loads COM Ports 3,4,5.
This time I get to World Map (before it would CTD on load).
Press Fly and BAM. CTD.
Try again to load sim. MSFS starts, but RSG Interface does not recognize ports.
Flight loads.
Rescan and RGS loads and I can move the screens over.
None of the buttons work.
Quit MSFS. RSG interface stays connected and sim loads well again.
So, it appears more work is needed, as you said. Are the buttons working for you now?
Okay - quick update!
I shut down MSFS again, ended RSG interface in Task Manager, and then restarted MSFS.
All loaded fine. AND, all buttons working on RSG.
Fantastic! Perhaps the new 1.6.1 setup/driver needed to load twice. Who knows! It works for me now.
Thank you @GhostlyFrend for the update on 1.6.1 
1 Like
Thanks for the heads up. It was a pleasure to be able to play the com-channel for this issue 
.
Happy flights!
I updated my RSG driver to 1.6.1 last night and did a flight. The RSG interface autostarted with the sim and was running from the beginning. Usually when the sim got to about 75%, it would CTD as the RSG would scan for hardware. With this new driver, it continued to load. I was able to continue and do my flight with no problems at all. But when I finished my flight and went to the main menu I got the CTD. Definitely progress here. I will do a flight here shortly and see if I get the same result.
I can confirm after a quick spin that the new driver (1.6.2) is working for me. No CTD after going back to the main menu.
I concur. I’ve done several flights with several different aircraft and I set the RSG to autostart with the sim, and I get no CTD at all. Thank you so much RealSimGear for coming up with a fix. I just hope the SU9 hotfix that is in the works won’t break it again.
I’ve set the exe.xml to autostart rsg, but it doesn’t happen. I have to do it manually. What does your exe.xml say?
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type=“Launch” version=“1,0”>
Launch
EXE.xml
False
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
False
False
FSUIPC7
D:\MSFS_Addons\FSUIPC7\FSUIPC7.exe
-auto
False
</Launch.Addon>
<Launch.Addon>
False
False
TDS Sim Software GTNXi Gauge Integration
C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe
-FSIntegration
True
</Launch.Addon>
<Launch.Addon>
RealSimGear Add-on
False
C:\Users\N8598\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\RealSimGear\bin\RealSimGear.exe
</Launch.Addon>
<Launch.Addon>
FSRealistic
false
D:\MSFS_Addons\FSRealistic\FSRealistic.exe
</Launch.Addon>
</SimBase.Document>