Still having this annoying bug, almost everytime I play new TSW6 routes: I close the doors, but the HUD still says to close them. No matter what I do... it's impossibile to continue...
I have a question for you about that. Which route was it on? Did you close the doors only when the HUD indicated that the doors should be closed? Because I noticed the same error yesterday on the Dresden–Leipzig route. As long as I waited to close the doors until it appeared in the HUD, everything was fine. Then I was at another station, and I closed the doors about 20 seconds before it appeared in the HUD. And that was the end of the game, because closing the doors appeared in the HUD and it wouldn't go any further. I even tried to open the doors again, which worked, and then closed them. But the HUD still said ‘Lock doors’.
OP said the new TSW6 routes, as a consequence my guess is they are playing with faults disabled but are getting the same bug we all are where that setting does not actually disable faults, just alerts for them. I get doors getting stuck all the time and need to fix them before I can proceed, even with faults set to OFF.
And then it stays stuck at the top of the HUD, even when you close the doors? And how do you repair the doors?
Yes, because as long as there is a fault in one door, that door does not close fully, though at a cursory glance in the external cams it looks closed. The main door closing controls will not affect it and the "close doors" notification remains until it's resolved. You have to find the one that's like half an inch open vs the others and manually open and close it individually at the door itself. It's one place where rolling stock with over the top interior lighting is helpful, because you can see it shining through the tiny crack in the door where it's not fully closing.
Okay, thank you for the explanation. I'll take a look next time it happens again. But I thought I read the following in a thread once. If you close the doors before it says “Close doors” at the top of the HUD, the train may no longer be able to run. And it also said that you should always wait until it says “Close doors” at the top of the HUD before actually closing the doors, because otherwise the HUD error will remain. It may be that there are two errors in TSW6. 1. Errors that you have deactivated but which still appear in the game. 2. An error with the HUD notification if you do not wait to close the doors before it appears at the top of the HUD.
Hi Nika Gear5 In the case of this error, or rather non-error, a disappearing HUD certainly won't help. And the mod you suggested already has its own thread.
I had this issue a few times, I can't remember exact on which routes, but for sure on Dresden - Riesa (yes the old route) with the BR442 . Also I have had the main circuit breaker switching to open while driving, this was on the BR101, also on Dresden - Riesa. Can't remember I had this before, but it seems they introduced nice new bugs for TSW6.
Just happened to me on WCML Preston Carlisle. Service won't complete. Just gets stuck on lock doors. I'm really getting sick of this stuff. This would be such a great sim if everything worked as advertised.
Looks like a basic word association chatbot. Took word frequencies from the posts and found similar other posts on the forums for word frequency but without the capacity to actually process context and meaning of the words written.
LOL What I meant to say was that it is not clear whether this is a TSW6 error or an error caused by the new error function in TSW6.
I was responding to the fact that the post you were responding to seemed to be from a chatbot, not a real human. The complete non-sequitur of suggesting a mod that hides the hud to "help" with hud objectives not updating is the kind of mistake a human who could read and understand the posts in the thread would not make, but a chatbot which measures word association frequency with no concept of what the words mean would dredge up from posts elsewhere on the forum. Unlike your more ambivalent position for now, I am myself however personally strongly convinced that this issue is related to flaws in implementation of the errors functionality having unintended systemic consequences throughout TSW6.
