Overall the Cab Signalling on NEC Trenton seemes to be working fairly well, but after a couple of timetable runs I found a few inconsistencies. The main issue I just found running the 7:58AM Acela NY Penn to Trenton. A mile or so before Rahway I'm running on clear trackside signals at track speed and get an approach medium on the cab signals out of the blue, no preceding Cab 80. The next couple fixed signals show a "Clear" aspect but my cabs signals remain on Approach Medium 45 for no reason. After 2 or 3 miles eventually the cabs upgrade to Clear 125 again, but this causes me to be late in to Metropark. I noticed the same behavior during the preview stream on Monday a couple times, notably when Matt was driving the NJT cab car northbound he also got a random drop to 45 on the cab signals for a while while the fixed signals showed "Clear". Later approaching Metropark on the same trip I got the Approach Medium 45 on the cab signals BEFORE I actually reached the physical distant signal showing "Approach Limited" for the crossover to Metropark. I got slowed at what I was believe was the code change point prior to that distant signal. As I approached the actual distant signal I noticed there was no scenery object for the track transponders under it on my track. It seemed like the code change point associated with that physical signal was forgotten so ASES rightly dropped my cab signals to Approach Medium 45, but it was just too early since there was a missing code change point at the signal. I noticed a similar issue running a morning NJT Super Express in to Newark Penn. Cab drops were occurring one signal too early leading up the "Stop " after Newark, and I noticed no transponder scenery object on my track at the "Approach" distant signal just outside the Newark platforms. I started noticing missing transponder scenery objects at physical signals all over the route in various random places after that, but running on "Clear" signals it was impossible to tell if they were just missing scenery or actual missing code change points as far as the sim's signalling system is concerned. Fixing these issues would elevate running the route to top tier behind Boston in my opinion (ignoring the glaringly empty timetable).
