[Wyoming DLC] Game crashes east of Cody, WY

[HayesPacific]

My game crashes every time I attempt to exit the town of Cody heading eastward, between the 16 and 20 markers.
I'm guessing the game's trying to load in a scenery object which for whatever reason cannot be rendered?

crash_world.png

crash_map.png

Game version: 1.50.1.14s (64-bit)
Game crashes east of Cody ;[08/06/2024 11:37:12] (sec-0013-0009);-50003.3;77.4543;-35506.8;-2.1082;-0.0122727
Reproducibility: Always Reproducible
OS: macOS Sonoma 14.4

game.log.txt

[Madkine]

The crash in the game log is completely silent. Can you provide the crash log as well please?

[HayesPacific]

Thank you for the reply!

I see... I've had a look, and for some reason it never generated a crash.log.txt file. Upon review, I've also noticed that no "This application has crashed" operating system messages are appearing either afterwards, so it seems like the game just force-closes itself, rather than crashing.

Though after this, if I start the game back up and try into load into my profile again, it does give the "Crash detected" warning message on the side of the profile select screen. I'm sorry I'm not more of a help in this – do you have any other idea on what I could try?

Or could you try reproducing the issue, maybe?

[nautofon]

Crash logs on macOS are not placed in "~Library/Application Support/American Truck Simulator", they're in "~/Library/Logs/DiagnosticReports". The file name also isn't "crash.log.txt", but rather something that starts with "amtrucks" (for ATS) and with the type extension ".crash" or ".ips" (depending on macOS version).

Note that the forum software doesn't allow you to attach that file as-is, you'll have to change its name to e.g. amtrucks.crash.txt.

@Madkine Perhaps you could fix the bug reporting process to reflect this? The current text merges instructions for Linux and macOS, which isn't very helpful.

Regarding the reported crash: I confirm that the game crashes at that particular location for me, too. This is a 1.50 regression—I drove past there no problem on 1.49 just a few weeks ago.

Code: Select all

crash near Cody - go east from here ;[08/06/2024 22:10:16] (sec-0013-0009);-50083.7;82.2319;-35532.5;-1.86961;-0.0789364

amtrucks_2024-06-08-221035.crash.txt

game.log.txt

edit: file location

[Madkine]

@Mohegan13 Can you update the bug reporting process?

[HayesPacific]

Ohh, I see now – thank you for the help @nautofon!

I've had a look in this folder, and I couldn't find any ".crash" files either – only ones ending with ".cpu_resource.diag".
I have reproduced the issue again and renamed the latest one of these to "amtrucks.crash.txt", which is attached below.

I've also attached another game.log.txt.

amtrucks.crash.txt

game.log.txt

I hope this helps!

[nautofon]

.diag is another kind of report though.

The "~/Library/Logs/DiagnosticReports" directory should be the correct location. However, I realize now that the type extension differs by macOS version: It's .crash on macOS 11 and earlier, but .ips on macOS 12 and later. I updated my earlier post accordingly.

Perhaps an easier way to find these reports would be through the Console utility, see the following Apple Support document. In Console, select "amtrucks" in Crash Reports, then Reveal in Finder:

https://support.apple.com/guide/console/reports-cnsl664be99a/1.1

[HayesPacific]

Thank you for the help!

Hmm... it's bizarre.
I've tried the Console app, but the "Crash Reports" section remains completely empty, even after reproducing the crash.
Same goes for the Spin Reports section. The only "Reports" sections that aren't empty are the Log Reports and Diagnostic Reports sections, the latter of which I had sent a report from.

I've also searched my computer for files with the extension of ".ips" and found none.

Somehow, I don't think it properly recognises that the game crashes for me, which is likely why there also are no system messages telling me that ATS had crashed after it happens... I'm really not sure what I can try still, sorry.

[nautofon]

Weird. I'm afraid I don't know, either.

But since SCS has the crash log from my machine, and since this issue seems to be real simple to reproduce, hopefully they'll still be able to fix this particular case at least.

[HayesPacific]

Yes, I'm glad they have yours at least and I hope the issue will be fixed soon.
Thank you again for the help though, I appreciate it!