Train Simulator Classic – Core Update & Route Refresh

I did. They said they were working with DTG on getting this fixed and it worked just fine before the core update so it is the core update which broke things.

 

Great you could find the floating point issue! And nice to have the proper 4 camera back.

And how elegant putting all of this in a super efficient 480 bytes delta patch!

 

Hello,

Although you can set the AFB up to 160 km/h, you cannot reduce the speed again

 

What loco are you talking about?

 

Going from reports on Rail-Sim.de it would be most of the vR locos.

 

DB BR 101, BR185,BR189,DB ET403 from www virtual-railroads.de

before the core update in April, everything worked perfectly.

 

Whatsup with the verified shield?

 

I´ve been waiting for weeks for my favourite german locos to work again... another disappointment on the VR locos. I guess they will never get fixed now.

 

But as soon as you set the AFB selector lever to 160 km/h, the speed cannot be reduced again.

 

and you can´t set it above 160 at all when in LZB and driving high speed lines.

 

Exactly right, as soon as you have the AFB selector lever at 160 km/h you can't set it any higher or at low speeds.

 

thank you for fix. is the team also working on phase 2 of the train simulator update program?

 

I wonder what Vr has to do with it, before the 2023/04/28 update everything worked fine. Until today's update, the AFB could be set to a maximum of 5 km/h. and since today's update 06.06.2023 version 74.4a you can set the AFB to a maximum of 160 km/h and as soon as you are at 160 km/h the AFB preselection can be set neither higher nor lower.

 

Many thanks for the update,it is appreciated.

 

F4 now working for me - haven't noticed any loco issues but haven't tried any BMG ones (apparently they have a problem).

 

The Developer behind AHS did a runner after releasing their products and not providing any support

 

The difficulties for DTG with this are:
a - to upgrade the application they HAVE to upgrade/cleanup the underlying technologies
b - much 3rd-party stuff hides its LUA code inside compiled modules so DTG cannot see what techniques/functions/shortcuts they have used
c - some 3rd party stuff (esp. locos as they are the most complex) will have relied on elements of the old LUA that are now 'illegal' or never-meant-to-work-that-way-but-did (and now don't)
d - because of b) the team at DTG don't know what someone else might have done which might be broken under the new LUA - and no one could reasonably exepct them to test every 3rd party thing themselves
e - some 3rd party devs ceased to work/support TS many years ago (I'm thinking IHH here but perhaps 'AHS' falls into the same category) and in some cases this may mean that a few locos just won't work unless someone steps up to provide a new 'clean' script for them
f - DTG could just make a mistake - it happens.

Having said this it would have made sense to pre-release this update to at least the main loco devs so they could troubleshoot before general release.

 

They hide it for good reason - protection of their hard scripting work. Many of these locos are more advanced even that TS Pro line from DTG. For example author Kal000px from czech/slovak community has scripted ETCS - imagine what could happen with that code, if it would be accesible as a plain source LUA code... and there are others as well. Btw, DTG do the same, for example with german BR155.

Also it is not completely true with that old LUA elements. AFAIK LUA is backwards compatible, so it shouldn´t be a problem. There is no such thing like "illegal" element in it - what do you think it could be I wonder?

My guess is that there is a problem with compiler, not the lua itself, because source LUA files work like a charm.

 

The problem is the reason the rolling stock are different size from the real, this make the stopping position and shunting different from the real. And the change of speed also not realistic, some Asian train game very value the acceleration and deceleration rate,
let the players experience the job of station stopping. I think TSC can also do this.

 

LUA decompiling isn't the hardest thing in the world...

 

Yes it would have made sense. Especialle because of a - f DTG should have done a extensively test with urgent/mandatory help by 3rd party developers (at least those who´s existing) from very first beginning if planning to make such profound changes in the core. And some of the developers are not the small ones that only have one product. Some have their products on steam too as RSSLO, Just Trains, .... For me, the alarm bells rang as soon as they announced that they want to cleaning the core. [It's not called for nothing: Never change a running system!]
Especially point d: A lot of users have TS since years. And they might have 3rd party stuff too. So it should be in interest to DTG that all possible is enough testet, otherwise the community will "Thank" it in an other way. And I hope they become the curve.

First patch: we could say it was a desaster. Following patches seems to solve some things but create other problems (and If I´m not wrong: the problem with the thumbnails only must be solved by that workaround by everyone itself!). It feels like it happends to lots of smartphone-apps, more and more updates and with every update other stuff becomes worse.
Already with first patch in my opinion DTG should have reset the game to its state before the patch and work further in calm in the background to fix all the problems and let them test it from 3rd party firstly. (Perhaps some additional Betatesters with a possibility to install a Beta-TSC parallel to the normal, so they could copy-Paste the official DLCs into it and test it enough).

Now I have still the feeling - we ALL only serve as Betatesters - without any choice, like we all would have buyed an Early Access Game.
I can only hope that TS will someday runs without problems as it has before the start of the "patches".

 

Do you know of a good decompiler? The only one I found was clunky and generated garbage - after which I gave up and just worked out (with help) how to achieve the stuff I needed to do.
As Kiski says - LUA sourcecode works just fine - so none of my locos are affected ;-)

 

Unfortunately not for TSC - I was making a comment about how LUA compilation shouldn't be relied upon for security.

 

Then how would you protect your scripting work?? Everything else can be quite easily extracted from the game, but compiled script not.

 

I wouldn't. If someone copies it then they're liable for copyright infringement.

 

Core Update?

Lua: Lua 5.0.2 Copyright (C) 1994-2004 Tecgraf, PUC-Rio
Authors: R. Ierusalimschy, L. H. de Figueiredo & W. Celes
URL: www.lua.org

Why are still using Lua 5.0 revision 2? A totally unoptimized version from 2004, that was nearly 20 years ago. The current Lua is Lua 5.4 revision 6 released on 14 May 2023, that must be why the scripts of some locomotives are beating the fraps down and even possibly functions with redundancy in local variables.

Version history
URL: www.lua.org/versions.html

 

Interesting - where are you finding this info? All I've seen so far is the luac.bat/exe which I assume is the compiler (last modified 2009).

 

Do a real-time debug on the RailWorks.exe process and you will see how the Lua scripts are loaded and thus you will see the Lua interpreter in version 5.0 revision 2. If you are not good at debugging in realtime, you can also load some of the GameManagerVC (.dll) with some debug interpreter and you will see the Lua interpreter in version 5.0 revision 2 encapsulated inside them. Inside the RailWorks folder there is also a luac.exe compiler with the same version.

This game is running with a lua script interpreter from 2004, where it is bad in optimization, it has been almost 20 years, where everything has been improved in the next versions. This must be a joke.

Code:

Microsoft Windows [versão 10.0.19045.3031]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Admin>C:\steamapps\common\RailWorks\luac.exe -v
Lua 5.0.2  Copyright (C) 1994-2004 Tecgraf, PUC-Rio

C:\Users\Admin>

 

With the recent update, browsing the Quick Drive menu seems to work better, not getting any freezes. However, getting quite a lot of Out of Memory errors, even while just browsing the menus.

 

OOM from just browsing the menus? Have you switched on LogMate to capture the faults?

 

No, I just kinda gave up on this old piece of unstable software and went to play something more reliable.

 

TSW3?

Jokes and banters aside, once your anger is subsided, I would recommend a clean installation with just the official content you actually want to play, try it a bit, set up a robocopy clone, and then gradually add 3rd party stuff to your installation.

I think I have a lot of content installed, but I have no problems whatsoever, except the dislike of how slow the UI is.
My install is a bit more scenario heavy, whereas there are people about 3 times my install size, lots of stock, routes and other assets I presume.

 

This was a recent fresh install, with only a selection of DLC installed. I only have content from Steam (either official DLC or Workshop) installed. Used to work fine (or at least, good enough).

Not looking forward to keep reinstalling TSC over and over again with the huge amount of DLC I own...

 

Well then, that should totally work. Can't tell why it doesn't.
I'm still on my install from 2015, a couple integrity checks, workshop, and the Win10 move. Same hardware, too (newer SSD).
I used to have a PC with an unstable memory slot many moons ago, causing random bugs in games. Never proven, but they work fine ever since. On the contrary, upgrading from GTX 560 to 970 made GT Legends crash a lot during night time. Less over the years, but still.
Wishing the best!

 

I have now switched off real time communication with Steam. I have seen other issues with other games on Steam. Since the last update (decimal point) and disconnecting real time Steam I have had no issues whatsoever. My Steam achievement now only update when I log off TSC.

 

I would recommend deinstalling routes that you have finished all the scenarios as i do i had over 240 gb of dlc's now its only about 170 gb

 

Donner Pass
Donner Pass: Southern Pacific Route
Together as One (Good Weather) CS
Career
EMD SD40T-2

Then using LogMate:
2023/06/10 06:58:21.144 - [Script Manager] - Trace D:\build\CoreRelease\Code\DLLs\ScriptManager\cScriptComponent.cpp : 365 = Push Function failed due to missing script instance in US Level Crossing
2023/06/10 06:58:21.144 - [Script Manager] - Trace D:\build\CoreRelease\Code\DLLs\ScriptManager\cScriptComponent.cpp : 464 = Failed to push function OnConsistApproach onto stack: US Level Crossing
Repeated error 11501 times until it created an OOM Error

Root cause: I did NOT have US Loco & Asset pack loaded. Looks like a certain points in the scenarios if the assets being looked for were not there there are times when the error stack overflowed and created an OOM error. LogMate was very useful in determining what was missing. It would be nice if assets were verified before the scenario is allowed to start?

 

My Utilities.exe is still not working. Is it me or still a issue?

 

Just upgraded from Win7 to Win10. All working fine, despite reports of Utilities.exe and RSbintool not working, they all do on my system. No issues.

 

Who still uses utilities, please?

 

I do. RWP files is a very handy format for delivering what i do in TSC.

 

If you're making and releasing content especially via the WS then still a fair few I should imagine, but for installing .rwp files it's easier to just use 7zip or other zip extractor/archiver, though I do like the (idea of) uninstall option that utilities offers even if I've never actually used it too uninstall anything myself.

 

I don't care about scenarios. I just want to enjoy Quick Drive. I shouldn't need to uninstall content I paid for because this software is unstable and unreliable.

 

Do you have workshop routes perchance?
Are you getting the crash browsing the routes or the trains? Is it consistent (on a page), or random?
I agree that it shouldn't be a problem, just trying to be solution oriented.

 

I would like to have a clarification on the Save & Reload issues related to Chinese localisation: which routes are affected (I assume they are Union Workshop ones) and what kind of update is foreseen: will there be corrections on individual routes or on the main program?
In some cases I bought the route on the Just Trains site instead of on steam.