by Tomcat » Tue Nov 07, 2017 6:35 pm
I've spent the afternoon trying to replicate these crashes and so far I haven't been able to.
The first test run I did was from Mojave till 10 miles East of the Palmdale siding on the cutoff. Before starting TS2017 I noted that total memory usage was 23% of 16 Gigs (I have a lot of crud running in the background that I should look into pruning). After Starting TS2017 and getting into the route at Mojave the memory usage goes to 33% and stays there for the entire session. I'll list the exact memory usage of TS2017 for several points along the way;
2 Miles North of Mojave - 1504MB
Mojave - 1686MB
Rosamond - 1576.7MB
Lancaster - 1654.4MB
Palmdale (Mojave Sub side) - 1704MB
Palmdale siding (on the cutoff) - 1661MB
My fps was hanging around 85 to 105 most of the way except for a low of 54 in Palmdale.
I tried the same route 2 more times, once in each direction with an 80 car consist and once just with the light engines provided in the Mojave free roam with consistent results in all 3 runs. I'll try similar length runs from West Colton, San Bernardino and Yermo.
Specs for my machine are an MSI laptop running Win 10 with an i7-7700HQ @2.8 - 3.8 GHz, GTX 1050 2 gigs ram and 16 gigs memory.
Download the PRB from page 51 of the Powder River Basin thread.