Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
There are two approaches how to learn German signaling - you can either memorize every single rule (and re-memorize them with every update - and this is a valid approach, make no mistake, but it is time consuming), or you can simply “get hang of it” and just follow it by applying logic, which simply requires certain level of abstraction not everyone is simply put capable of.
The bottom line is therefore pretty simple – if you want to create something based on German signal book, you have to be either diligent – or intelligent, preferably both.
But if you are neither, well, then this is simply a disaster in waiting…
The most annoying to me are signals practically missing boards, as well as signal priorities being seemingly random (permissive speed limit over restrictive lights = permission wins). Koblenz-Trier has custom signaling and it's even more like this. Also how Pzb magnets are placed quite randomly, so you don't always have to acknowledge, although it usually doesn't hurt. For a while I kept messing up combined signals (by not acknowledging), coming in a range of varieties.
Over time I just found that German rules are a bit sophisticated, but as a real driver you'd probably know them as part of route knowledge. There have been real life incidents due to inconsistencies, such as a Köln-Koblenz train derailing on a switch, having accelerated after clearing a switch - as you always do, right?
The most prominent issue I'm encountering is the multilayer speed limits: track speed, signal speed, signal expiry force override speed, and one of them wins with the others lingering, thus changing cameras can trigger a speeding penalty momentarily. It's not unique to German routes, you can make it happen in the US (NEC, NJCL), possibly even the UK.
Which routes are you talking about? Would help to know, to narrow down if it is indeed a route problem or a driver problem. ;-)
Everything OK till I hit the station before Eutin, which you don't stop at. 120kph line. First signal before the station was definitely steady green and I'm pretty sure the 2nd was too. No speed signs or anything on the HUD.
Limit dropped to 60. Speeding.
Then stopped at Eutin.
Departed. Line speed 60. Increased to 70 then suddenly dropped to 40 for about 400m. No signals, no signs, no warning on the HUD. Speeding.
Maybe its about learning the route.. but it just makes you want to avoid the German routes altogether.
You will need a lot of freeware scenery to make it work though.
As I said earlier, third party routes are much better. Konstanz-Villingen(-Hausach), Münster-Bremen, Freiburg-Basel for example are excellent routes.
Can't remember the original route I was driving when I made the first post but it was an ICE3 on a DTG route and it was even worse than the 648 today.
Playing the NJCL / NJT GP40PH-2B and... well, it's a nice loco for quick drives. Full power can't meet the timetable. Must ignore restrictive signals. Only by disabling (not enabling) all safety systems.
The NJCL itself has a few signaling issues, mostly a few Approach signals in the middle of nowhere, but there is an actual signal showing Approach all the time, I think South Amboy.
It's the standard of quality. Not bad, but some mistakes everywhere. There is a won't fix policy. They did a few, and messed up other things in the process.