14 GB of RAM

[David Bruce]

Today I noticed that the game is using 13.5 - 14 GB of RAM. It used to use a lot less. I thought it was because I have scaling set to 300%, but I turned scaling down to 100% and it's still using 14 GB of RAM. Only have ATS, trackIR, and msi afterburner running. My computer is ryzen 5600x, 32 GB ddr4 RAM, rx 7800 xt, ultrawide monitot (3440x1440p). All my graphic settings are set to high. Is everybody else using more RAM letely?

[[ BBS ] Bootleg]

Been running smoothly on around 9-8 gb of ram use here out of 16 total. Can't see much of a difference from earlier versions.

Might wanna check your task manager though if there's any TSR (terminate & stay resident) programs/apps in the background clogging up ram usage.

[Reversoman]

Just checked mine, Ryzen 7 48GB RAM 3840x1440 running trackIR, MSI Afterburner says 9.1GB used. In Nevada just north of Tonopah. Might depend a bit what state you are in?

[Reversoman]

Just out of interest, after half hour or so, now sitting at 11.2GB used. Restarted and back to about 9.1GB.

[Wolfpig]

Have you tried to remove half of your ram to see if it still tries to use it.

The thing with OS is, if the ram is available then it might get used.
Doubt you put that much into your System just for letting it "idle" around.

[The Pitts]

It feels to me like v1.49 of both games increased the amount of RAM that is grabbed at start up. Looking back at some older game logs (which are intermittent because I tend to only save them when I have a crash, and those are thankfully rare) I see the game allocating 2GB of memory at start up, eg. in this log from April 2023 with v1.47.2.0:

00:00:00.003 : [mem] Trying to allocate memory pool (2097152K)

whereas more recently in a log from January 2024 with v1.49.3.2:

00:00:00.003 : [mem] Trying to allocate memory pool (10485760K)

These are both from the same system with 32GB of RAM and the only launch parameter being -nointro, so something definitely has changed.

[Wolfgang]

Originally posted by The Pitts:

It feels to me like v1.49 of both games increased the amount of RAM that is grabbed at start up. Looking back at some older game logs (which are intermittent because I tend to only save them when I have a crash, and those are thankfully rare) I see the game allocating 2GB of memory at start up, eg. in this log from April 2023 with v1.47.2.0:

00:00:00.003 : [mem] Trying to allocate memory pool (2097152K)

whereas more recently in a log from January 2024 with v1.49.3.2:

00:00:00.003 : [mem] Trying to allocate memory pool (10485760K)

These are both from the same system with 32GB of RAM and the only launch parameter being -nointro, so something definitely has changed.

That is not what I have in my game.log file. At that position it reads for me:

00:00:00.002 : [mem] Trying to allocate memory pool (6291456K)

Which is a bit more than 6GB and more than half of what I have available at the time of starting the game:

00:00:00.002 : [mem] physical total: 16151M
00:00:00.002 : [mem] physical avail: 10131M

Though I don't have any pre-1.49 game.log directly but looking at my bug reports from before 1.49 shows indeed a change (this is from 1.45 in ETS2):

00:00:00.002 : [mem] Trying to allocate memory pool (2097152K)

Which is exactly the number you have in your 1.47 game.log file.
So my guess is that the game is now trying to allocate more RAM than before and actively use a bit more than half of the available RAM and allocate, like before, 5 temporary loading buffers to them effectively increasing the size of each temporary buffer. I think increasing the size of these buffers before was only possible via launch commands, now it is the game doing actively that which is likely due to newer assets maybe getting or already being bigger than the previous buffer.

[Madkine]

32GB of RAM

00:00:00.000 : [mem] Trying to allocate memory pool (10485760K)

So it does seem to be dependent on what you have.

[Witchfynder]

64GB of RAM

00:00:00.000 : [mem] Trying to allocate memory pool (10485760K)

Looks like it tops out at 10GB.

[Ryu]

64GB RAM here, but this is my log from last night:

00:00:00.000 : [mem] Trying to allocate memory pool (16777216K)

...also using "-mm_pool_size 16384" as one of my launch params.

[Madkine]

I added the launch parameter '-mm_pool_size 16384' and now my log shows

00:00:00.001 : [mem] Trying to allocate memory pool (16737286K)
00:00:00.178 : [mem] Allocated 2 temporary loading buffer(s)

Though interestingly only 2 buffers created

[Ryu]

You can get more (and larger) buffers with these two params:

-mm_max_resource_size 60 -mm_max_tmp_buffers_size 1000

[Cipus]

despite whatever you read on the scs forum about mm_pool_size being obsolete, think at this suggestion for a "clean" game only. at scs you will never find recommendations for a modded games and with the default limited number of Ai models and scarse traffic, indeed you don't need mm_pool_size. but if you have added some Ai packs and increased traffic density, you MUST add this parameter with the correct value which is half of your installed RAM in MB, alongside with the other 2 mentioned just above.
P.S. I reach close to 30 Gb RAM, but I play with a lot of traffic trailers from mods and base game that are not in traffic by default

[Wolfpig]

Originally posted by Cipus:

but if you have added some Ai packs and increased traffic density, you MUST add this parameter

Never had to use that parameter when I ran such things in the past.....