NTTs and CBTC signals
Angel is correct. The subcontracts are not going to be their own trains. Since the R143/160 are similar, we are only building one model and calling it an R143/160 so people don't get confused and such. It will include all of the B Division route readings for normal lines (and a few GOs thrown in there); the R142 will just be that--it'll be a smoother and cleaner version than the one that's currently out by Alexander55. This will also have changeable destination signs for all normal lines and a few GOs. Where Magicland's R44/46 LCD signs only flipped between two destination readings, ours will flip through three destinations as such: [Trunk Line]/[Destination]/[2nd trunk line]. An example would be: "(2) 7 Av Exp//To Wakefield-241//Bronx Lcl". Of course the "2nd trunk line" changes with the direction of the train--trains heading to Brooklyn would reference the "Eastern Pkwy Lcl" instead of the "Bronx Lcl", naturally. I am currently working on the 142's destinations as we speak, and adding more destinations to the 160's, as Hurricane Sandy gave us some interesting routings.
Oh, and an aside about CBTC signaling and my decision not to implement it: In theory, I know what it does (it's similar to the way BART runs, except BART only has signals at interlockings), but from a Trainz standpoint it doesn't make much sense right now unless you're running 15 or so AI trains on a line. Coupled with the complexity of the subway outside of the (7) and (L), the heavy load a dozen AI trains would make on your hardware, PLUS the scripting complexities involved with trying to mimic CBTC as best as possible (computing distances, then trying to figure out what to do), it's highly unlikely that even a 50% accurate CBTC signal would be possible for Trainz.
-A :wave: