OUT OF MEMORY?

[wopflyer]

I have modified a lot over the years and don't want all my stuff overwritten.

The best way to handle this is to make a script that automatically applies all your mods. You just run the script after a local files verification or a reinstall.
We have an example here: viewtopic.php?f=6&t=5383
My own implementation is better but more complicated.

Thanks Chacal.

[trev123]

I wonder if this issue could be caused by modifying scenarios. I purchased the MML route form JT https://www.justtrains.net/product/midl ... ield-derby and as you can see it has a lot of payware which most I have except the JN wagons since purchased and the AP Class 156. I paid $50 NZ for this route and $10 NZ for the wagon but the AP Class 156 was going to cost me $60 NZ so I decided to swap it out with RW Tools with APs Class 150. I did this and now that scenario I swapped out the DMU with now crashes to desktop with the out of memory message ending in 05. It also suggests I run TS in 64bit version which I am already doing. Before I did this when I loaded the scenario it said cannot find rail vehicle AP Class 156.

[peterhayes]

Trev
On occasions when I have swapped out items using RW-Tools including IHH, AP, JT, etc DLC I have experienced an OOM error with the xc05 code. (It was "Access Violation" in the old days!!)
This is a pretty vague error that can be caused by an "invalid Page Fault", AV Sofware, Firewall Settings, Windows Defender settings, DEP settings the list is endless.
Basically, and this is supposition, the DLC you are trying to swap occupies certain memory addresses in both the VAS and the working set in the RAM. Now when you use RW_Tools it may not entirely clear, (one or the other) the memory addresses, so when you load the scenario these addresses are no longer available to the item you have swapped in and you get the dreaded OOM. Or, the memory addresses occupied by the item you want to swap are significantly different to the item you want to use, protected, different, smaller, larger, etc and you get the OOM yet again.

Its a complex idiosyncratic issue that doesn't always happen, but it usually means that the amended code in the scenario is trying to access addresses in the RAM (as instructed by the OS/VAS) that are not available for whatever reason. That is an OOM at a particular address or set of addresses. As you can see the base game is not affected because you can open it immediately with a Scenario that has worked in the past.

Any message in "View Reliability History"?

pH

[trev123]

No nothing there Peter.

[jtousign]

Hi, I also live with that frustrating problem with all the Workshop scenarios mode and all the HSC scenarios, even the career ones!

[jtousign]

I uninstalled the HSC and reinstalled it, everything goes fine now! Yes!!!

[dr1980]

I can confirm that uninstalling and reinstalling HSC fixed my out of memory issues, both with running the centipede and downloading workshop scenarios. Good find!

[RudiJaeger]

I can confirm that going from Win-7 to Win-10 (and new gfx drivers) does not cure the OOM issue. Still getting them in the world-editor whenever manipulating memory-intensive objects (track, lofts, tree blocks, etc); and it also seems to be time-related, as I can still leave the sim running untouched for an hour or more, and it will eventually crash on it's own.

I have not tried the HSC course of action yet; sounds interesting. Any change-logs or other documentation (or ideas) that describe what happened in HSC that would influence the entire sim?

[buzz456]

I can confirm that going from Win-7 to Win-10 (and new gfx drivers) does not cure the OOM issue. Still getting them in the world-editor whenever manipulating memory-intensive objects (track, lofts, tree blocks, etc); and it also seems to be time-related, as I can still leave the sim running untouched for an hour or more, and it will eventually crash on it's own.

I have not tried the HSC course of action yet; sounds interesting. Any change-logs or other documentation (or ideas) that describe what happened in HSC that would influence the entire sim?

The sim crashing after a hour of not doing anything is not normal. I have wandered off watched the boob tube for a while gone to bed and got up the next morning to find the sim turned from day to night and still waiting patiently for my return. Something is leaking on your game for sure. I will tell you when route building particularly when putting down the various ground textures that it eats into RAM. Clearing the RAM regularly will keep the thing from crashing and I always hit the F2 before a save. I have said this before but I will repeat. There are probably other utilities that do this but the IOBIT Advanced System Care (yes there is a free version) has a nifty little program called Monitor in it which just sits in the corner of your screen and you can manually clear the RAM at will. I almost never get a crash when painting or putting down scenery by clearing this ever five minutes or so.

[_o_OOOO_oo-Kanawha]

And DTG still clueless?

Were there any such Out Of Memory problems and crashes before the "eye candy" update?

There must be some memory buffers set too small, a memory leak or whatever. Judging by the deteriorating standards of DLC and continuous lack of QA, only the scarcest resources are available for addressing this serious bug, and DTG are either too stubborn or too proud to admit their errors?

Only Minerman, TomCat, FireExplorer, the MRL crew and some other dedicated developers, who aren't in this business for money, but rather for their own pleasure (and some pride too ;-) keep me interested in TSxx.

Black Friday, Christmas Season Sales and such are quickly approaching but I am not tempted to throw DTG any more of my money, no matter the discount. My wallet does the voting.

[minerman146]

2-8-4,
I'm honored to keep you interested in this thing of ours. Thank you sir.

[buzz456]

And DTG still clueless?

Were there any such Out Of Memory problems and crashes before the "eye candy" update?

There must be some memory buffers set too small, a memory leak or whatever. Judging by the deteriorating standards of DLC and continuous lack of QA, only the scarcest resources are available for addressing this serious bug, and DTG are either too stubborn or too proud to admit their errors?

Only Minerman, TomCat, FireExplorer, the MRL crew and some other dedicated developers, who aren't in this business for money, but rather for their own pleasure (and some pride too ;-) keep me interested in TSxx.

Black Friday, Christmas Season Sales and such are quickly approaching but I am not tempted to throw DTG any more of my money, no matter the discount. My wallet does the voting.

Please just stop. If you have nothing to contribute except complaints please refrain from posting.

[trev123]

And DTG still clueless?

Were there any such Out Of Memory problems and crashes before the "eye candy" update?

There must be some memory buffers set too small, a memory leak or whatever. Judging by the deteriorating standards of DLC and continuous lack of QA, only the scarcest resources are available for addressing this serious bug, and DTG are either too stubborn or too proud to admit their errors?

Only Minerman, TomCat, FireExplorer, the MRL crew and some other dedicated developers, who aren't in this business for money, but rather for their own pleasure (and some pride too ;-) keep me interested in TSxx.

Black Friday, Christmas Season Sales and such are quickly approaching but I am not tempted to throw DTG any more of my money, no matter the discount. My wallet does the voting.

No, they are not. Quote from DTG Daniel on Steam.

As I've stated thus far we have been unable to replicate the issues experienced by a small number of users.

We have access to hundreds of computers and not a single one of these is having the persistent issue some users are experiencing which is why we are asking for people to send in tickets so we can request additional information as required.

So far in order to try and replicate it, we have purchased additional hardware ranging from an affected Xonar sound card and accompanying driver to a specific brand of Bluetooth headset.

Another thing to note is that just because you may have faced an issue it doesn't mean it's the same as anybody else's even if the error message is alike so thread highjacking really just confuses other users especially those who haven't followed any of our advice regarding technical issues:

https://dovetailgames.kayako.com/Knowle ... cal-issues

When it doesn't that's when we can investigate further in hopes of determining the cause of the remaining issue.

For instance just yesterday I was made aware that a specific Windows update released last Tuesday was causing a users game to crash whilst I myself have not experienced the same with exactly the same update installed.

With the update removed the game functioned without issue with no additional changes being made.

A quick Google search revealed hundreds of different people having issues with this update across all sorts of different hardware and affecting different software in multiple different ways.

So in summary, if you are having an issue submit a ticket.

Include a DxDiag and make sure you have followed all of the steps in our guide as this ensures the game is not only in its default state but all of its dependencies are functioning correctly as well.

As we can't debug an issue our end if it turns out something entirely disconnected from it is the cause.

[thegevo5k]

I've had OOM a few times on TS2020. There is something funny about the error though.

If you are streaming Train Simulator on Discord, and you stop streaming, the game will crash.

This NEVER happened in TS2019. Something got jacked up in 2020.

[trev123]

Something wrong with your computer then. Read the quote from DTG.