By now I am sure most of you have had a chance to give the new NEC: New York DLC a try. If you have turned on ATC and ACSES, you have definitely struggled with those systems. The good news is that it's not you. These systems are quite bugged. The goal of this post is to explain how these systems should work, how Dovetail Games implemented them, and ultimately how Dovetail Games can fix them. HOW THESE SYSTEMS SHOULD WORK Let's start with the cab signal system. The top part of the Aspect Display Unit (ADU) displays the signal conditions in the block you are currently occupying, not the conditions ahead of you. As you transition between signal blocks, the ADU will update the cab signal aspect accordingly. So if the signal you just passed is Medium Clear, the ADU will display Approach Medium. The cab signal aspect must conform to fixed wayside signals that you pass. This means you aren't going to pass a Clear signal and have the ADU display Approach Limited. If that does happen, there is a malfunction. Use the below table to see how fixed signals conform to the aspect displayed in the cab. This comes directly from NORAC Rule #552, "Conformity Between Cab Signals and Fixed Signals". Now for Automatic Train Control (ATC). ATC's job is to ensure the engineer complies with speed restrictions associated with signals, and signals only. For example, you currently have an Approach Medium aspect in the cab and you pass an Approach signal. The ADU will change to to Approach (see the table above for how the ADU should conform to the fixed signal you just passed) and ATC will enforce a signal speed of 30MPH. If you are exceeding 30MPH at this time, an audible alarm will sound. ATC will give you 6 seconds to apply the necessary amount of braking and acknowledge the drop in signal aspect. Once these two requirements are met, the alarm will turn off. Once the engineer reaches the signal speed (30MPH in this example), he can release the brakes and continue. It must be understood that ATC only enforces speed restrictions associated with signals, not civil speed limits. That is the job of Advanced Civil Speed Enforcement System (ACSES). ACSES is the Positive Train Control (PTC) used on the Northeast Corridor and provides additional layers of safety. The most important feature of ACSES is its ability to enforce civil speed limits. These are the maximum authorized speeds for any particular area. For example, I live next to a 150MPH section of the Northeast Corridor in Rhode Island. Beyond that is a 130MPH curve and then another 150MPH section. These are civil speed limits and ACSES has the ability to enforce these. If a train is on that 150MPH piece of track, ACSES will ensure that the train does not exceed it. When the same train is approaching the 130MPH curve, ACSES enforces that by means of braking curves. At all times, the on-board ACSES computer is aware train's speed and the distance to the next restriction. By using this information, it is always calculating a maximum safe braking curve AND an alert curve. The maximum safe braking curve is just that, the absolute latest the train can start braking and still meet the speed requirements of the upcoming restriction. The alert curve is more restrictive than the maximum safe braking curve and it's what the engineer has to follow. When the alert curve has been reached, the numerals in the Maximum Authorized Speed (MAS) section of the ADU will immediately change to that of the upcoming restriction. When the train's speed exceeds that of the alert curve, an audible alarm sounds and the engineer must apply brakes within 8 seconds to avoid a penalty. Once the train's speed is returned to the civil speed limit, the alarm is silenced. However, if the engineer does not slow the train down and he exceeds the braking curve, penalty brakes are immediately applied. This penalty application is released once the train is at or below the civil speeds and is known as a "running release". ACSES can also enforce positive stop at interlocking home signals. This means that if the home signal at an interlocking is displaying a STOP aspect, the on-board ACSES apparatus will ensure the train comes to a complete stop before the signal. Additionally, ACSES can also enforce temporary speed restrictions in real time for situations such as work crews. HOW DOVETAIL GAMES DESIGNED THESE SYSTEMS Now let's discuss how Dovetail Games implemented these systems, starting with the cab signal system. THIS FIRST ONE HAS BEEN FIXED! In this DLC, the ADU does not properly conform to block conditions. I just loaded up a service starting at Newark Airport. I am on No. 1 track and will be switching to No. 2 track at Hunter interlocking. The home signal at Hunter is displaying Medium Clear, but the ADU is showing Clear. Since I am in the signal block before Hunter, the ADU should be reading Approach Medium and the MAS should be 45MPH. But since the current block conditions aren't being reflected on the ADU, ATC can't enforce the proper signal speeds and the ACSES braking curve calculations get messed up. Many issues with ATC and ACSES stem from the cab signal system not displaying accurate block conditions on the ADU. Since the home signal at Hunter is a "Medium Clear" aspect, the signal block I am currently occupying should be "Approach Medium". The Cab Signal System did not pick up on this and believes the signal indication for this block is "Clear". Now to Automatic Train Control. The functionality of ATC is there, give or take a few things. If the ADU shows an aspect more restrictive than Clear, ATC will enforce the signal speed. However, the time to comply should be 6 seconds, not 5. Furthermore, upon applying the necessary braking and acknowledging the reduction in signal aspect, the audible alarm should stop. It doesn't always detect when you have properly acknoelwledged an ATC alarm. Finally, the braking penalty should be a Full Service application, not Emergency. Let's talk about ACSES. Dovetail Games did program the functionality of enforcing civil speed limits and they implemented the braking curve calculations. The numerals shouldnt count down as you reach a restriction. If you exceed the alert curve, the speed of the new restriction immediately shows up. If you never exceed the alert curve and brake very nicely to the next restriction, the MAS on the ADU will only change when you actually reach the restriction. This is to prevent engineer reliance on the system. The engineer needs to memorize the speed limits. Now let's get into the issues with the signals themselves. The signal aspects and their conformity to the cab signal system need to be revised. HOW DOVETAIL GAMES CAN FIX THESE SYSTEMS Ensure current block conditions are accurately reflected on the Aspect Display Unit. Use the table posted above to ensure conformity. Here are some examples. You pass an Approach Limited signal. The ADU should display Approach Medium 45 in order to conform. You pass a Restricting signal. The ADU should display Restricting in order to conform. You pass a Clear signal. The ADU should display Clear 125 in order to conform. 2. Ensure the alarm is turned off at the correct time. ATC alarms turn off when the proper braking is applied (suppression) and the acknowledge button is pressed. ACSES alarms turn off when the train's speed returns to the civil speed limit. 3. Fix the signal aspects and signal progressions. We shouldn't see "Slow Approach" at all on the mainline. It's just not a normal aspect here. Signals have natural progressions that gradually bring trains down to required speeds. We shouldn't be going from Approach Limited to Slow Approach. It just doesn't happen. Some common progressions are... Approach --> Stop OR Stop & Proceed Approach Limited --> Approach --> Stop OR Stop & Proceed Approach Limited --> Limited Clear Approach Medium --> Medium Clear Approach Slow --> Slow Clear The "C" lights on the signals shouldn't be used unless the cab signal system has failed. The "C" light is used to tell trains with inoperative cab signal systems that the route is clear to the next interlocking. In the game I see this at Rea interlocking pretty frequently. It's nice that DTG made the signals display this, but it isn't necessary unless the cab signalling system has failed. And IF the "C" light is lit, the "C" light on the ADU should also be lit. A maximum speed of 79MPH should be enforced in this particular situation. There are many examples of malformed/abnormal signal aspects in the route. I have seen tri-light/cluster light signals with all three bulbs illuminated with pure white. I have seen NYP signals with two lights illuminated on on the top, I have seen tri-light/cluster light signals with no bulbs illuminated at all on the bottom head...the list goes on. I hope Dovetail Games takes the time to fix these crucial systems. It makes the simulation much more enjoyable when these systems work properly. If anyone wants more details on how these systems work, just hit me up. I am happy to answer any questions you have. Thanks, Brandon DEFINITIONS AUTOMATIC BLOCK SIGNAL: A block signal that is activated either by track circuit or in conjunction with interlocking or controlled point circuits. This block signal automatically indicates track condition and block occupancy BLOCK: A length of track with defined limits on which train movements are governed by block signals, cab signals, or Form D. BLOCK SIGNAL: A fixed signal displayed to trains at the entrance of a block to govern use of that block. CAB SIGNAL: A signal that is located in the engine control compartment and which indicates track occupancy or condition. The cab signal is used in conjunction with interlocking signals and with or in lieu of block signals. DISTANT SIGNAL: A fixed signal used to govern the approach of a train to a home signal. HOME SIGNAL: A fixed signal governing entrance to an interlocking or controlled point. INTERLOCKING (Int): An interconnection of signals and signal appliances such that their movements must succeed each other in a predetermined sequence, assuring that signals cannot be displayed simultaneously on conflicting routes. Interlocking rules are in effect in an interlocking. SIGNAL ASPECT: The signal appearance, which conveys an indication as viewed either (1) from the direction of an approaching train, or (2) on the cab signal display unit in the engine control compartment. SIGNAL INDICATION: The required action conveyed by the aspect of a signal. NORMAL SPEED: The maximum authorized speed. LIMITED SPEED: For passenger trains, not exceeding 45 MPH; for freight trains, not exceeding 40 MPH. MEDIUM SPEED: Not exceeding 30 MPH. SLOW SPEED: Not exceeding 15 MPH. RESTRICTED SPEED: Not exceeding 20MPH outside interlocking limits, 15MPH within interlocking limits.
This is very useful and I did notice those signal issues in the videos that I have watched. Did you mention this? (See picture).
So the manual seems to suggest that the time to penalty should appear before the ACSES speed drops, and that going over the dropping ACSES speed would be bad-so it seems that the current implementation in DTGs mind is that the warning curve that the engineer sees is equivalent in function to the braking curve?
The time to penalty will pop up when the alert curve is exceeded. It's to warn the engineer that he has X seconds to brake or he will get a penalty application.
When the alarm is stuck on, you're down to the required speed, and pressing Q doesn't help, sometimes Tab, then Esc, then Q will stop it.
Hey folks, Thanks for posting up that doc Cactus, I've pinged this thread over to the development team to be incorporated into their next NEC update efforts. Best, Martin
Meh, some of it was fixed. The route is mostly playable, but there are still some major flaws with the signals and ATC/ACSES.
Apart from the "bicycle style" speed limits on the exit from Penn via its tunnels, one of the most annoying thing to me is the following (only happens in that particular point and travel direction): after Newark Penn in the direction of Secaucus Junction, the sign indicates 60 mph (Cab Speed). You arrive at a bridge over a river before entering Secaucus Junction and you have an unexpected and unwarned brake application. I have noticed that if you acknowledge after passing the 60 mph limit which is just before the bridge (when cab speed limit changes from 90 to 60) there is no brake application. I´m not sure if this is really correct, as the 60 mph limit has not long beep sound linked to it in ATC, which should be the one requiring you to press acknowledge button. There is simply a short beep. Does anyone know if this behaviour is correct at all? Cheers
Thanks Anthony. I supposed that, but this error has been there for so long and after several updates I started to have doubts. I hope it´s fixed. Cheers
Curious to know if any of these issues have been ironed out completely now there's more DLC in the pipeline for this route. Still getting a 30mph limit after NY Penn Station, not sure if that's supposed to happen but it makes it pretty hard to get to New Rochelle on schedule.
A couple have been fixed, but most haven't. 30MPH after NYP is not supposed to happen when the route ahead is completely clear. 60MPH is normal speed.
This post is literally insane with the amount of information. It’s very well written and very informative. Thank you for explaining!
Well I tried to play with ATC/ACSES turned on today, made me go 20 mph through the entire tunnel coming out of New York Penn towards the airport and put me 10 minutes behind schedule. I don't like to throw around the word "unplayable" but there's literally no way to play with the ATC turned on and still meet the schedule. Scenario ends with a bunch of big red Xs beside your arrival times, super super irritating.
Would appreciate if there's acknowledgment from DTG to at least to update us with the progress with where they at with it. That way there will be less people keep asking over and over and throw stuff at them with the way they work. Do make your customer understand the situation and whats holding up. This been happening before March 2018. Prove me wrong unless theres an official section to see the work in progress update for every one to see. Its a shame, NEC is awesome on how it works and features, but things like this holding us up
Corrected some grammatical mistakes. This information is still very relevant and I haven't heard of any additional fixes being planned for this route.
I've been in touch with them for years regarding this. It's something I'll continue to work on with them.
Not the 'same' as far as how it's presented to the engineer, but it's very very similar in terms of functionality.