Despite ETCS being a complex system in real life, and understanding it has to be simplified in game, there are still some relevant errors. Supervision seems to be reasonably ok, including movement authorities, release speed indication on stop signals, speedometer colors, warning sounds, icons and transition from Staff Responsible (SR) to Full Supervision (FS) in Level 1 (Limited Supervision (LS) in the case of this route). However the following things are not available (at least I didn´t find them) or are clear errors in my opinion: Level transitions are apparently not implemented. If you start in Level 0 or Level STM you would normally get an automatic transition to Level 1 (normal operating level of the line) at the first signals of the line start/end at least and other entry points to the line. On the other hand you would expect transitions to Level STM (requiring driver acknowledgement) in areas not fitted with ETCS but still having the national ATP, such as depot. Now if you select a level you will run the whole line in that level --> relevant issue. This feature is already available in game (LGV line with transition between systems). Currently manual selection of levels only allows to force usage of ETCS, force usage of national ATP or isolating both systems (Level 0 case). Infill balises seem to be inactive in some places. You can only get signal updates at main signal balises in those cases --> relevant issue Main line signal progressions are wrong. Many proceed (green) are directly followed by stop (Red). Entry to occupy tracks after signaller approval (TAB menu in game in second scenario for instance) results in signals giving yellow aspect --> relevant issue. Both are a no-go in terms of safety. An occupied block shall always result in most restrictive aspect signal is able to give (stop or override aspects) as interlocking is still detecting the occupied block ahead Override feature (with transition to SR mode) is apparently not available and that prevents overpassing end of authority when required, for instance if a stop signal can´t provide proceed aspect --> relevant issue, specially if we have a situation where you need to enter an occupied track. Onsight mode (OS) would be used in that case but we can assume override is also possible for simplicity. The override feature is already existing in other systems in game (PZB for instance) Overpassing a stop signal does not trigger transition to Trip mode (TR) nor brake application. Mode remains in FS in that case --> relevant safety issue, even if it´s not true to life assuming TR is not implemented for simplicity, as one of the main brake protections is missing. That protection is already existing in other systems in game (PZB for instance) Sometimes brake is applied while being already below release speed. That shouldn´t happen as the reason for release speed is to be able to approach to stop without the constraint of the braking curve, to read a signal change from stop to proceed for instance --> relevant issue 40km/h release speeds are too high (maybe that´s the real value there due to usage of Limited Supervision, I don´t know) but normally release speeds are much lower for safety reasons so that trains don´t run too much distance after overpassing stop signals and occupy the switches area after signal for instance --> value to be confirmed (maybe directly inherited from national ATP regulations) Approach to Luzern buffer stops is not including an end of authority protection at the buffer stop or an Onsight mode transition (used at some countries also) but a fixed 40km/h limit without braking curve instead --> relevant safety issue as it allows crashing into the buffer stop at 40 km/h without any system protection other than the speed limit (a total disaster in a terminal station). Overspeed warning sound (triggered when speedometer needle is orange) can remain active after train is at standstill at platform and needle has returned to standard light grey color. Sound will remain active forever until a new warning (orange/yellow color) happens --> relevant issue Once you are below release speed overspeed warning is still active (see also previous point). This shouldn´t happen as once you are in the release speed area the release speed supervision prevails over the braking curve speed supervision. Needle shall be yellow in that case and corona yellow+brown, because supervision of end of authority distance is still active and you are already in the release speed area, but braking curve speed supervision shall not be active to monitor braking curve speed (that speed supervison is replaced by the release speed limit supervision). In plain words, system shall behave as follows: you are still approaching a end of authority, so distance still has to be monitored and displayed, but you can approach it at 40km/h until you eventually overpass the end of authority --> relevant issue Note: in case of using transition to TR mode and additional step would be also required in game, leading to Post Trip (PT) mode after driver acknowledgement of TR mode. This extra mode allows to move train backwards for some meters (I think standard default value is 200m) to place it in front of signal again, allowing driver to read signal balises once signal is clear. Overpassing the backwards PT distance would lead to another brake application. Anyway overpassing a stop signal in game leads to scenario termination so most likely PT mode will never be used. The following are less criticial things: Shunting mode (SH) is apparently not available --> nice to have for shunting operations There´s no train data entry (no braking capacity nor train lenght setting available for multiple units case therefore, which would be relevant after joining/splitting trains). Start of mission procedure is limited to level selection only --> minor issue if we assume a simplified procedure. Train lenght is at least displayed and it´s updated after coupling 2 units, which is nice detail ETCS should go to Standby mode (SB) after startup, when enabling/disabling driver´s desk. This mode prevents unexpected train movements by commanding brake if they are detected until start of mission is complete (at least until level is selected if we assume a simplified procedure). Currently system starts directly in Level 0 / Unfitted (UN) mode and goes to that state after disabling master key too --> we assume a simplified procedure but a relevant brake protection (standstill supervision) is anyway missing I don´t know if there will be more bugs at some particular situations. The most relevant one I found are very frequent sudden movement authority shortenings that lead to instant overspeeding with brake application (e.g: first scenario while approaching Sursee platform stop and when switching track after changing cabs later on). In both cases you would expect a light grey corona pointing to the target speed of the change of tracks and a braking curve active earlier enough to react as soon as you got the last signal update on the balises (at Sursee exit signal for the changing cabs case). This shouldn´t happen as soon as route is already set in advance (you can have up to 32km movement authorities) but it´s still possible in real life if routes are also changed suddenly by dispatcher. In game it looks as the old LZB issue we had in the early stages of its implementation, most likely caused by taking into account signal aspect for only one block ahead instead of several blocks. With such cab signalling as ETCS system you are expected to get always an smooth approach to speed limits as in the case of LZB, because the information for several blocks ahead is always sent to onboard too. I have not tested all scenarios or services anyway, sorry, so maybe some of the features are somehow hardcoded in the scenarios or services instead of being available on ETCS display. Anyway, most of the main features are included to a nice relevant extent I would say. National ATP also reacts to warning signals requiring driver acknowledgment while in Level STM. I didn´t test the overpassing of stop signals to know if that brake protection exists or not in the national ATP. Cheers
My biggest issue with this route is the wrong signal aspects, means you cant drive no hud without etcs. Havent made tests with tsw4, probably there will be a few surprises.
