Train.exe memory switch use of command line memory switch
#1 Inactive_torque_*
Posted 16 January 2013 - 10:45 PM
David
#2
Posted 17 January 2013 - 12:16 AM
Yes, it is more reliable.
cheers
Derek
#3 Inactive_torque_*
Posted 17 January 2013 - 09:13 AM
David
#4
Posted 17 January 2013 - 09:28 AM
#5
Posted 17 January 2013 - 10:02 AM
I'll try the 2048 myself now, as GTA has been a PITA lately. :oldstry:
#6
Posted 17 January 2013 - 10:07 AM
#7
Posted 17 January 2013 - 10:29 AM
#8
Posted 17 January 2013 - 10:53 AM
Too bad the BIN didn't do something about that. ;)
:oldstry:
#9
Posted 17 January 2013 - 10:58 AM
#10
Posted 17 January 2013 - 12:26 PM
Noisemaker, on 17 January 2013 - 10:29 AM, said:
Most folks have gotten an erroneous view of the memory switch by reading the myths on places like trainsim.com. There is no 1024 "max". By invoking 1024 in the mem switch, you will not directly get 1,024 m assigned to "train.exe". You can easily demonstrate this to yourself by having Task Manager/Resource Monitor open when you fire up MSTS, then Alt-Tab to them from time to time.
You really have to work MSTS hard to get the memory assigned to approach anywhere near 1,024 m. Initial conditions for most routes may surprise you when you see such low initial mem assignments, so here's a couple of examples of fairly demanding routes. The first number is no mem switch, the second is either 1024 or 2048 (more on that later).
One point to make is that the place chosen to start can greatly affect initial assignment.
SeaView5 - 261 m, 351 m
Surfliner2+CajonPass Merge - 343 m, 549 m
What you will notice then is that mem assigned will increase as you work the route; sometimes a little, sometime markedly. I picked those two routes to talk about since in both I can exceed 1024 provided that the mem switch is set to 2048.
For SV5 I have an ITR that tours the whole thing and takes about 3.5 hours. The assigned memory climbs above 1200. A few times it has reached 1251, and that's the kiss of death on my machine (hard lockup, but I can get to Resource Monitor). So far I have not been able to push the "Surfing to Barstow" route to the killed condition.
As far as I can tell, those are the only two routes I have that actually use part of a setting of 2024. I just leave it in place, since with any operating systems from Vista onward with their better memory management, it surely does no harm...
regards,
charlie