Hi all, I'm looking for help figuring out some strange dispatcher behaviours. Short version: A "Go To" and a "Go Via" instruction (both with "Dispatch Beyond" unchecked) will result in subtly different behaviour from the signaller. I need the "Go To" behaviour but I don't want the train to have to stop. Is there any way to achieve this? Long version: I'm trying to get correct signal aspects for shunting moves from the dispatcher at Dresden Hbf in DRA. (Head to Lamplight 's website for a quick explanation of train moves vs shunting moves). TSW can't really distinguish between train and shunting moves, but through some trial and error in Free Roam Mode I've discovered that if there is a protection signal between two main signals, requesting a path only as far as that protection signal will make the main signal display the correct Hp 0 + Sh 1 aspect if it's capable of that. 1. Path from Dresden Hbf track 14 to just in front of a protection signal (in Free Roam) 2. Hp 0 + Sh 1 signal aspect resulting from the path in screenshot 1 3. For comparison: Path from the same location to the next main signal. 4. Ks 2 aspect resulting from the path in screenshot 3. I was very happy about this discovery as I assumed it would allow me to get the dispatcher to display shunting aspects for some of the ECS moves in my DRA timetable if I simply placed a "Go Via" instruction with "Dispatch Beyond" unticked between each Main and Protection Signal. But here's the thing: It doesn't! If I, say, place a "Go To" instruction in the same place as in screenshot 3, with a "Go Via, Don't Dispatch Beyond" instruction in the same place as in screenshot 1, I get the Ks 2 aspect from screenshot 4. Aside from not being what I want, it also doesn't make any sense to me: Being a main signal aspect, Ks 2 authorizes me to go as far as the next main signal... which is located, you know, beyond the "Don't Dispatch Beyond" instruction! Is there any way to make "Don't Dispatch Beyond" on a "Go Via" instruction actually not dispatch beyond the instruction, ie get the same Dispatcher Behaviour as if I'd placed a "Go To, Don't Dispatch Beyond" instruction? Sorry for the tag DTG Matt, but I'd really appreciate if you could help out here. Is this intentional behaviour from the dispatcher and is there any way around it?
I',m not Matt but I'm happy to take a look at this later when I'm back from shopping with my mother. (I'm part of the Gameplay team) - I'll have a look on both the internal editor and the public editor to check both have the same result and play around a bit and get back to you. - I'm not entirely sure if this is intended behaviour or not so will do my best to replicate and attempt to see if I can get it to do what you want
