Sorry to say it has not gone away. Just ran a short timetable service 1N40, with as class 465/9, on SEHS and got it on exit. Yes, the update was installed and verified.
I'm also on PC and had the update this afternoon. I have just played the NJ 491 Hamburg-Altona to Wien Hbf service, using the DB BR101 on SKW and then exited the game after and also had the UE4 crash on exit, so not fixed.
We can even say that the update did not solve anything. Neither the crash on output, nor the stutter.
On stuttering, it seems some better after the update on running Cajon Pass, though some is still present. The issue on initial load is also still present but now it's more like a pause instead of a freeze.
Bjr to all, indeed still to this day of 03/12/2022 all my game releases are systematically accompanied this time by the famous insert of the EU warning panel as before the update concerning it!!! Sincerely, tof
UE4 crash on exit happens since the release of this TSW3 DeLuxe version, so I resigned to accept the thing as all other bugs. Sometimes, the crash does not appear in the form of the Epic Dialog above mentioned but with a direct Windows 11 error report like this: - System - Provider [ Name] Application Error [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57} EventID 1000 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2022-12-02T18:23:44.7290244Z EventRecordID 3712 Correlation - Execution [ ProcessID] 6132 [ ThreadID] 20092 Channel Application Computer PCdiGiuseppe - Security [ UserID] S-1-5-21-3972237494-1609433406-98105874-1001 - EventData AppName TS2Prototype-Win64-Shipping.exe AppVersion 4.26.1.0 AppTimeStamp 637f26a0 ModuleName ntdll.dll ModuleVersion 10.0.22621.900 ModuleTimeStamp a97a9ed6 ExceptionCode c0000374 FaultingOffset 000000000010c249 ProcessId 0x3118 ProcessCreationTime 0x1d90674124e9986 AppPath I:\SteamLibrary\steamapps\common\Train Sim World 3\WindowsNoEditor\TS2Prototype\Binaries\Win64\TS2Prototype-Win64-Shipping.exe ModulePath C:\WINDOWS\SYSTEM32\ntdll.dll IntegratorReportId 7e3b3ebf-b2d1-45bd-b14c-6d35b902b46a PackageFullName PackageRelativeAppId No hope to see a solution, however.
Bjr, personally I haven't had an error message concerning TSW3 yet but if you have had one there's no reason why it shouldn't also happen for me unless it concerns a specific device or other but what? either way it becomes boring and annoying especially since DTG would have already worked on the problem but force to note that they did not settle it!!! Sincerely, tof
