Multiple crashes around LIPZ

[joscha66]

I've got reproducable crashes flying from LIPV to LIPZ (04L) using #1 GTN750xi and #2 GTN650,V 1.0.1.6. Tried it with two independent XP14.4.3 installations. I use Navigraph AIRAC 2610. TDS Log files do show nothing.

Any ideas what could couse this? Usually it runs rock solid! Today no issues EDMA->LOWI->LIPB->LIPV

Thanks for any hint,
joscha66

...750Unit1
[17/10/2026 18:22:17.553 00004f48 INFO] TDSGTNServices.dll version 1.0.1.6
[17/10/2026 18:33:22.167 000008ac INFO] Auto Closing GTNXi

...650Unit2
[17/10/2026 18:52:31.815 00000b08 INFO] TDSGTNServices.dll version 1.0.1.6
[17/10/2026 18:56:34.393 000028bc INFO] Auto Closing GTNXi
[17/10/2026 18:56:34.686 00000b08 INFO] Ending Process

ROAR
[17/10/2026 18:33:43.832 00001e8c INFO] TDSROARService.exe version 1.0.0.0
[17/10/2026 18:33:43.833 00002a78 INFO] Auto Closing TDS ROAR Service

panel log
[17/10/2026 18:50:45.571 00001048 INFO] TDSGTNXIXPlane.dll version 1.0.1.6
[17/10/2026 18:50:45.571 00001048 INFO] X-Plane Simulator appVersion: 12431 xplmver: 430
[17/10/2026 18:50:45.590 00001048 INFO] Searching for Steam Install: C:\X-Plane 12-DEV/steam_api64.dll with val: 0
[17/10/2026 18:50:45.690 00001048 INFO] Start OnAircraftLoaded
[17/10/2026 18:50:45.690 00001048 INFO] Received XPL MonitorBoundsOS index 0 with pxLeft: 0, pxTop: 1080, pxRight: 1920, pxBottom: 0
[17/10/2026 18:50:45.690 00001048 INFO] Received XPL MonitorBoundsOS index 1 with pxLeft: -1920, pxTop: 1080, pxRight: 0, pxBottom: 0
[17/10/2026 18:50:45.690 00001048 INFO] Received XPL MonitorBoundsOS index 2 with pxLeft: 1920, pxTop: 1080, pxRight: 3840, pxBottom: 0
[17/10/2026 18:50:45.690 00001048 INFO] Received XPL MonitorBoundsOS index 3 with pxLeft: 3840, pxTop: 1080, pxRight: 5120, pxBottom: 56
[17/10/2026 18:50:45.690 00001048 INFO] Received XPL MonitorBoundsGlobal index 0 with bxLeft: 0, bxTop: 1080, bxRight: 1920, bxBottom: 0
[17/10/2026 18:51:32.855 00001048 INFO] Start OnAircraftLoaded
[17/10/2026 18:52:28.558 000039dc INFO] Got Version: 10
[17/10/2026 18:52:28.562 000039dc INFO] Open GTNXi750U1
[17/10/2026 18:52:29.418 000039dc INFO] GTNProxy::Open Services DLL Version: 1.0.1.6
[17/10/2026 18:52:31.655 000039dc INFO] Got Version: 10
[17/10/2026 18:52:31.659 000039dc INFO] Open GTNXi650U2
[17/10/2026 18:52:31.659 000039dc INFO] GTNProxy::Open Services DLL Version: 1.0.1.6

XP12 Log.txt ... last lines of last crash
0:01:52.773 I/TEX: Target scale moved to 2.000000. Texture usage is 1.30 gb out of 10.20 gb available. Memory headroom is 9.17 gb
0:02:24.206 I/WIN: Opened window Ground handling window
0:02:46.086 I/TEX: Target scale moved to 4.000000. Texture usage is 1.78 gb out of 9.91 gb available. Memory headroom is 8.39 gb
0:03:32.318 I/TEX: Target scale moved to 8.000000. Texture usage is 2.18 gb out of 9.39 gb available. Memory headroom is 7.46 gb
0:04:16.352 I/TEX: Target scale moved to 16.000000. Texture usage is 3.00 gb out of 9.35 gb available. Memory headroom is 6.59 gb
0:05:08.951 I/SCN: Loading sim objects for airport LIPZ
--=={This application has crashed because of the plugin: C:\X-Plane 12-DEV\Resources\plugins\TDSGTNXi\64\win.xpl}==--
--=={FILE: C:\X-Plane 12-DEV\Log_ATC.txt}==--

[adminOwner2]

Hello,

We are sorry to hear of the issues, we are here to help.

Can you please help us out with the reproductive crash information, we need step by step instructions on how to reproduce the crash.

[joscha66]

Hello,

I've just tried in a plain 12.4.3 installation with the stock Super Cub. #1 GTN750xi, #2 GTN650, both popped out. Start at LIPV (Venice Lido), set flight plan destination in the GTN750 to LIPZ (Venice Tessera) - I've selected visual 04L, but as fas as I remember it is not relevant - just fly the direction towards LIPZ. A minute into the flight the sim/GTN crashes (CTD). Today, I've seen the error message as attached - did not see that at yesterday's crashes.

I've attached the complete XP-log. Please let me know in case you need anything else.

Thanks for your help!
joscha66

[adminOwner2]

Hello,

Thank you for the information. Can you please help us out with two screenshots inside X-Plane: the first of the flight plan page (pages) showing the exact flight plan.
The second of thee GTNXi screen in map/FPL mode when the crash occurs.

Can you confirm that you can always replicate this crash?

[joscha66]

Wow, this time it crashed already during take-off roll. This was the first time I've started with engine running to speed things up .... seems also the crash did speed up    .

Please find attached the screen shots as requested - and yes, I can reproduce it easily with different aircraft, installations. And the log.txt always tells the GTN plugin caused the crash.

---

... and I tried another flight, same setup, but did not select '04L' directly. Then I was able to fly to the position as shown in the attached screenshot. After selecting RWY 04L approach it crashed within 3 seconds.

Maybe, something with the data for that approach?

joscha66

[adminOwner2]

We thank you for brining this bug to our attention as well as the information provided.
As a test, can you please redownload/reinstall the TDS GTNXi XPlane, V1.0.1.6 and let us know if you still experience the bug?

[joscha66]

Ok, great, after a 'new' re-install (I did that yesterday a few times already) it works!
I did two test flights onto 04R and 04L LIPZ without any issue. Have you done some changes? The new .xpl shows a modified time in the future 

In any case, thank you for your support!

joscha66

[adminOwner2]

We are glad to hear this, we thank you very much for your help.

As part of the TDS GTNXi we offer Visual approaches. Navigraph Charts have started offering VFR charts, which correlate internally with our visual approaches, the issue lied in the Navigraph Charts code on the TDS end. Most likely now you will see the geo-referenced chart overlay on the map page as well.

As far as the .xpl file time/date, it originates from our systems, one hour ahead of Italy.

[joscha66]

Ahh, got it, after writing I've thought maybe you guys are not in CEST time zone!

About the bug:
That makes sense and yes, probably around the time the chart should show up, it crashed in the past. Glad, you have found that!

Thank you again for the great support!

joscha66