[Wyoming DLC] Game still force-quits itself east of Cody, WY [264893]

[Madkine]

@dummytrucker Can you provide the crash log? The game log looks to have nothing of value in it.

[dummytrucker]

@Madkine No problem, the attachment is my crash report.

[Madkine]

Ah, mac. I don't understand much in a game log from Windows and even less from a mac one. I can see it recorded the game as crashing, but don't understand the log beyond that.

[Madkine]

Whats interesting is that we are 2 for 2 for the crash occurring on a mac and so far no one being able to replicate on windows.

[dummytrucker]

Maybe this problem is only related to macOS.

I had to ask SCS to help mac users create a space portal to traverse that area. (just joke)

[nautofon]

It used to crash on my Mac, too. So 3 for 3, I guess. I don't understand why it works for me now, but still crashes for both of you.

@Madkine If you mean the crash log: That's right, only SCS can read it. They need to symbolicate it in Xcode.

developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report

[kaarlows]

Thanks to nautofon replying to my bug report of the exact same location.

Like him and other 2 other players who came here to the Forums, I'm also a macOS player, which probably indicates this must be something related to OpenGL graphics or some code which is poorly translated in Rosetta.

[HayesPacific]

I see. It is unfortunate that the issue persists, but I'm glad I'm not the only one experiencing it.
Hopefully SCS'll be able to locate and fix it soon.

I've also just checked again myself and can confirm that the crash still happens for me on 1.53.1.5s (64-bit) (macOS Sonoma 14.4, without mods).

[Cyclone]

Another thread was recently posted about this, so this is not an isolated issue. My experience with train simulators does beg a question of whether the issue may be computer hardware-related. What I mean is that it might not be a specific asset, but rather the fact that the computer is being overworked in that specific part of the map. Do you have the ability to test with a different computer? Your comment that you are seeing this on Macs is capturing my interest. I don't own a MAc and probably will not be able to get on my mother's to test, or I'd actually run this there.

I'll get up there and give this a run in due course on my Windows 10 PC. Just hanging out in the southeast corner of Texas right now. I have looked at the road network and may do an Interstate 25 drive like my I-10 drive and that would place me one city away in Sheridan, so I will make this my next trip after I return to Las Cruces. I shall report back.

[HayesPacific]

@Cyclone It is an idea, although I'm certain it's just some incompatible asset that's used in this specific area which causes the game to crash.

I'm experiencing this bug on a brand new Mac Studio, and the computer isn't struggling at all while playing ATS (fans are completely silent) no matter where I am in the map, and I'm also not experiencing any lag – it's only when I get to that particular spot, the game just immediately quits itself as though it was trying to load in some asset which it simply couldn't load.

Others in this thread have already tested it on Windows and weren't able to recreate it, so it really seems
like whatever the asset is, it's only incompatible with macOS and works completely fine on other platforms.