When I start the game, everything is white with a few graphic bugs and I get a error massage. I have a really good computer with 32 GB RAM.
Open your RailWorks folder and run LogMate.exe. Then start the game and redo the same thing that led to the crash. After that, look for the .log file(s) in the RailWorks folder, zip and attach here. Default location: C:\Program Files (x86)\Steam\Steamapps\common\RailWorks\LogMate.exe
I had to send it via ZIP, because it didnt let me post the log. But I saw something weird. At the top the stand verification failed even tough I have legit copy on steam. (It ould be because I made a backup and dragged it into the RW folder.)
Assets\Kai_8090\Südbahn Wien HBF-Wr.Neustadt Hbf\PreLoad\Commuter\OEBB_Cityjet.bin appears to contain invalid data Assets\Kai_8090\Südbahn Wien HBF-Wr.Neustadt Hbf\PreLoad\Commuter\OEBB_Cityjet_Doppel.bin appears to contain invalid data Reinstall that one - it's broken. Other than missing assets (which should not crash the game) I don't see anything. One thing you could try is reverting the game settings to default by deleting RailWorks\Content\PlayerProfiles.bin
I have just encountered the same. Started the game, Drive, Standard, Search 272. Spent a couple minutes around, came back to this error screen. I suppose it's related to workshop, one way or another. According to the following file, it was uploaded successfully: CrashRpt-Log-20240531-131446-{84e99684-1f01-4291-8654-1dcc83dc9768} Just for completeness' sake, here is the dialog (Ctrl+C copies the text): --------------------------- RailWorks --------------------------- Saved log to... C:\Program Files (x86)\Steam\steamapps\common\RailWorks\TempDump\ Exception Code: 0xC0000005 Exception Info: OUT OF MEMORY Fatal error in mode FRONTEND. 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 https://dovetailgames.freshdesk.com --------------------------- OK ---------------------------
Why don't you tell us route / scenario? That's not much of a bug report. "272" crashes. No LogMate either...
The CrashRpt is uploaded for DTG. It hopefully includes stack trace and all. If it doesn't, they have to improve it. The only intention of publishing this is to let others know that stuff happens. I think it's the job of DTG to fix the game. If you are working for DTG now, then it's simply an unhandled exception on a thread that sometimes interacts with the UI. The game is visibly idle after loading the scenario list, only some background stuff is happening, most likely workshop. I've had these subs for years without an issue, except now the reinstall means they're all processed again.
Sorry for my interest in that case. Like it or not, I'm angry if someone posts an issue and then won't share information what happened - then why post it at all?
Resisting an Angry Bird meme! I appreciate your desire to help. I shared all information available. Start the game, go to scenarios, leave it there, it just crashed. Can it be reproduced? Probably, in a wee 30-40 hours redoing all steps I did, including adding and removing DLC, clearing cache... I am deeply involved with development and this kind of information is all that I ever needed. Everything else is blame shifting. In line with your question, the very first thing to do is log a damn stack trace. It's C#. It can do it. In fact it does it by default, every Exception has the property. No need for LogMate. Absolutely. Ever. Hopefully it is part of the Crash Report actually submitted. I wish to see more DTG involvement in these forums. Just like Blizzard they keep directing players to a different bug reporting platform every few years, and according to player feedback they are the equivalent of a black hole. No status, no feedback, no fixes, nothing. Not even acknowledgment. That's why I post these things. Either I win by helping them fix it, or I win by exposing (and repeatedly proving) an attitude.
That is not LogMate, which tells you which line of the TS code has an issue with which asset. The CrashReport is of no use - it will only detect errors in your Windows installation, but you have a corrupt file which is nothing DTG are responsible for. That's why LogMate is there. I enjoy fixing stuff, but not useless discussions.
Alright, so it turns out that I now have some garbage workshop files again. As usual the source is fine, deleting them does the fix, so the problem is that TSC still cannot reliably extract several scenarios in a single session / sequence. Apparently it can even suicide in the process. I didn't expect this since I was checking several earlier, plus I've been running the game many times before. I noted that a lot of workshop downloads have been eliminated, though - the Steam folder being there but empty, but still subscribed, and presumably redownloaded again later. While I've learned to not use workshop anymore, I still have plenty of subs that I played one by one, slowly, removing afterwards. One can learn to always run / restart TSC after every single sub (however poor that sounds), however a reinstall is quite impossible in this sense. So the game probably didn't die from the UI per se (mode: frontend) but simply during it (workshop is aborted or paused when starting a scenario). I've been reporting this issue for nine years.
Today I started TSC three times. First it crashed. Second it crashed. I remembered LogMate, so the third time it didn't crash, but it caught some proof of its inability to probe rl y ead f___illes. rain lumator lassics StreamBeader impppppppplementtttation isssssss baa__$djljadsfd. (I have no brain damage, just simulating the simulator. ) Source data files are not corrupt.
