Core update issues if any

[Railfan722]

There's also been a change to how TS handles the SetControlValue function. Some developers have gotten away with the syntax of

Code: Select all

Call("SetControlValue", "controlname", 1)

skipping the 'index' check that TS might otherwise expect. With the update, the game now expects

Code: Select all

Call("SetControlValue", "controlname", 0, 1)

Prior to the update, both ways of writing the code were valid, although the first was technically incorrect; that being said, it worked until the other day so nobody had any real reason to change it. With the update, only the second way is recognized as correct, and anything that previously depended on the first method will now not function as intended. It remains to be seen if DTG will attempt to fix this by trying to bodge together some sort of handling for the first method, or if they'll keep it as-is.

[Chacal]

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.

So there's more, then. I'm trying to get the gist of it from the limited feedback we've had here.

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

So there's more, then. I'm trying to get the gist of it from the limited feedback we've had here.

Well for starters, all of my locos have been rendered useless because the core code that handles the injector control values is completely broken, except when the controls are linked directly to moveable knobs and levers in the cab with no intervening scripting to translate other variables into the final control values (which is what my Pro steam locos do).

[buzz456]

So let's work with DTG to get the stuff restored or modified to work with existing DLC's.

[pkz19]

I can't run the game with DX 12, this is the error I get, no idea what it means:

DX12Error.jpg

[buzz456]

Just guessing that DX12 is not installed on your computer. Microsoft has a thing to check and see if it's there. Google it.

[Minneapolitan]

Since this core update, the program freezes/crashes every time I couple and uncouple something.

I haven't tried it on every route, but so far it's only happening on my Vintage New Haven Springfield route, and so far just on my self-made free-roam scenarios. I created a new free-roam scenario just to troubleshoot, and it still freezes/crashes upon coupling and uncoupling when using ONLY VNH rolling stock. So add-on rolling stock and user-made reskins don't appear to be the issue.

But I tried the simple Wallingford Local career-mode switching scenario, and coupling and uncoupling works fine. So I don't know what's going on other than that I'd like to put my fist through my screen.

Right before the update, I added a crossover on the west end of Hartford, but never really got a chance to test it out. But usually when tinkering with the actual route, anything done wrong with track will still load...just with some error messages with coordinates and the option to exit or return to the editor (You've likely all seen it). But this shouldn't be it. After all, I can still MOVE a train just fine...and the Wallingford Local scenario works just fine and that's the same route. But I'm not a tech guy in the slightest so who knows what else the update changed?

And to be clear, when coupling and uncoupling crashes the program, I'm not getting the usual "TempDump" memory thingamajig. This time everything freezes, and Ctrl+Alt-Del to Task Manager does nothing. Rebooting my entire computer is apparently the only solution.

Any ideas?

[buzz456]

I can report that using the VNHRR rolling stock on another free roam scenario I get the same thing. Using some other rolling stock no issue. No clue at this point and am investigating further.

[pkz19]

Just guessing that DX12 is not installed on your computer. Microsoft has a thing to check and see if it's there. Google it.

Thanks Buzz, been around long enough I do have and know how to run DXDiag, and I had already checked, I have DirectX 12, but that said I don't know enough about DX to troubleshoot error messages

[buzz456]

Just guessing that DX12 is not installed on your computer. Microsoft has a thing to check and see if it's there. Google it.

Thanks Buzz, been around long enough I do have and know how to run DXDiag, and I had already checked, I have DirectX 12, but that said I don't know enough about DX to troubleshoot error messages

Have you opened a report? They answered me on both of the reports I sent in a few hours. I don't know how to troubleshoot this either. The only time I had trouble with 9 is I uninstalled and re-installed and it fixed the problem.

[GreatNortherner]

I can report that using the VNHRR rolling stock on another free roam scenario I get the same thing. Using some other rolling stock no issue. No clue at this point and am investigating further.

Hi Buzz, Hi Minneapolitan,

Good thing that I happened across this thread this morning. I have just tested this and can confirm that something got broken with the couplers on the Springfield Line. I've set up my own FR with the GP9 and S-2 and a bunch of cars around them. Most of them I could couple and un-couple okay, but eventually it locked up on me, too. In this case, it was when I attempted to split a heavyweight and an American Flyer coach.

No idea though WHAT is actually wrong here. I'll go over the coupler settings on the route's equipment of course to see if anything stands out. I fear this is going to be a search for the needle in a haystack.


Cheers,
Michael

Edit/PS: In order to prevent a lock-up/freeze of the game completely locking up your WIndows, too, I've found that running in borderless windowed mode helps. At least it's always allowed me to Alt-Tab back to the Desktop or fire up the TaskMan with Ctrl-Alt-Del if the game freezes solid.

[GreatNortherner]

Of course... and now that I re-run the test scenario to capture a log and dumplog, it doesn't crash. So... random crashing on un/coupling, then? What the heck is going on?

Buzz, Minneapolitan, could you possibly send me the scenarios in which cause the crashes in your game?

[AmericanSteam]

Just guessing that DX12 is not installed on your computer. Microsoft has a thing to check and see if it's there. Google it.

You may need to update your Windows C++
Follow this guide: https://dovetailgames.freshdesk.com/sup ... assic-use-

[ssbobz]

Is it possible to roll back to pre-update until this is sorted out? I'm guessing not.

[buzz456]

Is it possible to roll back to pre-update until this is sorted out? I'm guessing not.

That's why I was recommending backing up your whole Steam folder however if you didn't the answer is no. Are you having some problems we might be able to help you out with?