kiek

Thank you; this FSLTL log provides a much stronger lead. Immediately before MSFS crashed, the last aircraft successfully updated through SimConnect was: SCR762 / D-CSGD / C56X PSXT matched this aircraft repeatedly to the generic FSLTL C25C model using these liveries: FSLTL_GA_C25C_PS-CSF FSLTL_GA_C25C_M-MIKE FSLTL_GA_C25C_ZZZ SCR762 was removed and recreated several times shortly before the simulator disappeared. This does not conclusively prove that one of these liveries caused the crash, but the FSLTL C25C model group is currently the strongest suspect. As a first test, please add SCR762 to BLOCK_CALLSIGN and repeat the same situation at Bristol. If the crash no longer occurs, we can then test the three C25C liveries individually to identify the exact model variation. If possible, please also send the corresponding Windows Event Viewer “Application Error” entry for the MSFS crash. Its faulting-module information may confirm whether the crash occurred inside an aircraft model or texture component. AND PLEASE DO NOT POST LARGE BLOCKS OF TEXT WITHOUT THE SPOILER, see How to hide large texts when posting - PSXseeconTraffic for FSX | P3D | MSFS - The AVSIM Community

Received and implemented.

Received and replied.

I do not have your email address. Send me a test message at my tblo mail address, if you will. Then I'll reply.

Thank you Michael!

You can always donate via the button on my web site.

16.5.2 is now available, with the older versions still available in the archive. PSXT will warn you that there is a newer version, but it will not force you to update.

Thank you for the detailed examples. You are correct, and I apologize for the problem introduced in 16.5.1. PSXT should not require you to purchase FlyTampa KLAS V3 in order to keep using your valid V2 product. V2 and V3 are separate paid products, not successive free updates that can be treated as one version sequence. Your EGLL example also confirms that versions belonging to the MSFS 2020 and MSFS 2024 products can diverge. PSXT should therefore not present MSFS 2020 version 3.1.4 as a newer version of your current MSFS 2024 version 1.1.0. The ORBX examples may similarly concern different product or distribution variants. I will restore the airport archive from before it was reduced to three versions. I will also change PSXT’s newer_only handling so that the absence of an exact archived version no longer blocks sending the airport to TBLO or effectively forces users to purchase another product generation. The version warning logic will need further refinement because publisher, ICAO and version number alone are not sufficient to distinguish MSFS 2020/2024 products, paid V2/V3 releases and different distribution channels. Thank you again for reporting this so clearly. Your examples were very helpful in identifying both problems.

Then it must be another one? Switch to FSLTL only and try again.

Thanks, this additional information is important. Four MSFS CTDs with PSXT running, while three long flights without PSXT completed normally, does make an interaction with injected AI traffic more plausible. However, the “No match found” message cannot itself cause the CTD. A no-match means that PSXT did not find a suitable livery, so that aircraft is skipped and is not created in MSFS. A successfully matched model could still be involved. In this log MSFS appears to crash immediately after OCN5C_ starts its take-off transition. That aircraft was using AIGAIM_Discover Airlines Airbus A320-200SL. This makes it a possible candidate, although the log alone does not prove that this model caused the crash. The SimConnect dispatch failed message is most likely a consequence of the MSFS CTD: once MSFS disappears, PSXT loses its SimConnect connection. Could you please send me the PSXT logs from the other three CTDs as well? I would like to compare the final traffic events and determine whether the same model, location or take-off/landing transition appears before every crash. If possible, testing the same area once with only FSLTL liveries enabled and once with only AIG enabled would also help determine whether an AIG model is involved.

PSXSeecon? I think you meant PSXT! The link to jumpshare does not work for me. Just post your Log.txt here in line: Open the Log.txt, select all text with Ctrl-A, then CTRL-C en then post it with CTRL-V Btw model matching should not make PSXT crash, only the Sim might crash.

I tried... but Codex came up with new features to keep the archives with airport files manageable. See version 16.5.1

Maybe it is wise to check your mail system. This does not sound good.

Yes that may sometimes happen. Same with an aircraft crossing a runway a little too soon. Or aircraft that run into each other during taxi. It is all caused by differences in timing and location in adsb data plus time shifts PSXT used to fulfill the required groundspeed and location. Luckily it does not happen that often. I will ask my fabulous ChatGPT Codex friend to find a solution for it when I have enough money to hire him/her/it again 😀

Defaulting to minimum wingspan is also not what you want. Just give me the raw model string from your log.txt and I'll add it to PSXT. (and editing the aircraft.cfg yourself is even better, if you know the ICAO model code)