Core update issues if any

[AmericanSteam]

Firstly, follow the DTG guide I have provided a link to. https://www.dropbox.com/s/6f7laowrevfdi ... t.pdf?dl=0 to see if this corrects your issue before you need to do more editing.
I have successfully corrected the spinning wheels and crashes on my copy of Railworks. I used several methods to resize the problematic thumbnail resize. One method I used was to open the build menu and navigate to the route and open the RouteIformation folder. find the image.png and resize it to 512x256 pixels using paint and replace the file and save. The second option I did was to navigate to the Content/Routes folder using file explorer and go through each route and find the RouteInformation folder and resize those images. You can do most of those within the folder, some you must do in paint.
I had to provide a link because it was to large to upload.
There is no need to remove content or delete thumbnails.

[AmericanSteam]

There are scripting issues and some advance locos are still not driveable.I don't know how this will be handled either DTG will offer a fix or they will work with developers to provide their own fixes. Some or all of these broken scripts locos were sold through Steam so they should have been available to in house computers for testing.

[mikeadams2k]

Sorry AmericanSteam. I have trouble finding my way around my house, much less this forum. Thanks for the link to the fix. It's interesting that DTG states the correct thumbnail size should be 512x256, when in the past, the correct size was apparently 256x128.

[AmericanSteam]

Running DX12 will break the Raildriver cobra One (TS2019 joystick) interface software.

[ENR3005]

This is Deju Vu again if you used MSTS two decades ago and upgraded to the first unofficial patch which was called "MSTS Bin" back in the day around the time that Rail Simulator / Railworks was about to be released for the first time. Look through the chaos on the various MSTS forums from that time and you will see exactly what I am talking about. Some of the most recent posts on various forums mirror exactly what was going on back then, some of them just plain angry, others threatening that they are uninstalling and never coming back or worse. Then there are those that are providing constructive feedback and assisting with finding solutions to errors such as the image sizing and those folks should be commended. To be honest this is not to be unexpected when you tinker with a piece of software this old and will likely take some trial and error with feed back from all users much like MSTS Bin required before we got to see any light at the end of the tunnel and resulted in a 100% functional piece of software. DTG / Focus seem committed to working the bugs out along with many third party developers such as Searchlight's update today which may take some time and I suspect will be worth the temporary pain we are experiencing. I for one, will be very appreciative if it results in a similar end product much like MSTS Bin became years ago and you will find very few complaints about after the initial trial and error done years ago. In the interim having learned from my MSTS days with the first Bin upgrade, I have chosen to run from a older backup for now on my desktop and have been tinkering with the updates on my laptop which look promising. If you aren't happy with things right now, run from a backup for now and give it some time and forget about the updates till they are functional, it will happen with time and constructive feedback.

[buzz456]

The hysteria on some of the forums is just plain amusing. You'd think we lost the nuclear codes or something.

[buzz456]

Where you you go to try the DX12? I don't see that.

[kris120]

Regarding Smokebox Lima Consolidation's LocoInformation pics:

The original image.png is a "PNG -Zip, interlaced" and a size of 256x128 px. (information from irfanview). This lets TSC freeze.
I have saved it again with gimp, resulting in a "PNG - Zip" and the same size 256x128 px. This works.

So it's interlacing, that blocks TS, not the size of the image.

[buzz456]

Where you you go to try the DX12? I don't see that.

Never mind. I found it.

[mrennie]

As per the post I made last night on my Facebook page:

Apparently some of my locomotive thumbnail pictures, which have worked fine for up to 10 years, are now deemed "non-standard" by the updated TSC and cause it to crash the QD loco selection menu (what was that about "defensive" programming?).

Check out my replies to this thread: https://forums.dovetailgames.com/threads/train-simulator-classic-%E2%80%93-core-update-route-refresh.69230/page-3#post-646312

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 loco thumbnails:

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).

The "standard" isn't 512x256px. It can be 256x128px too, or even better, 256x144px to avoid stretching. What now causes the problem is interlacing in the png image. which used to work fine (until this stupid update).

[pkz19]

So I can't necessarily blame this on the update for sure since I haven't tried to put the HSC Lorry into anything in a while, but that is definitely not the HSC Lorry. Everything else in that content section is working properly as you can see.

HSC Lorry - not.jpg

[kris120]

@mrennie (and all members, too): I think DTG does not know that changing a standard by reducing tolerance will never be positive for all people not belonging to the primary developer.
This will not be accepted by third-party developers and by people who don't just use assets from Steam in the long run.

What is very desirable, on the other hand, is the specification of standards that lead to new capabilities.

Example:
An entry signal secures the entry into the yard and the main track until after the last switch, where the yard rejoins the main track. A standard situation on American stations (Essex, Cut Banks, Chester on the HiLine). The TS cannot reproduce this. For this to work, the road (switches) would have to be defined first, and then the signal scripts would have to be set according to the switches. But this is not the case so far.

[Chacal]

So there was one small change in the update that had an unforeseen impact on a few 3rd-party assets?

[mrennie]

So there was one small change in the update that had an unforeseen impact on a few 3rd-party assets?

No Chacal, there are more, with even worse impacts.

[ElphabaWS]

So there was one small change in the update that had an unforeseen impact on a few 3rd-party assets?

An unfortunate comment, given the impacts that have occurred to multiple third-party products.