schmusegewürzkatze621

Hardware: AMD Ryzen 5300U APU, 16 GB RAM – System: Ubuntu 22.04.2 LTS, Linux 5.19 x86_64 – Drivers: Proton 7.0-6, RADV Mesa 22.2. Every time I try to play as dispatcher in Włoszczowa Północ, I spawn in the middle of the tracks instead of inside the signal box: I cannot move, I cannot look around, and I cannot press 1 to teleport me to the signal box. This has made Włoszczowa Północ unplayable for me.

Olszamowice and Pilichowice, yes. Otherwise both are boring. Maybe not Opoczno Południe, though, that one is fine as it is. Knapówka and Psary would be nice if they could be merged, though. At least with the current timetable.

There’s a track plan on Semaforek (see the page linked above by ErsGT) dated 2015, which has the 130 km/h points.

Hmmm. Is Grodzisk Mazowiecki correct for SimRail? I just drove a 16xxx over 58, 60, 62, 65, and I could not see that ‘13’ on M1. (Then again, I didn’t check the HUD, so I might’ve simply missed it.)

(Nederlands) is correct. It’s the Dutch word for Dutch. Just like the Polish servers have (Polski), the German ones have (Deutsch), the French ones have (Français), …

Sorry, I meant Kozłów. Kozioł is on the Łc–DGWsch line …

I’d still like to see Kozłów.

No, the two needles are the target pressure and actual pressure. The main reservoir has an electronic gauge on the left display.

This happened on DE2 in Olszamowice: The 223034 and the selected 223036 have arrival times at :25 past the hour, 11 minutes of layover, then departure at :25 past the hour. With 11 minutes layover, I’d expect a departure at :36 or arrival at :14; with arrival and departure both at :25, I’d expect the ‘layover’ and ‘stop type’ to be 0 and empty respectively.

Translation note for all non-Germans: Fdl means ‘dispatcher’.

Interesting. That’s something you can’t do on German mechanical signal boxes! Signals can’t be moved without a locked route, and after a route is locked and the associated signal has been cleared and reset to danger, it cannot be cleared again; the route has to be released and re-locked first.

I don’t think signal boxes can be divided into ‘good’ and ‘bad’ that way. Some people might find signal boxes Psary or Dąbrowa Górnicza boring, but personally I occasionally play them explicitly cause I don’t always want to have to do too much thinking. People have varying preferences.

The lack of GSM-R in the simulator is due to the lack of GSM-R in Poland in reality. Also I think that function is probably specific to the UK implementation of GSM-R.

Tbh I’d like to know how that player managed to take a wrong turnout at Zawiercie in the first place.

It’s fairly realistic. Timetables always have some slack so that small delays can be compensated when they arise. And at busy stations, especially for intercity trains, passenger boarding may take a while longer, so the timetable will account for that.

Ah, now it’s working for me, too. Weird. Thanks for the fix!

Fixed where and how? I just checked, the timetable is the same as before – trains are still headed for Idzikowice Roz. 18 on L4 and there’s no second timetable either.

Activity check as part of gameplay. Brilliant idea, I love it.

But in Sosnowiec Gł. signal box you have two timetables for the two posts, and in any case there’s only one direction trains can go. In Idzikowice, I don’t have a second timetable for Idzikowice Roz. 18, so how am I supposed to know whether the train is supposed to go to L574 or to L573? There are trains to both lines!

I’m just saying what I’ve learnt about the real German network. Maybe different countries have different practices there? I guess you’ve got a point about communication. If both drivers call dispatchers to tell them they’re driving slower, and dispatchers call drivers to tell them about faster trains behind them, then these kinds of issues can be resolved without putting the burden on only one of the parties.

No, a dispatcher should assume that I (try to) keep to my timetable.

As I said, it’s the dispatcher’s job in that case to call me and tell me about that circumstance.

But you can’t fault me for driving according to my timetable, can you? If I have ten minutes and fifteen kilometres left till the next stop, then 90 km/h is the speed I need to go, and 100–110 is the speed I will be going, even if my train can do 140 or 160 or even 200. If a train is behind me that was scheduled to leave after me, it will, by nature, be scheduled to arrive at the next post after I do, so there’s no problem there. And if a dispatcher wrongly sends me before a train that should actually have departed before me, I can’t know that. The burden in that case is on them to tell me to go faster so the other train can pass.

‘transistor / mosfet’? You do know that MOSFET stands for ‘metal-oxide-semiconductor field effect transistor’, right? Also, I have to disagree there: traction inverters for three-phase motor drives do not generally use MOSFETs, not for the actual switching at least. Older inverters (80s–90s, e.g. German class 120 and 101 locos and ICE 1 and 2 powerheads) use gate turn-off thyristors; newer ones use insulated-gate bipolar transistors.

If you have information how far it is to the next post and when you’re supposed to pass it/stop there, you can calculate how fast you have to go. In case I’m very early, I generally accelerate to a decent speed and then just coast. If a dispatcher takes issue with that because I’m in front of a train that’s not as early as I am, then they can tell me and/or put me in the loop to let others pass.