Train Simulator Classic – Core Update & Route Refresh

Exact same issues here.

Game hangs, When you click drive. See image

 

It works perfectly for me, with perhaps a slight improvement in frame rates.

 

That with chache I´ve already tried. No change.
The Steam verfiy should be do someone else first. I have too many route upgrades installed must do firstly a fresh backup of them.

 

I cleared the cache but the problem persists; the game hangs when i click drive

 

Afraid I am also experiencing a frozen screen when trying to select a route from the main drive menu in both the Career and Standard Tabs.
Clearing the Cache has not helped.

 

In the tempdump folder I find only some text files; this is the last one.

 

It probably has to do with the image.png Those larger than 1 Mb cause problems.

They can be found in /LocoInformation and RouteInformation

 

As far as I'm aware, for a few years now TS automatically uploads the dumps to a website - refer to the end of the log you just shared.
It can be useful as it has an identifier in it, so your story can be connected to the dump.
But in general, TSC people should have a fair amount of logs sitting in their queue. Unless it's already redirected to /dev/null.

 

What is the fastest way to solve this. Because with the amount of content it's a lot of work. It was not a problem before the update.

 

If I click on the create button to modify a scenario, I can play; the crash then occurs when I finish the scenario

 

Alright works as usual for me otherwise reinstall the game you lazy buns

 

Working ok for me. I upgraded and immediately cleared cache, exited and restarted. I'm running Win10 home with TS in 64 bit. Tested an old scenario that always OOms if run first, still OOMs. Havne't done logging yet to see if error logging gives any clues.

 

The bug seems to be caused by PNG files encoded with Adam7 interlacing, which Train Simulator can't handle since the latest update. As soon as you encode the PNG images differently, everything works and there is no more freezing.

 

I usually get a 1 in 10 chance of the game locking after loading the first menu, after pressing "play" the spinning disc appears and I need to crash out and reload, which is almost always successful.
After the upgrade, the third launch of the game had the same issue, this time I rebooted the PC in case there was anything left in memory from the previous version, so far so good. Editing routes and playing the game is OK though, it rarely crashed and so far no crashes. 32GB of RAM helps.

 

I agree with that - just tested several routes that caused failure of menu - Stainmore from SSS and Wycombe workshop route. In both cases deleting the image.png in the Content/RouteXXX/Routeinfromation directory allowed the menu to load. Replacing the image.png with one opened and then resaved in a basic.png format allowed the route picture to show and the menu to load.
I then tried this with locos that were also preventing menu loading by editing the image.png in the loco information directory. Same result in that the menu now loaded. Brilliant discovery by OEBB_8073 - much obliged

 

Just confirmed this. I didn't have any issues normally but having searched for 'Stainmore' the game locked up. It didn't crash as such, just stopped. Something similar happened earlier on when picking locos but I assumed it was just a normal crash, but now we have evidence DTG should look into it.

 

Problem not only with route images but
also with loco images which make the
game crash,weich didn't happened before.

 

Exact same problem.
However, I can play by using the Editor and the pressing Play

 

TBH its not an issue I would have expected DTG to spot as its one that arises from freeware and 3rd party developers producing the .png files and the cause is so subtle I wouldn't have realised it was an issue if I was making.png files for my stock ( which is all OK 'cos I just tested it). I think DTG are firmly off the hook on this one.

 

Not entirely. They deleted the code that allows the game to view photos with the specific type of interlacing that is used by some routes and trains, so the game has no idea what to do with the file when it tries to load it. Granted it would have been better if it defaulted to the generic dummy image instead of locking up, but I expect it's an easy fix for DTG.

 

I have just checked with an original copy of the image for Stainmore that was causing the menu to lock up. Opened the image in the bog standard windows Paint app and simply resaved it. I did reduce the image size to get it to load faster but that was only after testing. I bow to superior knowledge about interlacing but when I have created image.png's for my stuff I just used the default methods in paint and Paint.net so I guess it is just a function of the fact that TSC is a great place for developers but it comes at a cost of occasionally inconsistent approaches to things that turn out to be oddly critical later. It always was the case - I remember the great track sleeper problem from one update that meant that I had to reissue all my narrow gauge tracks - my fault entirely.

 

Steam locked up for me initially. Did an uninstall and full reinstall. Seems to be working fine. Third rail also working. AP products running fine.

Running on Windows 11. Frame rates seem much more stable.

My suspicion is a full reinstall is possibly a wise move. It will defrag the TSC files and integrate them properly with the new software platform.

Regarding older imports/Workshop files I cannot comment.

 

This worked for to at least run some scenarios: For those TSC users who are having spinning circles and an unresponsive game in V73.6a. The workaround may to be to enter your route/scenario through the build menu. Select the route and scenario you would like to run, edit, save and exit.

 

Thank you. This solves the problem for me.

So it has nothing to do with .png files larger than 1mb or resolution larger than 1080P.

After I have modified the files in paint and put them back, the game no longer crashes

 

I have this problem too!!! She was before the update! I'm running the vehicle in 4K 64bit resolution. The error goes away if I turn off dynamic lighting in the settings. I can't understand what is the reason.
The system is new i7 12700K, RTX3070 Supreme, DDR5 6000, SSD 2 TB. TSW3 runs fine for me. Tell me what could be the reason?

 

Launched on Steam Deck yesterday after the 2nd update downloaded and it seems to be running fine (from secondary Steam library on SD card, not the default), at least for the Japanese route, though I only had time to drive for 10 minutes. I'll be able to test it some more during the weekend.

 

Probably would have been worth giving details on using Name My Route or opening the folder in-game to find the route folder.

 

I hope this doesn't mean that DTG aren't planning on fixing the issue.

 

Another feature in NameMyRoute... You can use it to find broken Scenarios, Especially workshop ones. here is an example from my installation.



Hamburg to Hannover, as you can see, has two broken scenarios. This is a clean Install with the Core update. It was like this before the update.

How to fix? They are empty and broken, so you delete them. The two that say 'missing Scenario Properties.xml' those are screwed, so delete them.

Here is a broken workshop scenario, With Hamburg S1.


A Look inside the offending ScenarioProperties.xml with notepad++ reveals this error in the xml.


Its pretty obvious that the XML has become corrupted. Delete the Scenario, Go back into TS and if it re-downloads and still has the same error again, Delete again. If its one Scenario you really like, tell the person on its workshop page. If its still like that after telling them, Delete and Unsubscribe.

Repeat this for all Scenarios you find like this. I have been doing this for Years. These problems are TS crashers. So its still good to get rid of them.

 

It's what the workshop extractor usually does. It happens when multiple scenarios are extracted at once.
I suspect the extract works mostly fine or the tags would be broken. It also saves fine, same reason. Just somewhere in the process some values get broken. Depending on which ones, it is more or less of a problem.
After deleting the scenario TSC thinks it's fresh workshop subscription, so it extracts it again.
Empty folders shouldn't happen but they could be leftovers after deleting a scenario. Also, when you save a scenario in an AP file, it creates the file structure but doesn't extract anything beyond saving your game state. (Which is the standard way for TSC.)

I was hoping they'd fix it with this set of updates.

 

I just tried the DirectX 12 build, it is unplayably bad. I intentionally stressed test it, with the same test on both the normal 64-bit and DX12 builds. The test was:
Quick Drive
New Chatham Main Line with AP Track - spawning at Brixton, facing Victoria
AP Sky and Weather 2.0, raining
AP Class 375
AI enabled
Maximum settings in TS, plus some enhancements in NVidia control panel

With these settings, an intensive route and an intensive train with intensive weather, the normal 64-bit version stayed around 30fps (the FPS counter was taken in the cab - for me, TS runs around 20fps lower in the cab on some routes and trains, but this time it wasn't the case). The DirectX 12 build dipped below the 15fps minimum to be recorded.

 

So you played the first cut of the DX12 implementation which is probably pretty much all defaults. I'm assuming you had an up to date driver. You then stress tested it and it didn't meet expectations. What were you expecting to happen; a pretty much perfect result?

 

No, I was expecting it to be useable.

I'm not sure what point you're trying to make. DTG released a new version of the game to experiment with. I experimented with it, and found it to be worse than what was already there. A cigar is a cigar.

 

I played the dx12 version, i choose a great western mainline scenario from Jt a very old route:
i noticed a great improved Vsync experience when you move your head around
i noticed no stuttering at all (even if it's an old route so maybe not the best to test)
One problem: in the main menu the mouse arrow randomly disapeear and return afer 3/4 sec. i have a Logitech mouse.

 

A sidenote: probably you shoukd have a compatible dx12 vga card to gain benefit.

 

DTG JD TrainSim-Steve

Is it correct that the supplied runtimes in the "Install" folder have not been updated? The vcredist_x86.exe is still the 2010 version.

I have the "2015-2022" version both x86 and x64 installed on my system - but shouldn't they be supplied with TSC?

 

In advance of an official patch via Steam, I've uploaded to my Google drive an "rwp" file, called Smokebox_TSC_Updated_Loco_Thumbnails_29Apr23.rwp, that contains all the necessary updated thumbnails for Smokebox locos:

https://drive.google.com/file/d/10B_t0LkjjmTQFHAajVyw_KD6IWzzArjD/view?usp=sharing

The rwp is a zipfile. The root folder in it is "Assets". Simply unzip that folder it into your RailWorks root folder (usually located at C:\Program Files (x86)\Steam\steamapps\common\RailWorks).

 

My point was that stress testing a v0.1 version of software and then just labelling it "unplayable" isn't really helpful. It's similar to those who say TSC is "broken" when they're having issues with a patch.
I played a scenario with DX12 and I couldn't really see any issues. Admittedly I'm sure it helped that the scenario was set in the dark but the cab, platforms and rails all seemed ok and there was no stuttering that I noticed. Now I need to find progressively more demanding scenarios until it starts having issues. I can then give the developers more details than just "unplayable".

 

Can I ask how to activate the DX12?
I've tried to find in the options but I haven't saw any changes in the pages

 

You can find the 'RailWorksDX12_64.exe' in your Railworks folder - start it from there or create a desktop shortcut.

 

I still don't see the issue. Demanding situations like the one I tested are very common in TS and if my experience falls flat at the first hurdle then it's a failure. The framerate I was getting was objectively unplayable, there is no other way around it. Some will have better experiences than others, but there's no point complaining that my results were bad. The test was identical on the existing version and it performed significantly better. I did give very clear results for the developers, and that is the framerate was worse than half what I had before on the normal 64-bit version. If that doesn't scream 'not optimised well enough' I don't know what will.

It's a launch option when starting with TS. If you've set it to default to the 64 bit version, you'll need to use the drop down box next to 'play' in Steam to override the setting.

 

Hello everyone .

Thank you so much for your quick fix!!
I am a huge fan of your steam locos and would have been unhappy not to be able to play with them anymore.

DTG is lucky to have a close-knit and competent community, to repair for them while they enjoy the big weekend.....

Thank you to all the third-party editors for the past and especially future work.

 

On a general note. I have been quite happy with the upgrade. So far the OOM issue is much better. As per the DirectX12 I will not be moving to it until the ThirdRail driver is produced. Been quite a productive day logging rides to my web site. Platform seems very stable.

Respectfully

 

DTG
Some Questions/Suggestions regarding future core changes/updates

I don't know if something like this happened or not, but wouldn't it be better to do the following for the subsequent serious changes in the TS core?
- Communicate with the well-known third-party manufacturers: "Hey. We changed this and that in the core. Please check out whether your products still work or not and give us feedback." Of course, in this case, you should also make the update available to them (and firstly before rolling out to everyone).
- if the manufacturers don't want to check it themselves: ask them to make the products available for you to install (or at least those who are available on Steam). Then you could adapt your test environment or one of the test systems so that as many of the payware products as possible are installed in the end. After all, there are many customers who also have many different payware products installed. This way you get a more comprehensive view and in the current case the problem with the thumbnails of the routes and the rolling stock should have been discovered early.
After all, this is to the advantage of EVERYONE: the manufacturers themselves (after all, they will want their products to continue to work?) and the customers? Of course, it still cannot be avoided that, for example, errors in the functionality of the Afb are discovered in some vehicles - ideally, the relevant third-party manufacturer would have to check this themselves. But at least more serious ones, for example if the game freezes while scrolling through the menu pages