Tomcat wrote:_o_OOOO_oo-Kanawha wrote:So the Task Manager shows 1.4 up to 3.1 GB? 3.1 for a large route with only 1 player train in service is rather a lot. A couple of AI trains might raise the memory to 3.5 GB. Anything above 3.5 GB will cause a fatal crash.
This has bothered me for the past few days. Turns out I'm an idgit! 3.1 GB seemed liked more than I usually see when I have Task Manager open so I went back and double checked a few spots on the route and it seems I made a boo boo in the initial reporting. 3.1 GB was the total memory usage of TS2016 combined with the OS and whatever other stuff I had open at the time. Checking just the memory usage of Railworks.exe I can report a less stressful 2.1 GB as the highest I've seen the usage go, even in built up areas such as San Bernardino. In non urban/suburban areas the memory usage hangs around 1.6 GB or so. Sorry for the initial error, perhaps I can blame it on age.
Thanks for clearing that up. Hate to see a great potential route go to waste under real operating conditions.
Like the Minermen on their New Jersey route project, do you also make maximum use of a relatively limited number of assets by stacking, scaling, turning and combining them in many different, previously unseen ways?


