I've not noticed any signal delays on pre-TSW6 routes, even though it's supposed to be backwards compatible.
Did I miss something? Have TSR's been added retroactively to existing routes now? The reason why I'm asking is, becuase I seem to have stumbled across an invisible TSR yesterday: I did a service on Ludwigsbahn, took an IC from Kaiserslautern to Mannheim, cab forward (don't remember the exact train number and can't look it up since I'm at work now, but the time was around 14:00). Since it's a rather simple service and I know the route quite well by now, I drove without HUD. Right after leaving Neustadt-Böbig, just when I was preparing to go up to 160 km/h, I got a PZB emergency brake out of nowhere. There was no sign, no PZB magnet anywhere as far as I could tell. Switched the HUD on and saw there was a speed restriction down to 70 km/h up ahead. I thought I might have missed the sign. But when I got the train running again, I passed the TSR slowly, and there were no "A" or "E" signs either. Shortly after passing this spot, the line speed rose up to 160 km/h again. To make sure, I went into photo mode and searched the line for an orange "7" sign, but found none. While I would welcome the addition of TSR's to older routes, I'd prefer to actually see them too
Just to add to this, I have encountered an invisible TSR on Stuttgart Heilbronn as well. This was the „the last nail in the coffin“ for me and I have now disabled all random events. They seem to be too unreliable, unfortunately… I want to add, though, I wanted to make sure this is not mod related, which I still need to do. Would be good if others could report this behaviour as well, if encountered, and maybe add if mods were installed or not (not sure mods could do this, just want to rule it out).
Stuttgart-Heilbronn was the first route where I encountered TSR's at all, prior to its release I never had a single TSR (I don't own any other TSW6 routes). There, they worked fine for me so far I don't have many mods installed, but I'll try the same service with the same conditions again this evening without any mods, to double-check.
I can confirm the same on Ludwigsbahn. Suddenly a PZB zwangsbremsung, then speed reduction. And then you pass the invisible magnet on the other side and you get another zwangsbremsung. Kind of very annoying
I haven't had much time to do a lot of TSW these days, but I did some experimentations. So far, the only pre-TSW6 route I encountered TSR's on is Ludwigsbahn. I had two more TSR's there, both were visible and working as intended.
I had my first invisible temporary speed limit encounter in the Ludwigsbahn today. Not one visible sign.
As I just mentioned over in the Stuttgart-Heilbronn feedback thread, invisible TSRs seem to occur there too now. Don't know if it's related to today's update. I think I'll deactivate random events for now. That's the second new TSW6 core feature (the other is train faults) deactivated for me, due to questionable reliability...
Still only ever see 40mph TSR Still only see TSR that are 2 carriages long candacedtg could you ask the team when TSR will actually be fixed?
Random faults - only seen doors getting stuck open/closed TSR - only ever had very short 40 ones, nothing else Signal delays - none that I can remember then again it's hard to tell with this one
Yes, TSRs are always 40mph and the signal checks are so slight that they’re almost never noticeable. It’s odd because it feels as if DTG have done the difficult bit in setting up this degree of randomisation, and now just need to make small tweaks to the parameters to really make them work. On TSRs, once the programming is in place to create 40mph TSRs, I can’t imagine it’s a big job to extend that to give other speeds (in the UK 5mph, 20mph and 50mph are the other common ones). On signal checks, it just needs an adjustment to the degree of variation in the timing of the signal clearing. Currently, from what Matt’s said, I think it’s 10 seconds. It needs to be increased (perhaps to 30 seconds initially) so that the signal checks are noticeable. What’s odd is that not only has this not been done but (as far as I’m aware) there’s been no response from DTG at all when this has been raised. They can’t respond on everything of course, but this was a big new feature and they asked for feedback, so it’s strange not even to acknowledge the issue. The good news is that both features have the potential to be really great, with these small tweaks. I drove the sleeper last night from Plymouth to Exeter (47 hauled stock). We got a 40mph TSR right at the bottom of Hemerdon Bank (where usually you get a good run at the bank at 70mph) and having cleared the TSR we slogged up the next 2 miles of 1-in-42, down to 35mph by the summit. It totally changed the nature of the run, firstly of the climb itself, and then needing to regain the time lost over the remainder of the journey to Exeter (which I did - just!) The fact that this can happen adds so much to TSW. Until this feature was introduced, if I drove the same service multiple times I knew it would be exactly the same, every time. Now there is variety. It just needs those tweaks to realise its full potential.
Further refinement of the virtual dispatcher may be required. Plus there is a lot of time for testing. There's a mod that adds TSR to all German routes. It works, but sometimes the virtual dispatcher sends you on the wrong route to avoid a traffic restriction. And this causes long stops at red lights. Sometimes everything comes to a complete standstill. Sometimes everything is fine and you just reach the speed limit. Literally every flight needs to be checked. Or changes need to be made to the virtual dispatcher.
Screenshot 2026-02-22 170705 by jimbaa posted Feb 26, 2026 at 8:44 PM Is it just me, or is everyone getting the annoying phenomena of TSRs showing in the opposite direction (including AWS) on a unidirectional line? Here we are on the way to Stafford on the down whilst the TSR is showing as if you were heading in the up direction, which is not possible. This happens on all routes for me.
Obviously been flagged before but adding to weight of feedback; TSR is a great idea, but duration renders the feature redundant in its current implementation..
