01-21-2024, 01:16 AM (This post was last modified: 01-21-2024, 01:33 AM by TacomaSailor.)
In all the aircraft using GTN750NXi I see the correct bezel and knobs but a black screen. I am a long time user of the TDS GTN stuff. The A2A Comanche, JPL 152 and Cessna 414AW were both working perfectly with the TDS 750 the last time I flew them - probably just after New Years.
I've attached a screen shot of the WASM debugger
TDS GPS manager says I am current at version 1.0.3.7 for the sim and 3.6.4.0 for the trainer.
When in the sim/Dev Mode I see that two TDS packages are mounted and registered:
tds-gtnxi-gauge (version 1.0.11) and tds-gtnxi-jpl_c152 (0.1.0 ). Here
Here is the log from the TDS module during a flight with the JPL C152 and a black GTNXi750 screen:
[19/01/2024 15:00:05.670 00002578 INFO] TDSGTNXiFlightSimEXE.exe version 1.0.3.7
[19/01/2024 15:00:06.034 00004f50 INFO] Got Version: 9
[19/01/2024 15:00:06.036 00004f50 INFO] GTNProxy::Open Services DLL Version: 1.0.3.7
[19/01/2024 15:00:16.453 00004f50 ERROR] ^^^ GTNProxy::Open Error starting process C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
[19/01/2024 15:00:16.453 00004f50 ERROR] Error closing program: 299
[19/01/2024 15:36:16.257 00000e08 INFO] Received Simconnect Quit
[19/01/2024 15:36:16.377 00000e08 INFO] Closing program automatically with MSFS
[19/01/2024 15:36:16.475 00002578 INFO] Ending EXE Process
Here the TDS GPS Manager log and the .exe log:
[20/01/2024 17:13:01.853 0000275c INFO] TDSGPSManager.exe version 1.0.1.0
[20/01/2024 17:13:01.854 0000275c INFO] MSFS Double Install: 0
[20/01/2024 17:13:01.854 0000275c INFO] MSFS Community Folder: 1 and I:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community\
[20/01/2024 17:13:01.855 0000275c INFO] MSFS LocalState Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\
[20/01/2024 17:13:01.855 0000275c INFO] MSFS TDS GTNXI Gauge Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\TDS-GTNXi-Gauge\work\
[20/01/2024 17:13:01.856 0000275c INFO] MSFS LocalCache Folder: 1 and C:\Users\svmir\AppData\Roaming\Microsoft Flight Simulator
[20/01/2024 17:13:01.856 0000275c INFO] Set CDD: 1 at path: C:\Users\svmir\AppData\Local\Temp\TDS\Temporary\
[20/01/2024 17:13:01.857 0000275c INFO] Set CID: 1 at path: C:\ProgramData\TDS\Trainers\
[20/01/2024 17:17:06.990 0000275c INFO] Exiting WinMain
[20/01/2024 17:09:42.439 00006388 INFO] TDSGTNServices.dll version 1.0.3.7
[20/01/2024 17:11:18.129 00006388 INFO] Ending Process
ALL my test flights are with NO addons except those necessary for A2A, Navigraph, Flow Pro, FSLTL
01-21-2024, 10:29 PM (This post was last modified: 01-21-2024, 10:40 PM by TacomaSailor.)
I uninstalled the Garmin Trainer app, deleted all files and folders associated with Garmin Trainer or TDS, and deleted all registery enteries (Win 11) for Garmin Trainer or TDS.
I then reinstalled Garmin Trainer and the instruments for single and multi engine recip, and turbo prop.
The trainer works perfectly in offliner/simulated data mode.
Here is the log of the install:
[21/01/2024 13:22:46.926 00002458 INFO] TDSGPSManager.exe version 1.0.1.0
[21/01/2024 13:22:46.927 00002458 INFO] MSFS Double Install: 0
[21/01/2024 13:22:46.927 00002458 INFO] MSFS Community Folder: 1 and I:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community\
[21/01/2024 13:22:46.927 00002458 INFO] MSFS LocalState Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\
[21/01/2024 13:22:46.928 00002458 INFO] MSFS TDS GTNXI Gauge Folder: 1 and C:\Users\svmir\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\TDS-GTNXi-Gauge\work\
[21/01/2024 13:22:46.928 00002458 INFO] MSFS LocalCache Folder: 1 and C:\Users\svmir\AppData\Roaming\Microsoft Flight Simulator
[21/01/2024 13:22:46.929 00002458 INFO] Set CDD: 1 at path: C:\Users\svmir\AppData\Local\Temp\TDS\Temporary\
[21/01/2024 13:22:46.930 00002458 INFO] Set CID: 1 at path: C:\ProgramData\TDS\Trainers\
[21/01/2024 13:27:03.759 00002458 INFO] Exiting WinMain
I then started MSFS with only the A2A PA24, the Flysimware 414aw, and the jpllogistics C 152 as aircraft to use. The community folder also had the tds-gtnxi-gauge folder and the tds-gtnxi-JPL_C152 folder.
The sim started normally and I saw the TDS display during the loading.
The GTN750NXi bezel and knobs appear in all three aircraft but the screen remains blank/black.
Here is the .exe log for this session of the flight simulator:
When I go try to execute the app at:
C:\ProgramData\Garmin\Trainers\GTI\Production\GTI__GTN_Xi__20_30\app-20.30.8\bin\GTN_Simulator.exe
I see the same bezel and knobs as in MSFS. If I click on the home button I get the message:
GTN Xi Series Trainer has stopped working
GTN_Simulator.exe has a Digest algorithm of sha256 and Timestamp of Monday, January 23, 2023 05:05:58 PM with a file version of 20.30.8.0 with date modified of 1/21/24 1:25PM
You can see in the following image that the wasm files for the gauge are loaded properly.
We have seen this error message only with Avast/AVG antivirus software. There is no need to keep on looking for other log files/sources as the problem is clearly stated in the TDSGTNXiExeLog.txt
In addition, the standalone GTN Simulator.exe is not designed to be executed externally, which is why it would not work/display a crash error message.
At this point, the only test that is relevant is this: with MSFS closed, start the TDS GTNXi from the desktop shortcut and click on the GTN750Xi button, please check if the screen lights up.
Since the TDS GTNXi has worked well in the past, most likely a software got installed that is interfering with it, let's try to remember which software got installed and work from there. As we have said above, this exact error has been seen with AVG/Avast.
For the sake of this conversation, we recommend continuing it via email: support@tdssim.com
You are correct - I had turned off (off until I turn back on) all AVAST shields and firewall and used Task Manager to ensure they were not running. The error still occurred.
I then disabled AVAST ransomware shield, email guardian, remote access shield. I also created exceptions in AVAST to not perform any security checks on the three drives I use for MSFS.
Now the TDS software works perfectly.
I will have to work on figuring out which AVAST task is the problem.
Why does no other MSFS addon, of which I have many dozens, have a similar problem as your software does with AVAST?
(01-23-2024, 03:11 AM)TacomaSailor Wrote: Why does no other MSFS addon, of which I have many dozens, have a similar problem as your software does with AVAST?
Or, why is AVAST the only virus scanner that has a problem with this software?
We see that AVAST/AVG have the tendency to inject themselves into running processes, which would result in a performance loss as well as disrupting normal process usage.