A Database Of Outstanding Bugs

Well, I can, since I play on PC, but console users are screwed since they don't have the teleport function

 

I don't have a video of it, might do one when I've got the time. The error is easily reproducible.

Re-checked it, and it's basically only the service starting at 00:03. It's the only one which leads you onto the main tracks and outside the boundaries instead of the little dead-end branch like all others.

I'll do a run up and down the route tomorrow, and note down any missing signs, as well as the missing signal near Heidesheim. Got no time to do it today, sadly.

It's not a bug, but detracting from the game nonetheless. Right off the bat, I could think of a couple of better and more intuitive solutions than these stop markers.

That's not a solution, it's a workaround. If I'd take over a train from someone else (be it from a previous service or fresh from depot), I expect the train to be set up properly. Especially the rear cab. For the same reason I long for a "start with active safety systems" option.

A similar problem exists on all routes which feature BR 110 with n-Wagen (Bnrdzf). When you start with the cab forward, the loco's red rear lights should be turned on, but aren't. And since they can't be turned on from the cab, you have to walk all the way back to turn them on.

 

And not just for certain routes/trains since certain routes/trains, they do.

 

Don't the points go to the right route and train, so only the labels are wrong?

 

Think I did read that’s the case, but still a niggling bug nonetheless.

 

Regarding the issue of missing speed limit signs along Linke Rheinstrecke, I made some notes while taking two IC's up and down the route
There are not as many signs missing as I originally thought, some of them are just mounted in weird places so I tend to forget about them... quite embarrassing, really
Don't wanna clutter everything with more or less helpful screenshots, I just noted at which point the signs should be, using the route's own kilometer signs as reference.
For good measure, I also included some other speed-related issues which came to my mind.

From Mainz to Koblenz
-Missing Vorsignal before Heidesheim, at about kilometer 19,0.
-Missing upcoming speed 100 km/h sign (orange triangle with a 10) at the Ausfahrsignal of Oberwesel, on the left and right track. The signal of the middle (main) track has got one, but all three should have it.
-At the entrance of Koblenz station, there are signs for a speed limit of 100 km/h (orange triangle with a 10 and white rectangle with a 10) for trains, which are going straight into platform 3. Which is correct. Albeit the user interface shows a speed reduction to 120 km/h, which is not correct.

From Koblenz to Mainz
-Missing upcoming speed 110 km/h sign (orange triangle with an 11) at kilometer 105,6.
-At kilometer 118,3, the speed drops down from 140 to 100 km/h. The signs show this correctly, but the UI tells you a drop to 120 km/h and then immediately further to 100 km/h. Can be startling if one is not that familiar with the route.
-Missing upcoming speed 100 km/h sign (orange triangle with a 10) at kilometer 150,6 and speed limit 100 km/h sign (white rectangle with a 10) at kilometer 151,6.

 

There are a few scenario's that can't be completed (or only with a workaround):

- Rapid transit, Leipziger scenario: the doubled up unit exhibits strange behaviour. Brakes not working and a lot of wheelslip. Can't be completed because it derails near the end;
- Vorarlberg, international rescue: can't be finished because of a signal stuck at red;
- Bremen, Stuck in the middle with Hude: after you run around the consist with the loco at Oldenburg, the brakes don't work (can be worked around by resetting the simulation).

A few other things:
- Bremen Oldenburg: some freight services spawn you in random places, no train to be found;
- Some services in London Victoria (BML) and London Euston (WCML south) spawn on top of the buffers and derail

These things should be relatively easy to fix, if deemed important enough...

 

I can tell you what the problem is with double 1442 consists in RT, while it's still a bug, you can solve it by making sure the rear EMU repeats the commands coming from the front one. I don't remember the exact steps right now but the base problem seems to be that it does not apply brake nor traction when you do from the front, and I was able to remedy that somewhen somehow.

EDIT: Tried now on TSW5: again, while the fact this needs to be done is still a bug, do this.
Follow the instructions up to opening the doors, while you wait for the passengers to board exit the front cab and head into the front cab of the rear 1442, turn the main switch to On and close the MCB (this unlocks the rear 1442 giving you forward traction already) then turn the main switch back to Off (and this will additionally unlock the rear 1442 giving you electric braking). You can go back and continue as normal now.
I wouldn't save and leave along the scenario though cause resuming doesn't really work well here....

 

Thanks! I'll try that.

 

Which signal is this?

Which services are these?

 

Signal SBLWs1

Can't recall, see if I can find some of the numbers.

 

During scenario “malfunctioning madness” on Salzburg-Rosenheim, the controller function for resetting SIFA (circle on PS5) does not work on the 766 Dosto. It does work on timetable services for the same Dosto.

On Semmeringbahn, the controller functions for Cruise Control on the OBB 4024 don’t work. Furthermore, on the downhill the cruise control doesn’t function optimally (goes 1 kmh faster than set, so not enough brake applied).

With services on Dresden Riesa with the BR 442, no bonus points are awarded for driving with safety systems on, despite them being switched on and clearly functioning.

 

Also posted this in the Maintalbahn feedback thread, just wanted it to add to here as well.

DLC: Maintalbahn
Type: Gameplay
Severity: High
Description: In Journey mode, service EZK 54877, part one with the BR 363 is broken in a very weird way. At the start, once the brakes are released, the loco just takes off like a bullet and can't be stopped by any means. It just shoots out onto the main track towards Gemünden with way more than 60 km/h.Tried it with different versions of the 363, always the same result.
In timetable mode, the same service works perfectly fine.
No, I don't have a video on this. But it can be reproduced easily by simply starting the service and releasing the brakes.


And something else which just came to my mind:
DLC: Tharandter Rampe and BR 612 in general
Type: Vehicle issue
Severity: Medium
Description: The cab light in the BR 612 is basically nonexistent and forces you to set up the train while standing up, holding a flashlight at night. Very inconvenient.

 

On both of JT's routes, at Preston, you cannot go between platforms 3 and 4 using the external camera. You'll just get booted to above the roof.

 

Just to add to this growing thread. Title says "Solved" but it is anything but.

[solved] Db Br 218 To The Rescue Scenario Broken

 

Just a few bugs I encountered today:

DLC Bremen - Oldenburg:
Arriving at Bremen with an RE from Nordenham (BR 425), the entrance signal to Bremen shows yellow with a white "2" for 20 kph (Ks2+Zs3). The distant signal and the repeaters should show flashing green with a yellow "2" (Ks1+Zs3v), but just show flashing green - this signal doesn't even exist.

On HRR I recently encountered Yellow + a yellow "6" at the distant entrance signal to Bochum while the entrance signal was showing yellow + white "6" - the distance signal should show flashing green instead of yellow.

DLC Hamburg - Lübeck:
Substition between the 112 and the 114 causes the timetable to break, because AI trains will open the doors on the wrong side, thus fail to reach their objective, meaning they will never depart from the first station they arrive at. Just had a jam of 6 trains into Hamburg coming from Lubeck, because the train waiting at Hamburg Hbf opened the doors on the wrong side...
In fact I just wrote a post about this:
https://forums.dovetailgames.com/threads/substitution-on-hbk-breaks-the-timetable.88450/

The ampere meter on the HBK Dosto cab car doesn't work. As soon as you just use a bit traction, the ampere meter goes to maximum.
The missing running sounds on the cab car - after that many years of not fixing them I'm not sure if this is a bug or feature...

Another bug I encountered a few weeks ago on WCML South:
Using the emergency plunger or putting the reverser into neutral accidently (apparently also while standing at a station) causes the brakes never to release. Even resetting the physics won't work, although there seems to be a workaround with turning the battery off and on. This didn't work when I tried though.
https://forums.dovetailgames.com/th...s-350-1-from-safety-devices-trip-fault.87731/

I guess many more bugs to report.

 

Another one:

SEHS collectibles: the total number of collectibles on the route is higher than what it actually tells you. Makes it difficult to know if you've actually found them all. Only applies to the TSW3+ version.

 

This is easy to explain, when SEHS was extended, 4x 11 additional collectibles were added to the new section, bringing the total number from 100 to 144. The menu shows 4x 36/25 collectibles or 144/100. DTG simply forgot to update the menu after the extension to reflect the new number of collectibles.

 

The guide on TSWmania.com has all collectibles, including the extension. So if you want to make sure you have everything, follow that guide.

 

On SEHS, take a train out of the shed at Ashford Depot (an alarm sounds when you do this which is a cool detail), take it to the shunt and change ends. You can then drive out of the Depot by passing a red signal that you are facing. You'll get stopped by a red signal before the platforms though.

 

I couldn't reproduce this on PC. What platform are you on?

Are the signals numbered, and if so can you provide their numbers?

From testing this appears to be an issue with the BR 112 rather than the cab car.

Do you have a video or similar?

 

I'm on PC, Steam. But it seems to be an intermittent issue, I just tried it again two times and it bugged both times, tried it a third time and it worked. The world is a weird place.

 

If it means anything, I could reproduce that here also on PC the behaviour is definitely different between Journey and timetable.

 

That Maintalbahn bug with EZK 54877 happened to me on PS5.

 

The bug with the Vorarlberg scenario seems to be resolved. It wasn't in the patch notes, but Alex confirmed that something was patched: https://forums.dovetailgames.com/threads/jan-21-updates.88642/page-2#post-957694

Anyway, I tested it and the scenario can be completed now (PS5)

 

I've moved the bug to a new "fixed bugs" section; only fair to give DTG credit if they do fix bugs.

And of course since there are plenty of unfixed bugs that aren't on the list yet, keep those reports coming!

 

Can you record a video of the bug, ideally with the latest Maintalbahn update?

 

Don't know if I've mentioned this, but on both JT routes, you cannot move between platforms 3 and 4 at Preston using the external camera.

 

I'm still on TSW4 so maybe someone can concur if it's still the case in TSW5, but on PS5 the game crashes every time if you cycle through external views on a very long train. Or even if watch the train pass you with the free camera, and then you attempt to come back to the first person view in the cab, there's a very good probability the game would crash.

 

With a recent large update (that fixed at least one bug that was on the list) I'd like to remind people to submit bugs - and inform me of any that have been fixed.

 

I started playing on the class 350 on Xbox this morning and here are some Broken features:
The brakes are way to harsh even though they got patched a few weeks ago
Desk light dimmer only goes to 100% or 0%
Vigilance pedal doesn’t rise when raised
PBC has an extra power notch that does nothing
AI class 350 have their tail lights turned on on the front of the train with the day head

 

The Dosto from Mannheim-Kaiserslautern sometimes loses power when powering off, braking and then trying to power up again. It also gives the player assist message to release the brakes before powering up again at the wrong moments.

Using another Dosto (tested the Frankfurt-Fulda Dosto for this) does not give this problem

 

Is there a way to consistently reproduce this?

 

Start a timetable with the MKN Dosto from Mannheim, safety systems on. The problem seems to occur every time you let the throttle run down, and brake with the train brakes. It occurs soon in the service, as you have to brake a few times early on, with the stops in Ludwigshafen.

You don't get power, even after making sure the throttle is off after using the train brake, before powering up again. Raising the pantograph and closing the MCB does not help. It did recover for me after the station stop, but occured again further on in the service.

Retested with the same Dosto: problem keeps occuring. Retested with another Dosto iteration (FTF): problem does not occur.

 

I'd like to add the FTF problem of the LZB not ending before gelnhausen (from Frankfurt to Fulda) but continuing on until Wächtersbach is still not fixed

I recall a stop marker making freight trains holding at that station not enter the full track and blocking services for 15 minutes. forgot the name but that might be a still existing bug too.

Mittenwald's invisible walls on the underground section of Innsbruck, making you unable to leave to the tracks will most likely be fixed in the next update but might as well mention it.

 

Can't reproduce, can you record a video?

 

Do you have links to more detailed explanations of these issues?

 

When I get the chance, I will try that

 

should be in the official feedback thread. off to work in a bit so I can explain them better myself too. the LZB one doesn;t need much more explanation though. it should end and it doesn't.

 

Sorry, can't seem to consistently reproduce. I also tried after the update. It wasn't in the patch notes, but you never know.

The player assist message does persist though.

 

Can you consistently reproduce the player assist message?