I am trying to play the Hibernal Heaven scenario in Journey mode and the game always crashes as soon as the loco is moving. This is the error I captured from the crash screen "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff" But all other scenarios in the DLC run fine. It looks to be isolated to this one.
I'd like to expand upon this. I've found this crash is not just limited to the Hibernal Heaven scenario, but rather that it can occur at any time the G6 is operated with the Multiple Unit Mode switch set to "Master", regardless of if it's coupled to another G6 or not.
This was the missing piece i guess. Thanks! There is indeed a little mistake in the cable-logic i think. Need to get confirmed that by a core-engineer first on Monday.
Just to say that I've also had multiple crashes running this scenario this afternoon. Its good to see that the problem has been identified.
I also get this crash whenever I activate, myself, the Multiple Unit Mode with Master during a scenario/service. However, if you start a service with a preconfigured coupling on Master, it does not crash. For example the time service: G6-Sh19 (22:10); I finished it without a crash.
Yes it is and i suffered the same problem. After 5-10 minutes in this scenario i got a crash to desktop with the following crash report: LoginId:1267aa5b4c599ea565f7ab924e4c774f EpicAccountId:ae17b9402eb94de8b3ccd338a7f3ae9f Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000295f1900019b TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping kernel32 ntdll Here is a Youtube Video (not from me) where the player get the same CTD. Looks the same like my crash
As said somewhere else here in the forums, this is already fixed on my end. But the release of fixes need a new round of QA and all that stuff. That takes a good portion of time unfortunately. So please be patient. The fixes will come at some point.
For the time being, switching on multiple unit mode causes a crash, whether in this scenario or anywhere else.
Ok, the fix might be there. Let's have a look if it works now. Edit: "Today we are bringing updates to the Arosa Line in preparation for the RhB anniversary pack, and we have one additional optimisation update for Sherman Hill. Core Fixed an issue where coupling certain vehicles would cause a game crash." The scenario still crashes.
Yep, can confirm, that was not fixed. Still crashes. But is it possible that not everyone has the problem? He played the scenario without any problems and there are no comments mentioning a computer crash... this is weird because for me, the scenario regularly crashes within 3 minutes.
The crash is a more random thing as it seems. The (potential) fix for it is not released yet (i have no idea when this will happen, it's not on me).
I can repeat the crash with the stopwatch. The scenario starts, i stand up from the driver seat, set the switch to master, then i go to the second loco, set the switch to slave, return to the first loco, set the drive direction, engage SIFA and the PZB, release the brakes and when i am appling power, the game crashes.
I have the same issue. It occurs fairly consistent, shortly after you get permission from dispatch. I then tried to resume from a saved game. It now happens after various driving distance. I include the last crash report, in case this is useful.
Hmm. I just ran the whole scenario with no problems (well, except for that hill start, which took a bit of juggling on my part).
Thank God for the forums!! I have been trying this scenario four or five times today and crashes every time. Tried another scenario and it works as it should. Much relief after reading these comments!
Is there any ETA for this fix? This was the first scenario I tried after buying this DLC (after reading rave reviews about the quality of the loco both here and on the Steam forums) and doing the introductory session. Was not a good experience as it invariably crashes after setting the master and slave setting on the two locos and starting the master loco. Trust this will get fixed soon. Hope to try some of the other scenarios meanwhile.
Sorry guys that it takes so long to get the fixes out. But it is not on me. I just discussed with DTG about it to have an idea when the fixes will get released. But still, i have no clear answer to that yet.
Well, I think it's most likely, that they will be released with the RRO preservation crew upgrade, as this is the last on the list on the roadmap I wouldn't expect anything before May...just taking a guess.
