Bremen Oldenburg - Unplayable Since Tsw4

Seems since the TSW4 update, i cant finish serives heading to Bremen. The entire traffic is getting stuck on red lights. (In Bremen)

What the heck DTG? This was running very well and smooth in TSW3, so since the change i rather was focusing on BRO because i like the timetable, but cant even finish a single service.

So i wanted to discus this topic:

- Are there similar issues with other "older" routes from TSW3 or even TSW2?
- What is with peak forest, there was discussed what services are "added"?, instead the people on that thread wrote there were actually services removed...

Whats going on?

 

For me concerning: I usually never had problems with red lights and traffic stuck etc.
So far im enjoying TSW4, but not with leaving behind the older content in a mess. What about Riesa Dresden? Any indication the timetable got cutted in a way, or is it the same as in TSW2 /3 ?

 

Can you name a service to reproduce this? Thanks.

 

I Tried many different freight services starting at oldenburg, ended up in a mess in bremen. (usually stuck on a red light after delmenhorst). The 2 part autotransporter to Bremen. 1. Part 12:15 to Hude was no problem. 2. Part was starting well, but ended up stuck on red lights behind a huge a.i pile all stuck until bremen.

Seems some services are not moving. Yesterday the 425 didnt move into the depot sidings, on todays service the 612 didnt move into the depot there.

 

Holy LOVE you're right. DGS 52710 Part 2 - Congestion.

This is annoying. In TSC's 9 map you can see the state of the automatic switches and make conclusions, in TSW the map is... ridiculous. What the hell are they waiting for?

These two guys are deadlocked it seems - one of their paths is wrong?


Going back to TSW3 and check on this.

EDIT: Not the cause, service top right is eastbound. Removed it but traffic still not moved.

 

Its happens on the enitre timetable, so im asking me right now are there other routes from tsw3, which are messed up, because thats a no Go. I already uninstalled the entire tsw3 folder

 

Must be this one but it is for the devs to debug. If a train is standing across two signal blocks then something's off here. Removing it by clicking on the map and select the remove train option crashed UE.

I've reinstalled TSW3 again (for modding purposes initially, have a dedicated 1TB SSD for TSW) but I feel we might discover some more issues with TSW4... just a feeling.

Btw TSW3 is loading up much faster than TSW4...



DTG Alex please make this a high priority, apparently the whole BRO timetable is broken. And leave a "Helpful" if you have seen this, thank you.

 

Haven’t seen issues like this pop up on other routes yet but this is concerning. Good catch tbh

 

Try this workaround.

Go to the 9 map, locate this service, click on it and select "Remove train". (This time it didn't crash.)

 

For other services, it might help until the issues are solved (if they will be solved), to check the map on service start and see if trains are placed over signals without moving.

 

I can confirm that many services are unplayable (PC/Epic).

 

Bremen Oldenburg is a great route and it is totally unacceptable that each new iteration of TSW breaks previous dlc. I am lucky in that I have had the space to keep TSW3 installed and I am playing all previous dlc's on this. For me the earlier routes are also spoilt because the unofficial mods which make the routes so much better no longer work. Other issues are cropping up all the time. Medals awarded appear in the timetable listings but are no longer added to the profile screen (at least the platinum ones aren't!). Creators club says I have reached the maximum number of downloads when I haven't. Its all starting to be a bit of a disappointment and requires the usual 'customer workarounds' to avoid problems.

 

Can confirm this. Also in journey mode its broken with exact the same behaviour.
You can't remove the faulty train in journey mode though.
This needs to be adressed asap, making every scenarios and timetable session inbound to Bremen impossible.

There is a BR 612 stuck right with its middle on a signal at the platform. It is supposed to drive off the platform into the sidings but instead it just sits there.
https://www.xbox.com/play/media/YS53EME7RJ

 

Not directly related, but more problems with older routes were reported here:
https://forums.dovetailgames.com/threads/no-passengers-mainz-koblenz.74486/
This is looking bad - real bad.

 

Holy &hit, didnt know about the other thread, they really released TSW4 with braking so much stuff on older content..., no words to that.
Well this has to be adressed ASAP,and definetly not in the usual halfhearted fire and forget approach.

So far im very impressed with TSW4, it introduced the right features and opens now a lot of new possibilities for everybody. But seriously DTG, i dont even bother with a new franchais every new year, "buying" the new content from new etc, but why releasing the new successor and botch the entire older content with introducing new bugs.

Currently i regret uninstalling TSW3, The state of the older content is inacceptable. Did somebody even test before release?!

 

I´ve defened DTG for the last couple of weeks... but this is totally unacceptable. It needs to be adressed and sorted swiftly.

 

So I've just completed a ride on Bremen - Oldenburg. To be exact on the DB BR110 as RE(4414) Hannover Hbf - Norddeich Mole and didn't find any error while driving (except for some reason the Station bords are empty)

 

At least some services work...

 

This situation happend to me on a evening service to Bremen, but instead the 612 a 425 was stuck.

 

I was not able to finish DGS 52719 Part 2 after deleting the stuck service, about 4 kms from Bremen Hbf I got a UE crash...

 

It happens to services inbound to Bremen HBF, not outbound to Oldenburg.
That direction i had no issues as well.

 

Okay I may test this tomorrow.

 

Seems also i huge substitution mess. In tsw3 was a mix of all, but now 20x the 155 press spawns for all a.i, but never had a red 185.

I think im gonna uninstall tsw4 and stay away for a while. I didnt pay for botched version, inteoducing a huge mess in all the existing routes.

So the plan here is the paying betatesters have to report every single new bug and hope it gets maybe a fix or maybe not?

Seems also to have problems with route pis and train lights etc etc etc...

No thank you.

 

Just had the same thing RE4431, red signal about 3.5km from Bremen. No save game involved, 9 map shows at least 2 trains ahead also stopped at red signals. Unable to delete (Journry mode).

 

Fully returned to TSW3 for that one, as I can't use my mods on TSW4 anyway atm...

They should remove the "cheat" protection on Journey Mode. It's a single player game anyway, who cares?

 

Another bug to note: if you have old custom scenarios from TSW 3 and edit them in TSW 4, it doesn't check or at least incorrectly checks if a service already exists on the given start point. I made a chained path for my player service and accidentally set the start at a stop that already had a service starting on it, and to my surprise it didn't stop me from doing it, so when I started the scenario, I was greeted with two trains clipping into each other leading to derailment, lol. Happened to me on BRO

 

Surely at least a couple of the beta testers were tasked with checking for this type of thing? BBO was a bit twitchy anyway in 3, with the save game tending to produce signal redouts but more at the Oldenburg end.

Obviously all the testers were “glammed” by the new stuff and didn’t find time to run through the old content.

I will have to try Hamburg to Lubeck later as that was another route with dodgy signalling.

 

Now I've testet RE(4427) Norddeich Mole - Hannover Hbf on the Cab Car of the N-Wagen. I'm Stuck at Bremen Neustadt, in front of me there are 2 Trains waiting. 1x BR425 and another Set of BR110 and N-Wagen. It looks like (in this case) they're stuck because of a BR612 waiting in Bremen Hbf for something which is not clear. One of the Signals shows the BR612 a Shunting Operation.


Yeah it is totally broken. Since there are now (with me) 3 Trains waiting to enter Bremen Hbf, I assume this train (BR612) is standing there for a long time already.

 

Sad to say, but these discoveries certainly put Matt’s comment in a new light.

 

Don't worry, it will be fixed with TSW5 release

 

That's not for shunting, that's an authorization to pass a signal at danger (driving on sight until the next signal). It's a completely inappropriate aspect to show in this context so it does at least make sense that the AI train doesn't know what to do with it.

 

That 612 is supposed to drive into the siding a bit further up, but it does not. It just sits there.
If you spawn on foot however, it is moving about 10 - 15 Minutes after arival. I was curious and observed it over the duration of 90 minutes yesterday.
This 612.. or a 425 sometimes, does arive from direction Oldenburg unloads passenger and then after 10 - 15 Minutes it moves up into the siding.
However, if you are doing a scenario or service then is seems to not leave the platform, even after 1 hour of waiting, blocking the whole inbound to Bremen comming from Oldenburg track.

 

But I think it should show a shunting operation if I'm not wrong. However, before the move to TSW4, it worked at least. Even with the wrong signal aspect.

 

It should, yeah.

 

holy hell this is bad! I might actually at some point just lose it, even though I don't own this route.

 

Its my favourite route when it comes to an interesting timetable. You get looped a lot with freight and most sidings are used in the 24h timetable. Locos uncouple and park on the sidings allover.
Whoever did this timetable, its definetly a masterpiece. (Not "just" a-b)

So yes with tsw4, as much i like the voralberg route, i prefered to start with BRO and test the vectron.
The fist a.i got stuck i was sure its because i spawned trains with the free roam feature (which is a superb feature for tt mode), but then i decided to just do nothing and make a service from the menu and with starting on foot & taking over the train.

Never since tsw i had such problems, spawning on foot was a safe solution to walkaround many redlight bugs in the past.

Seems its not just a "minor" change causing all this.
I mean to have no passengers doesnt brake the route, but was the plan that the paying customers have to report every single bug on every route now??

Again no thank you, DTG you decided to remonetize yor title every year instead of making updates. This is something i can be ok, but do at least your job right and release a finished product.
With Sos was the same, after changing the buffer physics there were bugs on many older routes.

Just because you focus on new routes, it doeant mean older dlcs are not played anymore.

 

I'll look into it tomorrow. We made some changes to the pathfinder and timetable systems (to support the new content and free roam) and obviously exhaustive testing of playing every service on every timetable is impossible.

Edit: It appears that Unload All instructions aren't working correctly on this route, but they were working in TSW3. The engineer responsible (some guy called Will Marshall, never heard of him honestly) has been disciplined and told to find the root cause.

 

It is, but clearly some kind of automated playthrough testing needs to be created, or improved if it exists. The complexity of these routes and the effort it takes to create them is self-evident, but that complexity makes proper testing more important even if it also makes testing harder. That's a conundrum DTG needs to work on solving, as you devs ideally should be basking in the glow of a job well done at this point.

 

Cause found - that's good. I'm sure that Will Marshall guy won't disappoint you and will use his skills successfully to fix this Cheers

 

I have found the exact cause (corrupt asset submitted in August which got bundled in for TSW4 but hasn't made it to any patches for TSW3 yet. For the DTG Employees following along, Change 282739 ) and will be submitting a fix. I can't promise when it will launch but I'll bump it to the release team as a priority. Thanks for the report, maybe next time it'll happen without the gnashing of teeth and wailing of laments?

Edit: Luzern, LeftRhine and PeakForest probably have the same issue. I'll get them fixed too.

 

Brilliant, Will. This thread serves as a textbook example on how to solve issues.

 

I have no idea who you are but I believe I found something that belongs to you

 

It´s always shown that on Bremen-Oldenburg when you go in to those sidings and it´s always been wrong.... the signalling is not great on the whole route to be honest.

 

Seems like NYT maybe affected as well.

 

Top man Will.

Have a virtual beer…

 

Will Marshall , be sure to also check out a 3/4 litre bottle of my local brewery's fine beer. Cheers!

Vern, is that tiny bottle of yours a joke?

 

That's a great idea! And we have the perfect local brewery.

 

First clothes and now beer? What’s next?

 

New York Trenton has a similar issue with passengers that I have found a fix for. Obviously that's not the only issue with that route right now but I can't make any promises other than "passengers should get sorted out"