|
|
Post by DeepChillWolf on Apr 27, 2020 21:13:58 GMT
I have noticed that it seems like S7 stopping markers are causing my TS to crash occasionally. When the train encounters the object, my game either crashes or hits a mostly unnoticeable lag spike. I assume this is a bug, as I am not having issues otherwise (except for one crash on a junction and in the main menu). Sometimes it'll give me an out of memory error. However, it haven't got one recently so I can't take a screenshot.
UPDATE 1: This seems to be happening on the Metropolitan Line also. This shows that it is not just the District Line Route. I'll have to check if this happens with other trains.
UPDATE 2: This also happens on other units such as the C stock.
Processor: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz 3.50 GHz
Installed Ram: 8.00 GB
System Type: 64-bit operating system, x64-based processor
Railworks Version: x64
Graphics: As suggested by VDL Team
Graphics Card: Geforce GTX 950
|
|
|
|
Post by Xavier on Apr 27, 2020 21:22:55 GMT
Possibly either you have a corrupt install of the Metropolitan Line/S7 or you're running out of memory.
|
|
|
|
Post by DeepChillWolf on Apr 27, 2020 21:48:06 GMT
What is weird is that this problem wasn't happening yesterday. The game isn't lagging terribly with the S7 which means that it isn't likely my memory.
|
|
|
|
Post by Jimi on Apr 28, 2020 1:21:07 GMT
It's not "your memory" per se - either PC RAM or GPU. I have 32GB of fast RAM and an Nvidia GTX 1080 GPU with 16GB, and I get TS OOM (Out Of Memory) errors, although less so with the 64-bit app. Editing with the 32-bit app can be a pain. There are known issues with TS and memory errors. I don't recall ever getting an issue with the JT stop markers, but that you are with 2 different routes and multiple trains suggests its the action of the marker that's at fault. Have you tried different scenarios or QuickDrive? If it happens in multiple situations, that tends to point to an object corruption of some kind.
I can only ask the same question that I ask to this team when something "stops working" - what changed? Something had to. We're glad to try and help, bu you may also with to contact JT's support folks and ask there too.
|
|
|
|
Post by DeepChillWolf on Apr 28, 2020 2:08:30 GMT
It's not "your memory" per se - either PC RAM or GPU. I have 32GB of fast RAM and an Nvidia GTX 1080 GPU with 16GB, and I get TS OOM (Out Of Memory) errors, although less so with the 64-bit app. Editing with the 32-bit app can be a pain. There are known issues with TS and memory errors. I don't recall ever getting an issue with the JT stop markers, but that you are with 2 different routes and multiple trains suggests its the action of the marker that's at fault. Have you tried different scenarios or QuickDrive? If it happens in multiple situations, that tends to point to an object corruption of some kind. I can only ask the same question that I ask to this team when something "stops working" - what changed? Something had to. We're glad to try and help, bu you may also with to contact JT's support folks and ask there too. Well, this happens on both QuickDrive and various scenarios. I have contacted JustTrains support and am awaiting a response from them. Nothing seems to have changed except for trying out different routes on QuickDrive. The S7 was running fine yesterday on the Metropolitan Line, but when I changed to the District from High Street Kensington - Olympia, the sim crashed on a junction. Then the next time I tried a route on Quickdrive (Gloucester Road - Richmond) using the same train as previously, the sim crashed yet again while hitting the stop marker at Barons Court. Not every time I stop at a station triggers the crash, as it seems to happen every once in a while. |
|
|
|
Post by Eddie on Apr 28, 2020 13:02:08 GMT
Emptying out your Temp Dump folder is a good move. It will just get bloated by these crashes. Often this will cure the issue as well.
|
|
|
|
Post by DeepChillWolf on Apr 28, 2020 14:45:02 GMT
Saved log to... E:\Program Files (x86)\Steam\steamapps\common\RailWorks\TempDump\ Exception Code: 0xC0000005 Exception Info: OUT OF MEMORY The system is unable to run this scenario on the current configuration, we suggest either lowering the graphical quality settings or attempting to run the game in the 64-bit version, if this fails to resolve the issue please contact our Customer Support Team at dovetailgames.kayako.com |
|
|
|
Post by Jimi on Apr 28, 2020 18:00:47 GMT
Yes, sorry but we all get those errors from TS since about 2 updates ago. It's not the route, or train, or JT's S7 gadget. It's TS. UKTS and similar boards are full of related posts. No one's found an answer yet, short of DTG fixing it.
|
|
|
|
Post by DeepChillWolf on Apr 28, 2020 22:16:15 GMT
Well, this is fun. There goes my video idea on TS.
|
|
|
|
Post by DeepChillWolf on Apr 28, 2020 22:44:49 GMT
Is it not possible to possibly remove any objects that are affecting the game? It's going to make things very difficult having to use OpenBVE for stuff.
|
|
|
|
Post by Jimi on Apr 29, 2020 13:08:38 GMT
This isn't about objects affecting the game. It runs fine, most of the time, for most people and there are many people creating videos and streaming TS scenarios including the VDL ones. It is more about how an individual's system is set up, and TS options and settings that cause a higher load on the system resources. If anything, it's DTG's problem to solve - not route builders, not us, not JT. We have done all we can to make our trains and scenarios be reasonable in terms of resource need. So the few things we have been able to determine make it more likely TS will run without OOM errors include: Run the TS 64-bit version, not 32-bit. This is essential.
Clear out the TS Temp Dump folder. If you're getting OOM errors there will be a load of logs in there.
Try clearing the TS tools cache TS Options -> Tools -> Clear cache (note TS will restart an use the 32-bit version of TS so you will need to exit that and re-start the 64-bit version!!)
Reduce your graphic settings in TS Options to lower the load on TS. View distance, Shadow detail and water detail can be very resource heavy.
Check sites like UKTS. There are a lot of posts on there relating to OOM errors and TS tuning.
EDIT: Just noticed a few more things re your system. 8GB is close to the limit with Win10. I'm running 32GB and as I type I see I'm actually using 7.6GB, and I'm just running windows and Firefox right now. Not TS. So 8GB seems iffy for running TS with fairly complex routes and trains. Secondly - what graphics card are you using and how much memory on it? So although TS OOM errors can also happen on big systems, it is *possible* you are indeed out of memory.
|
|
|
|
Post by DeepChillWolf on Apr 29, 2020 17:28:28 GMT
I'm using an a Geforce GTX 950. It's a few years old which might explain things. I've tried doing everything but clearing my cache and changing my settings (that's my next step). I can't believe I'm already in this situation as my computer was on the high-end side of things when it came out. I'm not really in the mood to pay a couple hundred dollars after I just purchased the route. Thanks for helping. I'll let you know once I've adjusted my settings.
|
|
|
|
Post by DeepChillWolf on Apr 29, 2020 19:07:24 GMT
I've tried every piece of advice and the game still crashes. Is there a tracker thing that can show if it actually uses up all my memory?
|
|
|
|
Post by DeepChillWolf on Apr 29, 2020 19:46:17 GMT
Interestingly enough, the game was using most of my free memory, but there was plenty of standby memory left.
|
|
|
|
Post by Eddie on Apr 30, 2020 17:56:46 GMT
Try doing a File Integrity Check to put your TS installation back to a default condition. Something you've added has borked your install. Often a FIC will recover a broken installation.
|
|
|
|
Post by DeepChillWolf on Apr 30, 2020 21:23:12 GMT
Won't it get rid of my assets like the Met Line?
|
|
|
|
Post by DeepChillWolf on May 1, 2020 0:53:54 GMT
No luck sadly.
|
|
|
|
Post by DeepChillWolf on May 3, 2020 4:05:30 GMT
Should I purchase a new graphics card or more ram?
|
|
|
|
Post by Xavier on May 3, 2020 6:13:25 GMT
Should I purchase a new graphics card or more ram? I would try doubling your RAM first as it's ultimately cheaper and easier while still likely to have a positive effect. It was 8GB you had at the moment? Look online at how much the compatible 16GB RAM is, and also have a look inside your PC at how many RAM slots (2 or 4 typically) you have as you might be able to push it up to 32GB or 64GB if it's still in price range. |
|
|
|
Post by DeepChillWolf on May 8, 2020 23:10:55 GMT
Are you kidding me? I just spent like 40 dollars on 8GBs more of ram, and the sim still crashes.
|
|
|
|
Post by DeepChillWolf on May 8, 2020 23:11:43 GMT
Totalling to 16GB... I'm not sure if it's worth even contacting Dovetail Games, as they'll do nothing about it.
|
|
|
|
Post by DeepChillWolf on May 8, 2020 23:23:42 GMT
DxDiag.txt (70.92 KB) I'm not sure if DxDiag would help. But here you go, anyways.
|
|
|
|
Post by DeepChillWolf on May 9, 2020 4:04:33 GMT
Should I try disabling "NIVIDA High Definition Audio" and only enable "High Definition Audio Device"?
Edit: I did it anyways to no avail.
|
|
|
|
Post by DeepChillWolf on May 9, 2020 5:07:37 GMT
Good News: I think getting rid of SDBCache.bin fixed things.
|
|
|
|
Post by Jimi on May 9, 2020 10:42:28 GMT
You didn't get rid of the cache file, but rather forced a re-build of the scenario cache. Doing this periodically, especially if you've added/removed routes or scenarios helps. Same seems to be true re the Tools cache.
I would also bet the adding the 8GB RAM contributed too.
|
|
