schmusegewürzkatze621

You can already open the EDR timetable screen in your browser. Links are on this website in the header under ‘Multiplayer’

Locking a signal is primarily a mechanism to remind the dispatcher not to use the signal. If, for instance, a signal is known to be faulty and unable to show correct ‘proceed’ aspects, dispatchers should route trains through other tracks instead, rather than through the ‘correct’ track using substitute signals or written orders – running with lower capacity and/or lower speed is preferable to running with less safety.

All three of these examples are situations where a signal will not have been cleared in the first place. That’s what the interlocking is for. It’s designed specifically to clear a signal if and only if the path is clear and is secured to remain so. If the route is not free of other vehicles, or the points are not locked in the correct position, or another route is set for a train into the same section from the opposite side, the signal box will prevent the route from being set and locked. The only reason why a cleared signal would ever be revoked – outside of emergencies – is if the route was set in the wrong direction by accident.

Also Zawiercie hab ich vorhin ganz normal spielen können. Ist es denn bei dir auch bei anderen Stellwerken außer D. G. Wsch.?

As of the 01-28 update, when playing with the lighting quality graphics setting set to ‘very low’, the control desk surface appears so bright that I can’t comfortably read labels and see which sections/lamps are lit any more. See attached screenshot. With ‘low’ lighting quality, the desk appears much less bright, and both the labelling and the indicator lamps stand out nicely, just as they should (and just as it was in the previous game version).

Die EU07/EP07/EP08 hat ein Gleichspannungsschaltwerk mit Anfahrwiderständen. Von den vier Fahrmotoren (einer auf jeder Achse) sind die beiden auf einem Drehgestell jeweils in Reihe geschaltet. In den Fahrstufen 1–28 sind die beiden Drehgestelle in Reihe; in 29–43 sind die beiden Drehgestelle parallel geschaltet. Das eine Amperemeter (in SimRail das rechte) ist immer im Stromkreis; in den Parallelfahrstufen wird das zweite auch noch verwendet, sodass man für jeden Zweig eins hat. Dauerfahrstufen ohne Widerstände sind nur die jeweils höchsten Stufen – also Stufe 28 für die Reihenschaltung und Stufe 43 für die Parallelschaltung. Bei der EP07 kannst du, ohne die Motorstromgrenzen zu überschreiten, Stufe 28 etwa ab 30 km/h nutzen und Stufe 43 etwa ab 60 km/h. Bei der EU07 liegen die Werte wegen der anderen Getriebeübersetzung ein Stück niedriger, bei der EP08 entsprechend ein bisschen höher. In den Dauerfahrstufen kannst du durch den irreführenderweise als „Rangierfahrhebel“ bezeichneten Hebel das Erregerfeld der Motoren schwächen (auch genannt „shuntieren“ vom englischen ‘shunt’ – daher auch die Fehlübersetzung). Dadurch wird der Strom und damit die Zugkraft größer. Um zügig zu beschleunigen, empfiehlt es sich, aus Stufe 28 direkt weiter aufzuschalten in den Parallelbetrieb. Wenn du es nicht eilig hast, kannst du aber auch erst mal auf Stufe 28 bleiben und die Shuntierung nach und nach bis auf Maximum schalten, dann die Shuntierung ab und mit dem Rad direkt auf die 43 hoch. Damit bist du sparsamer unterwegs und schonst die Widerstände (auch wenn das dem Spiel (momentan noch) komplett egal ist). Du musst allerdings aufpassen – wenn du in Stufe 28 shuntierst und dann das Rad weiterdrehst, bleibt das Schaltwerk noch so lange in Stufe 28 stehen, bis du den Shunthebel wieder auf 0 gestellt hast. Vielleicht ist es das, was dir passiert ist, weswegen du nicht auf Geschwindigkeit kommst?

Never heard of that, never noticed anything like it when riding any electric train here in Germany. I’d have thought that with modern semiconductor-controlled three-phase motors the difference would be negligible. Why would they all have automatic speed control if it were inefficient? Maybe it applies only to old locomotives with series-wound motors and transformer tap changers? Or maybe it’s diesel trains – internal combustion engines, as should be common knowledge, are most efficient at or near full load, and least efficient at light load or no load (idling). Not sure what bprog means about coasting in modern cars being obsolete, by the way. After all, coasting in gear often means you’re not consuming any fuel at all, provided the engine RPM is high enough. Not sure what an ‘IBGT MOSFET’ is supposed to be, by the way. Thyristors, insulated-gate bipolar transistors (IGBTs), and metal-oxide-semiconductor field-effect transistors (MOSFETs) are three distinct kinds of semiconductor devices with fairly different characteristics.

Yeah, I’ve noticed this, too. I assume the gauge in the game currently shows a percentage of whatever is currently the limiting factor – at lower speeds, that’s current tractive effort divided by maximum tractive effort (250 kN); at higher speeds, that’s current electrical power divided by full electrical power (6 MW). Traction control (‘throttle’) levers are often interpreted exactly like that (at least when AFB/tempomat is off), so you have finer-grained control at higher speeds. However, the traction gauges/displays generally measure actual tractive effort, even where they’re labelled with percentages only. In SimRail, it’s as you said – not just in the ED250, but also e.g. in the Traxx and in the Dragon.

No, you’re right … only the current/previous location and the next three are displayed. Another reason why I’d like more.

Isn’t that simply because the switch is a two-way toggle? A red light with a hand brake pictogram should turn on in the panel on the right when you press ‘Activate’ and should go out when you press ‘Deactivate’.

On DE3, driving TCE 245061 down from Tunel towards Bukowno. There’s a temporary slow zone for 20 km/h at a level crossing, with an end sign with a C. I thought this meant that I was allowed to accelerate directly after passing the sign, but the game kept displaying a speed limit of 20. So I waited until the whole train had passed the location. Still the game displayed 20 km/h, and when I tried accelerating anyway, I got points docked for violating the speed limit. I drove at 40 km/h through Zarzecze. Halfway on the way to Chrząstowice Olkuskie I enabled the bot – it slowed down to 20 immediately. As of writing this, the train’s still going at that speed and it’ll probably be another half hour till it’s in Jaroszowiec.

To be fair, those things are displayed when you’re driving the train … just not in the selection menu. But I agree, this information should also be displayed there. Even Zusi 3, which is not exactly what I’d call good UI design, does this.

Well, I don’t know what kind of regulation Italy has, but in other countries, unless it’s an emergency, dispatchers are simply not allowed to revoke a signal that they’ve already cleared. Doubly so if the train it’s for has already passed the distant signal.

The issue here is that Numpad Enter is an undocumented keybinding for selecting the radio chat. You can work around it by choosing a different key for PTT.

Agreeing on giving players information about trains in multiplayer. Train length is vitally important for judging where speed limits end if you want to drive without HUD, and for passenger trains, how much leeway you have at platforms. And train mass and brake percentage of loco-hauled trains is good to know for judging acceleration and braking behaviour. Good to hear that the dispatcher’s timetable is getting an overhaul, too. It’s not bad as it is, but could definitely use some improvement.

Signal aspects aren’t part of the timetable. How could they be? And what do you mean, ‘change a signal light’?

So how do you read your timetable then?

AFB on locomotives also adds a bit of train brake to the electric brake if the decrease is large and/or the train is heavy, but it also doesn’t know that after pressure is back at 5 bar you have to wait till the brakes on the entire train are released before switching traction force back up, leading to wasted energy and unnecessary stress on the couplings.

Currently you can drive mostly without the right-side HUD but not entirely – e.g. sometimes there are no W27a boards for a speed limit raise. And you still need your timetable on the left. I agree that having a ‘proper’ working timetable with all the route data would be good. Also, yeah, in Poland, apart from ETCS on a few important high-speed lines, there is no cab signalling or other safety system (SHP barely counts, it just tells you ‘there is a signal’). Drivers have to look at the lineside signals and their working timetable. Or at the train simulator’s HUD, I guess.

I also play on Linux via Steam Play on a waaaay lower spec machine (Ryzen 3 5300U laptop, 16 GB RAM, integrated graphics chip) … and intermittent freezes don’t happen for me. Stuttering, yes. Eventual performance degradation likely due to running out of graphics-available memory, yes. But nothing like what you described.

I’ve found that happening sometimes in multiplayer when driving through the platform track at Łazy.

In my experience this happens in all computer signal boxes, not just at Góra Włodowska.

Today I was driving TLK 61126 through the Warszawa cross-city line coming from Zachodnia into Centralna. As I entered Centralna, the screen suddenly went white and I could only come to a stop at the platform by switching on the F2 and F4 HUD. Screenshot from the cab after stopping at the platform: Screenshot from outside (I exited the cab and jumped onto the platform): Two days ago I also had a similar problem in the same location, though not quite as extreme – at least I could still see my surroundings: CPU/GPU: AMD Ryzen 3 5300U integrated Radeon Vega graphics – OS: Ubuntu 22.04.1 LTS x86_64 – Proton: v7.0-5 – Vulkan driver: RADV Mesa v22.0.5-0ubuntu0.3 Graphics settings: Custom – based on ‘Very low’ preset but LODs, densities, and render distance even further reduced; upscaling turned off; AA set to TAA with lowest quality

I’d already be happy with having a working timetable like that available to view in-game. As it is, we only have the basic timetable HUD, which is unfortunately rather less detailed …

When I choose an EIP/EIJ service with an ED250 train, and the train is currently moving when I take over, when I push the drive handle forward, the traction display stays at zero and the train doesn’t accelerate. I have tried various methods to rectify this, but only one has been successful: braking to a stop somewhere and starting back up from zero. This doesn’t happen when I take over while the train is standing in a station. It also doesn’t happen in the singleplayer Katowice–Warszawa mission I tested (since I’m cold starting the train there).