Train.exe memory switch use of command line memory switch
#11
Posted 17 January 2013 - 12:51 PM
#12
Posted 18 January 2013 - 01:19 PM
#13
Posted 18 January 2013 - 01:22 PM
#14
Posted 19 January 2013 - 03:51 PM
i do find however that if i come out of MSTS a few times and restart, that when total machine memory usage gets to around 50% MSTS will crash, but if i go in and run without coming out i can run an entire act on the new SLI seligmans at 40-59fps in one go. If i want to keep on starting MSTS then i generally restart the PC to clear the memory once in a while.
i tested a number of routes using 1024 then 2048 then 3072 and then 4096 to gauge the differences and in all cases on the high load routes each increase in assigned ram brought noticable fps increases. i have 8GB of memory installed, when i double that to 16GB this year i will try even higher values.
#15
Posted 26 January 2013 - 07:29 AM
Numbers above 2048 can't make much sense. Under normal circumstances, Windows cannot assign a 32-bit process more than 2 gigabytes of memory at a time. It doesn't matter how much memory your computer has or how many bits are pumping through the operating system you're running.
I think specifying more than 1024 for the "mem" switch is unnecessary, but I guess as demonstrated above it can (rarely) make a difference if you have the memory to spare. You need to be using a 64-bit operating system with at least 4 GB of physical memory before you even consider specifying 2048, though. For 99% of users, 1024 will be fine, provided you have at least 2 GB of physical memory installed.
If you have 2 GB or less less of memory installed, you should be specifying half of that value for the "mem" switch. For 2 GB, specify 1024. For 1.5 GB, specify 768. For 1 GB, specify 512. If you don't know how much physical memory your computer has available to Windows, it's easy to find out. The System Properties Control Panel is one place.
#16
Posted 26 January 2013 - 08:25 PM
Cheers Bazza
#17
Posted 28 January 2013 - 06:40 AM
If you intend to specify the "mem" switch to start MSTS, you must specify it by starting train.exe directly. By default, the MSTS installer points the shortcuts to start launcher.exe. But launcher.exe will not turn around and pass on the extra information you gave it to MSTS.
So, to start the game normally:
C:\Program Files\Microsoft Games\Train Simulator\train.exe -mem:nnnn
To start the game windowed:
C:\Program Files\Microsoft Games\Train Simulator\train.exe -vm:w -mem:nnnn
To start the Route Editor or Activity Editor:
C:\Program Files\Microsoft Games\Train Simulator\train.exe -toolset -mem:nnnn
Keep in mind that the path shown here is the default path to train.exe....which is likely different on your system.
#18
Posted 28 January 2013 - 09:50 AM
#19
Posted 28 January 2013 - 07:32 PM
As some of you know, my own route, where I am experimenting with 2048 and 4096 terrtex tiles, 1024 and 2048 aces for the trees close to the tracks and ridiculous numbers of forest regions, has been having issues with Tim's NP W class steamers double headed. Frame rates have been dropping in the worst areas to 5-8 fps. I changed it to -mem:2048 and in a couple spots the rates have dropped to 37, otherwise staying in the mid 40's to mid 50's! Almost no stutters anywhere! It's a new route!
Steve
#20
Posted 29 January 2013 - 02:37 PM
Noisemaker, on 28 January 2013 - 09:50 AM, said:
Won't affect performance per se, but If you're using a paranoid operating system (Vista or better) you should always be using Run as Administrator with MSTS to ensure it has the proper permissions.
Noisemaker, on 28 January 2013 - 09:50 AM, said:
You'll be "hindered" without the use of the "mem" switch, which benefits the Route Editor just as much as the normal game (some might say more!...see above :yahoo: )