ATS Game Crashes with 300% Scaling in 1.55

[autobahn186]

A very strange issue has arisen in ATS since the 1.55 update. I did not have this issue at all in 1.54. Basically, if I start the game with 300% scaling, within a few minutes of driving the game will crash. With 200% scaling I don't have this issue. One workaround I've found that works is if instead of starting the game with 300% scaling, I start it with 200% and then while driving in the game, pausing the game and changing the scaling to 300%, the game will run fine and not crash. It's only starting the game with 300% scaling that makes it crash after a short duration of gameplay. I have also noticed that the VRAM usage is much higher with 300% scaling when I change the scaling in the middle of the game, than it is if I start the game with 300% scaling, so I'm wondering if there is an issue with how the game is allocating VRAM when starting the game. However, VRAM usage is not a limitation with my hardware as I'm on an RTX5090 GPU with 32GB of VAM.

I am running triple 4K monitors with an RTX5090 GPU, Ryzen 9800X3D CPU and 64GB of RAM.

I am using the following launch options:
-nointro -unlimitedlog -sysmouse -mm_max_resource_size 100 -mm_max_tmp_buffers_size 1000 -mm_pool_size 32768

I appreciate any feedback or ideas on how to deal with this frustrating issue.

[Madkine]

Try verifying your game files.
In Steam, right click on the game, select properties, go to local files tab and press verify integrity of game files.

If that doesn't work post your game.log.txt and crash log to pastebin.com (no account needed) and then post the link here and we'll have a look for you (split the game.log.txt into multiple pastes if it is too big).
If pastebin is not available in your country please use http://rentry.co and post the link to it here please. The page works like pastebin.
The files can be found at "C:\Users\*USERNAME*\Documents\American Truck Simulator" for a default install.

Possible fixes:

Change Scaling/TAA combination. NVIDIA does not like some combinations. (300%, SMAA+TAA crashing - 400%, TAA working)

[The_SimTrucker]

I had the same thing. The combination of a multimonitor setup, Nvidia drivers, and scaling 300% will crash the game within a few minutes.

I use r_multimon_mode "4", with a virtual 3 screen setup on my curved monitor. I get rock solid gameplay with scaling at 400% and a crash within minutes when running 300% scaling.

Perhaps here there are posts with more hints and tips: https://roextended.ro/forum/viewtopic.php?f=23&t=1563

[R1jerome]

A very strange issue has arisen in ATS since the 1.55 update. I did not have this issue at all in 1.54. Basically, if I start the game with 300% scaling, within a few minutes of driving the game will crash. With 200% scaling I don't have this issue. One workaround I've found that works is if instead of starting the game with 300% scaling, I start it with 200% and then while driving in the game, pausing the game and changing the scaling to 300%, the game will run fine and not crash. It's only starting the game with 300% scaling that makes it crash after a short duration of gameplay. I have also noticed that the VRAM usage is much higher with 300% scaling when I change the scaling in the middle of the game, than it is if I start the game with 300% scaling, so I'm wondering if there is an issue with how the game is allocating VRAM when starting the game. However, VRAM usage is not a limitation with my hardware as I'm on an RTX5090 GPU with 32GB of VAM.

I am running triple 4K monitors with an RTX5090 GPU, Ryzen 9800X3D CPU and 64GB of RAM.

I am using the following launch options:
-nointro -unlimitedlog -sysmouse -mm_max_resource_size 100 -mm_max_tmp_buffers_size 1000 -mm_pool_size 32768

I appreciate any feedback or ideas on how to deal with this frustrating issue.

got the same problem here since 1.55, if i want to play at 400% render scale, i've to start the game at 300% then switch during game to 400%. If not, if i start he game at 400%, it crashs after few minutes of gameplay. Have you find a fix to solve the issue for you ?

[autobahn186]

I have not sadly