"Out of Memory" error with Penn Steam Route

[SD402]

Well, I've encountered a error I've never had before when running the freeware Penn Steam route.

I had to re-install TS2020 due to a screwup on my end involving some confusion with addons. After re-installing TS2020, the first thing I re-installed was the Penn Steam route. Well, it no longer boots, crashing to the desktop with the "Out of Memory" message, even when I closed down some memory hogs to help. What's frustrating is that it worked just fine on a previous installation of TS2020 with the same settings. The Six-Wheeler and Santa Fe locomotives work just fine.

Here are my System specs. These are the same ones at the time the route loaded.

OS is Windows 10 Home
CPU: Intel i5-8400 CPU @ 2.80 GHz.
GPU: Nivida GTX 1060 3GB
RAM: 16 GB of RAM

This is on a fresh install of TS2020, with only the Steam DLC and 3 Workshop routes loaded, nothing else. I have the US and European Loco and Asset Packs installed and working.

I am using the 64bit executable currently.

Thank you in advance.

[buzz456]

System sure is fine but you already know that since it ran before. Try uninstalling the route and then reinstalling it. Also run a verify to make sure that your new install has all the stuff it needs. If that doesn't work we will probably have to move on to the torturous logmate route.

[SD402]

Thanks for the help.

Well, I went through and verified the files. (Which came back just fine.), and uninstalled and reinstalled Penn Steam. To make sure it wasn't something else, I tried a Penn Steam scenario I knew to have worked in the past. ([Six Coupled] Shenango Work Train)

Still got a "out of memory" message. And Railworks didn't increase it's memory usage at any time.

Overall Graphics setting is "High".

[GreatNortherner]

This Out of Memory thing is so confusing!

I have no idea what might be happening here so this is going to be a long shot:

Have you tried starting in 32 bit mode, just to see what happens?

Also, did you install any 3rd party mods that may in any way touch the route or its content (or the referenced Kuju assets)? -- I know this is unlikely since you just ran the "verify".

And before I run out of ideas entirely, as a last resort, I would try and unsubscribe (and then physically delete from the HD) the Workshop content. I've seen it a few times that files got corrupted when downloading which caused strange issues (at one time even making it impossible to even get to the main menu). I don't know how a totally unrelated Workshop file could interfere with the running of this route but then I don't know what is going on here and, as I've said, this would be my last resort.

Cheers,
Michael

[buzz456]

Run logmate and post the results if you don't understand what it's saying. That will at least tell us where it's hanging up.

[JohnS]

the only time I ever got this error was when I had things from the workshop installed. even when they didn't have anything to do with the route giving the error.

[SD402]

Okay, here's the things I tried.

Run in 32-bit mode: That just made it crash faster.

Removed all workshop items (The 3 fictional routes that originally came with TS): Didn't do a thing.

Re-installing the route: Didn't do a thing.

ts-2020-08-23-13-23-28.log

Attached Logmate: I noticed a few errors at the end, but I think that you all will be better at noticing any errors.

[BigBoyMoon]

Go to the folder in the TS install labeled "Install" and try running the dotnet framework, as well as the other executable in there to reinstall some of the games dependencies. It's a long shot but RunTimeError may stop showing up, at a minimum. I would also try running the game as an admin, if you haven't already

[JohnS]

Okay, here's the things I tried.

Run in 32-bit mode: That just made it crash faster.

Removed all workshop items (The 3 fictional routes that originally came with TS): Didn't do a thing.

Re-installing the route: Didn't do a thing.

ts-2020-08-23-13-23-28.log

Attached Logmate: I noticed a few errors at the end, but I think that you all will be better at noticing any errors.

When you removed the workshop items did you delete the files left behind in Railworks Directory?

[peterhayes]

If you want to make sure that you have removed all WS items from TS - you need to try this:
If it is to do with workshop scenarios and/or a corrupt scenario database try this:
(This is for errors that occur where TS20XX is loading, checking, verifying the scenario database on start – up.
NB: Verifying the game files won't fix a WS scenario problem. and for OOMS with a WS route/scenario)

Open Steam and highlight Train Simulator.
Click on The Workshop Tab
Click Browse then Subscribed items.
Individually unsubscribe each scenario or choose Unsubscribe all to get rid of the lot.

Just because you have unsubscribed WS scenarios via STEAM does not mean that they have been removed from your computer. Invest in the FREE TS-Tools and remove them route by route - they are colour coded - blue.

Additional method to check:
Delete all WS scenarios from your computer, navigate to \STEAM\steamapps\workshop\content\24010 and delete every file and sub-folder in that folder. DO NOT DELETE the \24010 folder itself (If you want to keep any or all scenarios then copy the contents first to a safe place before deleting the files and then reinstall once your error is fixed.

Once you have done that you need to close TS delete/rename the following files:
navigate to:
\STEAM\steamapps\common\RailWorks\Content and delete/rename the following 4 files:
SDBCache.bin;
SDBCache.bin.MD5;
RVDBCache.bin;
RVDBCache.bin.MD5;
(and if you want to reset TS graphics/monitor settings del/rename playerprofiles.bin file as well.)
Restart steam and TS
If not to do with WS scenarios - ignore this!

Looking at your logmate file suggests that this was a TS error per se but how Windows and TS and your computer interacted - it has NOTHING to do with the amount of RAM installed it would have happened if you had, 64GB installed.
I would love to see the windows log, "View Reliability History" to see if that recorded any error at the time of the crash?
pH

[SD402]

When you removed the workshop items did you delete the files left behind in Railworks Directory?

Yes, I did. I should now probably mention that the three routes in question (Hedborough North, Seebergbahn, and Castle Rock Railroad) did not cause problems in the past. In fact, I had a whole bunch of addons installed before I wiped it clean. (User error on my part in that regard.)

Also, every other route works just fine on the system. It's only when I try to load Penn Steam does it crash.

After I uninstalled Penn Steam, I installed another third party addon route, Maine Martime, and that works nicely. I'll keep trying and poking around at things.

I did go over and read the Windows error logs, nothing for the sim came up.

[SD402]

Update:

Turns out I badly screwed up my install again, having all sorts of leftover files, including the workshop routes for some reason. Cleaned all of those out, and re-installed it, sans workshop content.

Going to run some UP equipment on the Surfliner route to relax a bit, and take a look at this again tomorrow.

[plethaus]

I'm trying Penn Steam for the first time (on 64 bit) and also keep getting out of memory errors. I do not have any workshop content installed (or ever had any on this install.) The only DLC is even have installed is Western Lines of Scotland, Stevens Pass, Weardale and Teesdale and Penn Steam. Thanks for any help anyone might be able to provide, and extra huge thank you to the Penn Steam team for making it free for everyone. Although I can't keep it running for long, it's obviously a pure labor of love!

[plethaus]

Well this defies all logic and reason, but some googling led me to a few comments about the 64 bit executable being the culprit for these OOM errors. Sure enough, after switching to the 32 bit one, I have not had an OOM error once yet. Train Simulator by Dovetail Games, ya gotta love it!

It needs to be said again though how amazing this route is. Authentic, beautiful, unique, and FUN.

[trev123]

As this is a freeware route why blame DTG when it is something out of their control.