TS 2024 now live

[buzz456]

I thought since we now have the update rockin on it's time to start posting stuff about it here.

[AmericanSteam]

So far the only thing I found unusual, was when in the editor the GPU loads to 90-100%, the temperature runs hotter and the GPU fans come on high. I don't remember this when using the BETA version. Other than that it seems to be working as usual. There seems to be a lot of chatter about missing headlight flairs from some players. Either the headlights are not on and the flairs show or there are no distant flairs but only show up when close.

[pkz19]

So I tried running my IHSX steel mill route, and when switching to the 2-D map, it would start to flicker between a black screen and the 2-D view.

It stops flickering like that when back in the regular view, but then the track names weren't showing up in the HUD.

I tried loading a different map, specifically the B&O Mountain route, and had the same issue. Also, the SD35 gauge faces are missing, but that could be unrelated to the 2-D map issue, I need to check other locos.

Screenshot_B&O Mountain Subdivision_39.65649--78.77161_12-02-19.jpg

[AmericanSteam]

Not having the missing gauge face or the 2D map issue.

[august1929]

Has anyone experienced any of these issues raised across the Pond. Originally thought to relate to the F4 HUD but that was just a symptom of the freezing, not the cause. No solution yet from DTG (DLC routes possibly not affected) but it would appear that reinstating a previous version of the "plugins" folder solves the problem, specifically "GameManagerDX12_VC64.dll". I have not found any detrimental affect on DLC routes so far using the old "plugin".

Full discussion here which is worth reading through as there appear to be a number of apparently unconnected areas of the sim and other routes affected;

https://railworks.freeforums.net/thread ... se-tsc2024

My initial post as follows;

" F4 HUD freezing following the release of TSC2024

Bit of a poser this one.

As far as I can see from testing different routes the freezing only occurs on SSS Stainmore route.

I have the route installed in three locations. On my old relatively low power computer, on a backup copy of TSC on my new fairly high power computer and also installed in the standard Steam folder under TSC2024.

All 3 installations have identical options ticked and unticked in the TSC Options. Obviously the environment (other background programs etc.) is different on the older computer, but is identical for the 2 installations on the new computer.

Prior to TSC2024 I could run very satisfactorily all of a large number of scenarios on Stainmore. The old computer was slow to load scenarios, typically around 3 or 4 minutes, but once loaded ran without any problem. On the new computer, within the Steam installation, the loading time was quick, typically less than a minute, and again I could then run the scenarios without any problem. Post TSC2024 I can no longer load any of the scenarios through Steam, each of them freezing just as the initial in route/engine cab scene appears, with the F4 Hud failing, looking like the screenshot below.

I can run TSC from my backup in the new computer, including all scenarios I have tested on Stainmore. Loading time is slightly slower than within the Steam installation, but they do load and run satisfactorily.

I have completely reinstalled Stainmore in the Steam folder, but to no avail. I have tried reducing the options to far lower than would have been acceptable before but without any luck on the Steam installation - it still freezes.

I can actually go straight into world and scenario builder on Stainmore, any of the scenarios I have failed to load, and move about but as soon as I go back to play, the sim freezes.

Does anyone have any ideas what may be happening?

Frozen F4Hud - TSC2024



From the original installations

"

Rod

[buzz456]

Nary a sign of this here and I must have run at least ten different routes since '24 came out. Maybe it's only a problem in the old world.

[pkz19]

Well disregard my comment, I tried running another game and ran into a similar issue with switching between screens in-game. Turns out it was a graphics/resolution setting issue on my end, and now everything seems to be running smoothly.

I will say about this new TS iteration, I do like hearing the old menu music again.

[august1929]

Nary a sign of this here and I must have run at least ten different routes since '24 came out. Maybe it's only a problem in the old world.

Could be down to the way in the UK certain freeware assets were aligned to original KUJU assets, using references to the originals. There seems to be a possible link to textures and also signal scripts where dozens and dozens of bespoke semaphore signals have been produced over the years, all specific to regional and Victorian railway company originals. If anything does turn up you side of the Pond it could be worth a look back at the link above as investigation is ongoing.

In the meantime, the last version of "plugins" pre TSC2024 seem to solve the problem.

Rod

[jalsina]

I must be the only one that has no problems with the TSC 2024?

[buzz456]

I must be the only one that has no problems with the TSC 2024?

I'm incident free since I got the RWA Lakeside to load.
https://railworksamerica.com/index.php/ ... ide-addons

[august1929]

I must be the only one that has no problems with the TSC 2024?

I'm incident free since I got the RWA Lakeside to load.
https://railworksamerica.com/index.php/ ... ide-addons

OK, Wayne was straight on to that one - any idea what was wrong as that seems kind of similar to something this side of the Pond .

[wacampbell]

OK, Wayne was straight on to that one - any idea what was wrong as that seems kind of similar to something this side of the Pond .

In our case a signal script object was throwing an error. Prior versions of Railworks have always just ignored the error and carried on. But in TS2024 the error crashes the sim.

The error was visible in logmate as:

Code: Select all

[Script Manager 8:43:28 AM] Trace D:\RGBuild\CoreRelease\Code\DLLs\ScriptManager\cScriptState.cpp : 245 = error in
"...\Assets\RWA\Lakeside\RailNetwork\Signals\Scripts\Message Blocker.out" running function : C stack overflow


We had a more recent version of this script file available which we were able to roll out quickly to the RWA community.

Not sure if that is what you are experiencing, but hope it helps.

Wayne

[jalsina]

I must be the only one that has no problems with the TSC 2024?

I'm incident free since I got the RWA Lakeside to load.
https://railworksamerica.com/index.php/ ... ide-addons

I don´t know if this was fixed automatically, because I did not install the posted patch.
But in the last two days I have loaded Lakeside several times and played for at least half an hour. No issues so far.
I also have been playing with the Lakeside switch stands in FRCE, with not so much success so far.

[buzz456]

I must be the only one that has no problems with the TSC 2024?

I'm incident free since I got the RWA Lakeside to load.
https://railworksamerica.com/index.php/ ... ide-addons

I don´t know if this was fixed automatically, because I did not install the posted patch.
But in the last two days I have loaded Lakeside several times and played for at least half an hour. No issues so far.
I also have been playing with the Lakeside switch stands in FRCE, with not so much success so far.

If you are running in 32 bit you don't have the problem.

[jalsina]

If you are running in 32 bit you don't have the problem.

I´m running Railworks64.exe
Lakeside loads and I can run with no issues.
May I have done something else that fixed the issue?