Track speed jumps to infinite on first switch

[Tomas9970]

Hello.I keep running into a curious issue when creating test tracks for my switch kits. Note that this isn't directly related to them as I can replicate this even with the German ones but basically when I try to drive on my test tracks, the track speed jumps to infinite (or top speed of the consist) precisely for the duration of the first switch I'm driving over, which also happens to have a -1 speed limit.

From what I know, the sections with -1 speed limit should take the line speed from surrounding track elements but it clearly doesn't work here.

The quick and dirty solution is to just hit Ctrl-D and set the whole switching area to the line speed but I know there are switches with -1 speed already in released modules and they don't have this issue. Is there like a trick or something special that I need to do to make this work as intended?

Thanks in advance.

[Carsten Hölscher]

Is there a switch and a signal in the same track element? That should be two different elements.

Carsten

[Tomas9970]

Hello. I did some more testing and the issue it indeed tied solely to the first switch and doesn't have anything the do with the position of the entry signal. I tested on my draft of the Dürnkrut module (where the entry signal is way back) and it's exactly the same. Please ignore the "Forgot a scheduled stop" message as that's just my hacky way to do an entry without having a second module to depart from.


As for the entry signals being at the same spot as the first switch in my tests, I think it has to do with them being very close to the switch in question (usually 5-10 meters or only 1 track element away) so maybe that's why the game is drawing them at the same spot in the evaluation. It's weird but also kind of an edge case that won't really exist anywhere in a real module.

Here's a test module that I made only using assets that are already in the game and that has the exact same issues.
https://drive.google.com/file/d/1NX5Isk ... sp=sharing

And here's a run from it:


Again, I don't think this is a game bug but more like it's something I don't understand about route-building and that I need explaining.

[Johannes]

Your test file isn't immediately usable as the routes are missing, but apart from that it does look like a bug to me. When the train starts, the maximum speed is given as

GNT oo km/h, signal oo km/h, route oo km/h, LZB oo km/h, ETCS oo km/h
anzeige: oo
invers: oo

although the elements it's on have 100 km/h as maximum speed.

[Carsten Hölscher]

Is there a timetable file that produces this problem?

Carsten

[Tomas9970]

As far as I can tell, it doesn't happen when creating new timetables for already released modules or when running existing timetables from the game. I tried making runs over -1 speed switches in Köln Hbf and Erfurt Pbf and things behaved as intended. So the glitch only happens with new modules.

[Tomas9970]

Ok so, I looked up what the -1 speed limit actually means and chapter 5.3.1.10.1 of the manual says this:

"If the speed is specified as -1 in the route elements, then the last speed is retained"

This means that if you enter the -1 speed element from another one set to 120km/h, you will keep that for the entire section that has -1 speed. That is nice and intuitive and does indeed work just fine in version 3.5.12.0 except when another thing glitches out.

Basically there is now a new intended behaviour where every train spawns with it's speed limit set to -4 (whatever this wildcard means) and that gets adjusted to the proper line speed as soon as the train is given a clear signal. This behaviour seems kinda iffy right now and sometimes (at least for me) the train retains it's -4 speed limit when departing, which can then snowball and cause all sorts of things.

I don't yet know what's causing this or how to consistently replicate it other than that it's tied to the route module where it either glitches out 100% at a time or works perfectly.