Hi,

 

I hope everyone this doing well.

I recently purchased the GTNxi Pro version from TDS to fly it mostly with my flysimware learjet 35A. However, I have an odd issue, whenever I launch MSFS 2024, during the launch screen, always around 52% of loading the TDS GTNxi logo will pop up on screen and then everything will freeze and the only way to get out of it is to turn of the PC manually.

I really don't know what is happening here.

I reached out to TDS via their discord and their support was very reactive and kind but unfortunately, they couldn't solve my issue mentionning  that this issue could be linked to a bad install of drivers or even Windows 11.

I have reinstalled msfs 2024 completly, I have updated every single driver I could (even the intel gpu), I have updated my nvidia drivers using DDU... nothing has changed for this issue. In a last resort, I even wiped out everything and reinstalled windows 11 (that was not too much of a problem as my pc is dedicated to flight sim only), I let it to its vanillia state, updated all drivers and reinstalled the GTN... and... still the same issue. I have no idea what is going on.

I have been using all simulators since FS9 and this is the 4th time I built a pc dedicated to flight sim, so I consider myself rather sim/windows/tech savy but I never came across this kind of mystery.

If anyone has any idea regarding this issue, that would be highly appreaciated.

Here is the troubleshooting done so far:

- empty the entire community

- updating all drivers

- fix/reinstall msfs 2024

- update all graphics drivers

- whitelist the .exes in windows defender

- reinstall windows 11 pro

- perform a clean install of the GTN and TDS softwares (removing all Garmin and TDS hidden folders)

- remove any extra background programs and overlays

My systems specs

- Windows 11 Pro, lastest updates

- intel i7 14700k

- Gygabyte RTX 5080 OC (latest nvidia drivers)

- Gsync display, 1440p, 144 hz

- MSI B760 TOMAHAWK wifi (latest bios)

- 64 GB DDR5 RAMS

Thank you very much !

 

 

Anything in the Windows Event logs to give you a clue?

Hi Flyingscampi,

Nothing special at least related to graphics. I did some research with precise time stamps, but nothing critical, no warnings.

Thanks

 

How long have you been using the PC? A complete Windows lockup is rare without a hardware issue.

I presume you've stress tested?

 

The PC is about 1 month old. FurMark, Occt and Cinebench done. No problem, no overheating. I don't always need to reboot pc, most of the time is just a regular crash to desktop.

Also, if I bypass the automatic launch of the TDS plugin, by starting msfs 2024 first and then, start the plugin manually, everything works fine in the sim afterwards. Same if I start the plugin first and then MSFS 2024.

The problem comes when the plugin launch automatically with the sim. 

1 hour ago, matos64 said:

The PC is about 1 month old. FurMark, Occt and Cinebench done. No problem, no overheating. I don't always need to reboot pc, most of the time is just a regular crash to desktop.

Also, if I bypass the automatic launch of the TDS plugin, by starting msfs 2024 first and then, start the plugin manually, everything works fine in the sim afterwards. Same if I start the plugin first and then MSFS 2024.

The problem comes when the plugin launch automatically with the sim. 

I also presume this happens on a vanilla copy of 2024 with only TDS installed.

I doubt any two contributors to this forum have an identical setup and it sounds like you have found an anomaly. At least you have a work around!

 

1 hour ago, flyingscampi said:

bt any two contributors to this forum have a

Hey, that's true. It happens with a vanilla msfs and windows. Yes as you said, I have a work around, I can still enjoy the TDS, but it doesn't work for me like it is supposed to work and like it is apparently working for others. Which is frustrating. 😉 Finding the cause of this bug is more like a new challenge for me now 😉

Are you usuing the beta? Maybe SU2 might fix it...

Apps that start automatically when the sim launches usually do so through an entry in the exe.xml file. Might be worth checking if something corrupted that file. 

Might also change the order of load in the EXE.XML file and see if that affects it.

Here is my exe.xml file as a comparison:

<?xml version="1.0" encoding="Windows-1252" ?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>EXE.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>TDS Sim Software GTNXi Gauge Integration</Name>
        <Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
        <CommandLine>-FSIntegration</CommandLine>
        <NewConsole>True</NewConsole>
    </Launch.Addon>
</SimBase.Document>

 

When you check your exe.xml file, pay particular attention to make sure all the <  and > characters are present as shown above by Bert. A missing character will corrupt the file.
And don't ask me how I know!   😉

Al

Edited April 29, 20251 yr by ark

Two things stood out to me:

1) make sure the encoding of the exe.xml file itself isn't an issue.  I do not know if MSFS is that concerned about the encoding of that file, but it's always a possibility -- assuming there isn't an outright corruption or parsing problem as the others mentioned.

2) Another thought I had was to underclock the vidcard.  I noticed you have one of the OC versions, i.e. a factory overclock.  It's a longshot, but given everything else you have tried, it's worth looking at.  In your case it wouldn't really be underclocking the card per se, it would be returning it to the factory-standard setting for a 5080.

Thank you all for the support. Much appreciated. My exe.xml is exactly like the one shown.

 

Good idea for the graphic card, I will try to "detune" it.

Thanks all/.

I had this exact same problem. It would load in FSUIPC and the TDS app, and then lock up.

I assumed it was something wrong with the app, so I reinstalled it and FSUIPC, but no change. Finally I checked event viewer, and saw that the problem module was a dll in my Nvidia program nvngx_dlss.dll. I opened NVidia app and optimized the driver settings for 2024 and it fixed it.