Another Update, More Broken Stuff

DTG Matt Unfortunately I've just had a crash on ECML 1E04 (game crash, not train crash) 2 miles after Doncaster (DON said 34 miles to NNG then when crashed said 32 miles left). This is the first time I've had a crash after Doncaster, but have had many when approaching. May also be new after the update.

PS4

 

Looks like I can no longer use keyboard to confirm AFB speed on Vectron on PC.

 

Bad on night drives. Vectron pak hasn't been touched - so again a core change is responsible.

I'm glad all this is handled differently now on Train Simulator Classic, with core changes being tested by a small team first and then rolled out as Public Beta for everyone to decide for themselves to use it, and then after the feedback period it gets rolled into the stable public release.

Nothing is more dangerous for a DLC based game than making core changes, and unfortunately TSW serves as a textbook example for software engineering on how not to do it.

 

Only thing I’ve encountered so far is that joypad (which I don’t use on PC) vibration had been switched back on. Don’t want it, don’t need it!

 

How much you encounter depends on how much you are testing. I played four routes and discovered new bugs on all of them - some content- and many core-related things.

In that respect smaller updates would be more favourable - when pushing out such huge updates you must be sure it's well tested before rolling out.

 

I could not replicate that issue on PS5 (with all DLC installed) earlier. Rosenheim to Endorf and back was fine for me.

 

Quick question, are there any updates about the low resolution and blurry texture for console users?

 

In case you're unaware, low res tex is occurring on PS5 too mainly with in-cab dials etc when it occurs (though not as frequently as the hobbled XBSS)

 

Matt,

this may well stand for a technical explanation, sure. In the example below, the double heading Vectron would demand double texture streaming. And the memory drain seems to build up as you drive around (Pic 1 vs. Pic 2, both from the same run). All logic. So far so good.

But it still begs the questions why these evident texture blurs didn't happen until rather recently and, of course, the One-Million-Dollar question: Which "Up"date and what part of it broke the show?
I hate to say that your "patches" come almost always full of surprises, and the surprises are hardly pleasant ones. And that's why the OP did the right thing to open (just another) thread about these issues.

https://forums.dovetailgames.com/search/59233324/?q=texture+resolution&o=relevance

The screenshots below might help to pinpoint the root cause. That's why I've attached them.

Pipe.

Ran on PS5, from TT, all German DLC - except Dispolok - installed.

 

The malformed Vectron on your screen is not a texture downscale, that's a completely different LOD (level of detail), a simpler, autogenerated model meant to be only shown when viewed from very far away.

The only TSW4 route I play is Vorarlberg, but there is a lot of LOD problems there with railway infrastructure and assets. Houses are popping into the game few meters from you, tunel entrances in Feldkirch are extremely malformed as well. And that is playing on ultra on PC. My feeling is that the team responsible for optimization just gave up and let some AI do it automatically, and the result is atrocious. I never saw something like that on TSW3 and older routes.

 

DTG Matt Not sure if it’s been mentioned but since the core update the game keeps crashing on the approach to Doncaster on ECML. It’s happened numerous times now…Doesn't happened if I do Doncaster to Peterborough though…

 

I'm no specialist for this. Bottom line here is: It sucks big time, and it's not how it's supposed to look! Wrong LOD programation, memory leakage, tile dump missing .......... I don't know. What's caught my attention is the fact that the textures are OK when you start the service, no matter if your're close or distant. Then, while driving the service, it becomes worse step by step and it doesn't recover in the end. I've tried with several camera angles and on foot, distancing and then closing in again, motion blur on and off .................. all the same.

I suspect the so called "team responsible for optimization" doesn't exist. At least not anymore. IMHO one of the biggest DTG F........ups was the dismissal of Alan's preservation crew. They did a great job on several routes, so much that I still come back with pleasure to RSN (or RRO, or MSB, or HRR). And judging by the forum, I'm not the only one.

But there, it is what it is, and I hope DTG can find the root causes and fix this for good (Yeah, hope's last thing to die).

 

This is something I’ve been in communication with DTG Alex about, and he passed it onto the team so I reckon DTG Matt is aware too. I would just highlight that this a bug I faced prior to the core update. Haven’t done PBO to DON since though, so can’t confirm if it does it still or not. Likely does though, as unfortunately it now also occurs (since the core update) on departure from Doncaster too at the same distance from Doncaster (between 1-2 miles) on PS4. Unfortunately makes any service originating or terminating (for our purposes, not the full route) at DON unplayable. Which console are you on?

 

If it's deteriorating over time and never recovering back, it suggest memory leaks overall, and probably big ones. The game fails to release the memory after unloading objects, so the remaining memory for new things will be smaller and smaller until the engine needs to start taking some desperate measures to continue working. OMSI was famous for suffering from this a lot in early versions, but that was a project wholly created by like two people.

 

Im on PS5 did a run from Donny to Peterbro and it was fine…did a return service and the game crashed on the approach to Donny again!

Edit: gonna try the same service on PC for comparison…

 

This is so frustrating.... Everytime we get a patch but instead of fixes it will ruined alot.... Please consider an open bèta for pc users! The most of the bugs are related to no knowledge system... The beta testers are have no clue and to low educated for the trains and the behaviour i guess. When you test first an open bèta we can help you to fix the most bugs. We have already so many things its already a dramatic turn again. For normal users they expect a good patch not a half broken one and be honest this is not at the quality standards as needed

 

After reading this thread I drove a 375 around Gillingham and couldn't reproduce this issue on PC. I do however remember it on GWE way back in TSW2 days, specifically on the 166.

 

The double traction Vectron service is -----> DGS 46660 Curtici - München Nord Rbf - Part 1.
The 111 in Dresden came from Riesa working an RE50 service. Pics are taken in Dresden Neustadt and Dresden Hbf. It usually starts around Coswig when you close in to Dresden.

I can't pinpoint on "which service" it happens "consistently". But the again, the forum is full of reports about this issue. Across many routes and trains. Which makes me believe you won't have trouble to reproduce it.

Here's from Maintalbahn:
Texture Resolution Problem

A list where it has been detected:
Texture Resolution Problem

And again the search link:
https://forums.dovetailgames.com/search/59233324/?q=texture+resolution&o=relevance

EDIT to add: Fingers crossed and Good Luck!

 

Another report of low res textures appearing during a run…

I’m on PS5 and whilst driving the latest Railion BR 185.2 on a double header freight run out of Salzburg (DGS(47840) Stadlau to Wolfurt), all was fine until at some point around an hour or so into the run, when returning to the cab view after looking at the map, every controller and switch label texture in the cab including the buttons around all the screens was reduced to a fuzzy mess. A quick look at the exterior showed all the logos and text on the outside of the loco was the same and most of the exterior textures on the Railpool 185 behind it. That’s the worst I’ve seen so far although I had been seeing some low res textures before the latest update. I have 54 routes and lots of loco DLC installed.

 

It looks like a memory leak on the PS5! What i have noticed so far is that the game on pc needs te load this textures as well and it takes way longer than earlier. I will add video in this message asap so that you see what i mean....

 

I guess it is! And have made a quick video where you can see on pc its there but loaded later but that was not how it is now... Earlier this was no like this behavior!

And i have a highlevel gaming pc
AMD Ryzen 7300X
Nvida RTX4070TI
All my drives are SSD/Nvme

DTG Matt

 

PS5 user here also seeing the low resolution issues. I have all UK addons that have been released up to this point, makes it easier for testing I suppose. One place I know this always happens without fail is if I start up in Doncaster and drive a train out from there (timetable or free roam), and while I can understand it around Doncaster with how packed the freight yards are, the models remain in this state all the way to Peterborough. It happens occasionally on other routes too but ECML is the main example I can think of where it seems to be near permanent once it starts. Attaching some pics below.

 

Yeah shadow pop in is worse. Look at Dresden in this video.

https://www.xbox.com/play/media/sqa5vEys4c

And are fields supposed to be like this??? Actually the pop in is off the scale in Dresden. The render distance is tiny.

 

I hope it was OK for me to post 2 images I took here to show more broken things this is on the Blackpool Branches line on Xbox Series S

 

Needs fixing asap