CTD after 3Hr. 55 Min. A350 and only when using FSLTL in Combination

[MPO910]

Used FSLTL and Traffic was shown in PFD.

Repeatable CTD same failure code as below, mostly between 30Min and 4 hours in flight ONLY when using FSLTL

RTX4090

9900X3D

64GB RAM 6000MhZ

No OC

FSLTL with PMDG has no issues at any flight, A350 without FLSTL also no  ctd. But in Combination CTD. Like with 1.0.0, 1.0.2 as solved since 1.0.3, 1.0.4 and CTD came back with 1.0.5 and still present with 1.0.6

It happened while I clicked in the enroute map of IOS  (maybe that was coincidence)

Faulting application name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.6636, time stamp: 0x674f613e
Exception code: 0xc0000005
Fault offset: 0x0000000000108ba7
Faulting process id: 0x5088
Faulting application start time: 0x1DBA0A7BA73B5A4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvwgf2umx.dll
Report Id: 036cc186-4216-4a49-927a-f7161dd323b5
Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Edited March 29 by MPO910

[Swisspilot1986]

Could you recover your flight entirely with the new feature Autosave?

[MPO910]

3 hours ago, Swisspilot1986 said:

Could you recover your flight entirely with the new feature Autosave?

Partly ..... Bur the issues make this function unusable. .fuel on Arrival isnnot correct....way to high...(44t instead of 9.2 as before the CTD) and CRZ altitude is not recognized by the autopilot anymore... plane ignored the set altitude on the FCU and FMC...it climbs through that set value or descents through it.....doesn't matter. All the time.....so OPENCLB OPENDSC and Managed climb and descent are unusable After a flight with auto save is restored. 

Also stored or pinned maps didn't work, radio volume controls not restored as well ....fuel weights (alternate, reserve) not correct ... 

Edited March 29 by MPO910

[Swisspilot1986]

This Autosave is brillant but need some fixes

[SUB750T]

Actually my game CTD and I recover 100% using auto save. Even A Pilots Live Chapter 2 Flight is going back ok.

 

Thank you Dev's!🥰

Edited March 30 by SUB750T

[Simon Stühlinger]

What is your TLOD settings?

[MPO910]

75 ground and 150 crz

[Simon Stühlinger]

check it with arround 90 in cruis.... i think there come no ctd back

 

[MPO910]

1 hour ago, Simon Stühlinger said:

check it with arround 90 in cruis.... i think there come no ctd back

 

Why should I set it so low at a system which is capable of 70 FPS in VR or 90 without VR and 25% cpu utility and lax 60% GPU utilisation?

I have 0.1% low framerates....and 99,9% low framtimes....so a stutter free system

[Powie]

also got an CTD in cruise today after 2,5 hours...... 
NO FLSTL... I think this is not related to fsltl traffic...

[Tveo]

Hello, my contribution to the matter:

In the last two days, I obtained two CTDs with the combination of this aircraft + FLSTL activated through its injector (not through BATC).

I must say, I hadn't obtained CTDs in the system for many months, almost as many since I installed the simulator, MSFS2024.

In my case:
- Flight from TLS - DBX: 8 hours without CTD
Followed:
- Flight DBX - AKL: CTD at 9:47 hours It was stopped for almost 4 hours until I realized (seen in the Pegasus client of vAMSYS).
I started MS24 WITHOUT ACTIVATING FLSTL this time, and in the air. The aircraft has its systems in C&D, so I couldn't activate the save through the dashboard. Ok, I started a new flight on a runway near the CTD location with the engines running. Everything's up and running, and I activate the last autosave via the tablet. Less than 15 seconds later, I'm in the air, and everything is proceeding normally except that the PA is in HDG mode and the EFB flight plan has disappeared (a minor issue). I activate a direct to the next waypoint, and the plane heads off. I didn't have to do anything else on the plane. Well, yes, I had the arrival runway entered in the MCDU with its STAR... and I think this is why the TOD was lost from the flight plan, but a simple descent calculation resumed the descent in managed mode at the calculated point. I landed at AKL almost 6 hours later without further problems.
- Just today, in fact, a few minutes ago. Flight MAD - NRT. New CTD with FLSTL active this time, at 6:58 hours. I restart the flight on the nearby airport runway and activate the last save without FLSTL activated. Just like the previous flight, less than 15 seconds, and I'm in the air at the same point, so much so that Pegasus doesn't detect any route changes. Everything is fine, fuel consumption, route, etc., except for the minor EFB details mentioned earlier. Now, this time, I haven't missed TOD because I didn't have an arrival runway in the flight plan. Just to test, I activate the runway, STAR, and APP, and... if the TOD appears. I still have about 5 hours of route time left to arrive... if I arrive.

I mean, FSTL has something to do with it... although on one of my flights, having it enabled wasn't a problem, on the other two, there was CTD.

My next flight, I'll fly without FLSTL from the start... whether or not the theory is confirmed.

PS: the autosave works VERY well.

Edited March 31 by Tveo