This is the master feedback thread for the Northeast Corridor: Boston - Providence Route Add-On. Support Information: NEC: Boston-Providence Gameplay Guide
Finally managed to complete the cold as ice scenario, however all the trains are still stuck at Boston South, nothing moves in or out for the 95% of the scenario. Also is the ATC/cab signalling suppose to have you on restricted for the whole journey back? I was being limited to a max of 45mph from Canton and wasn't sure if that was intended or not.
Generally a good product overall and enjoyable to play, but there’s room for improvement. As someone who’s from the Boston area, I would say that it does a decent job approximating the look and feel of the route, while not being overly accurate. Scenery improvements: Buildings at Route 128 and Attleboro could use more accurate substitutions (see Google Maps Streetview). The stretch approaching Providence next to I-95 is too dark. In real life this is a very busy highway and fairly well lit up at night. Rolling-stock: the stock included looks good, but it’s not a very accurate representation of what’s most commonly seen on the route. HSP-46 locos and bilevel Kawasaki and Hyundai Rotem cars are very common. Single level MBB only consists are seldom, if never seen. Also, would love to see static or AI MBTA Orange Line (subway) formations along the Southwest Corridor portion of the route. Enjoyable route overall and I recommend it to others, but some improvements and additions could enhance it quite a bit. Good bones, but a bit basic as it is now.
It's one of my favourite routes, but I would love more MBTA stock. I'd buy the HSP-46 with some bilevel cars in an instant.
One thing I forgot: the sunken cars at Stoughton need to be fixed. Not a big problem of course, but it is sloppy and detracts from the experience.
Has anyone noticed a portion of missing track on this route? I can't remember where, but it is there. It's a very short piece...I do not have access to the game at this time to show or verify where. I do believe it's on the long stretch of Northeast Corridor, from Attleboro--Mansfield section.
Indeed. It feels like something 85% complete. Fun and enjoyable for a video game, but could go further. A little more work could bring it to a higher level of detail/accuracy and increase the immersion. It has good bones, why stop just short? A bit more care with the scenery, some additions and just some more quality control.
With a fix finally released for TSW3 as well, I can confirm. The scenario can be completed now, but trains are stuck all over Boston South, all of them waiting at signals that never change. I assume their fix was simply deleting that one single trains that blocks your path, lol... But the whole scenario is horrible to begin with. It is a simple run to Stoughton and back, in snow. I could do that in timetable mode as well, and I would have even more traffic around me at least. I assume the scenario tries to simulate a traffic jam due to all the snow, by... placing a single train in front of you that goes incredibly slow on purpose. But no other traffic around you, so you just drive at 20 MPH for an hour on empty tracks.
Has anyone else noticed an issue with the ADU in the CTC-3 cab cars? it's not updating without resetting the camera view, it just kinda sits there displaying whatever was displayed last time I switched to the first person camera, it doesn't visually update current speed, speed limit, speed restrictions, etc. But the sounds and functionality of ATC and ACSES are fine
I have the same issue, the safety system displays only update after view change... Which makes the CTC-3 cab pretty much unplayable. I've tried verifying steam files, removing all mods, and engine.ini modification, but nothing helped.
I wonder what core change ended up breaking this. I haven't tested it myself since I am busy with another project, but can someone post a video of the phenomenon? I can forward it to the team.
It's still an issue in Timetable mode. Everything starts fine, but after a short time, trains will begin to stack up on infinite red signals, unable to move. Last night I tried running the MBTA #915 (Boston - Stoughton, 16:18) with plans to continue after completion in free mode to the #916 return trip. No issues at the beginning. Trains were moving in and out of Boston. Made it all the way to Stoughton without any red lights, completing the service successfully. Went back to free mode and prepared to turn the train around for the returning 916 service. Checked the map [9] and... Trains at Boston had completely stopped and backed up on the signals, with one of them blocking the points to the East platforms. This was on TSW4 - PC/Steam. I also have the Acela add-on, if that makes a difference...
I agree and I even know what needs to be added to this route. For example, you would need to add the Pawtucket/Central Falls station, which is located between the Pawtucket depot and the South Attleboro station, and check the MBTA train schedule accordingly, due to the stop at the Pawtucket/Central Falls station.
That is, this route was and will be as of 2019 and there will never be any changes to the schedule? I understand correctly?
each dlc is set during a specific era. You could have a different separate timetable which a few routes have (rapid transit, bakerloo) but you couldn't have pawtucket unless you rebuild the line when that existed and other changes that existed
Exactly. And then you'd have to modernize every aspect of the route, to include the opening of Ruggles track 2 platform. All of this would then require a new timetable, too. It's a lot of work for very minimal gain in terms of gameplay.
I think I know what might be causing the traffic jam (at least the one I noticed the other day). Seems to be a similar issue that was brought up for the Metrolink Antelope Valley route. Started off at 16:15, shortly before MBTA #915 leaves (train I controlled last time). Stood at the end of the platforms watching trains come and go. All was well, traffic kept moving smoothly. Between 16:15 and 16:55, two trains stack up on the Greenbush/Kingston/Middleborough line (Southeast past the yard) at the signals just south of the wye. At around 16:55, after an outbound MBTA train clears the switches, the first train in the stack begins to move and is lined onto track 11. Looks to become the outbound 17:12 Middleborough, based on the platform display board. It pulls into the platform with no issues. Once it clears the switches, they re-align for track 12 and the train that was stacked behind it starts making its way while a third train that had joined the line moves up and holds at the signal. However, just as the lead bogie of the cab car runs over the switch for tracks 12 and 13, it comes to a stop and refuses to move. It will not let me take control of the train so I can clear it manually either. Over the course of the next half hour, trains will slowly begin to stack up behind it at the lights. Eventually, even outbound trains are unable to move, grinding the whole station to a stop. One thing I noticed, though, is that the train may be coming to a stop because it's supposed to go to a different track other than 12 (maybe 13?). Seems to be somewhat similar to how on the Antelope Valley route, the 7:59 Metrolink train bound for CMF gets stuck at a switch that's not aligned correctly for it and ends up causing a traffic jam, per this post. I am able to remove the obstructing train in map view [9] without the game crashing or any other negative effects (at least during the time I observed). Once the obstructing train is cleared, the third train that was stacked moves up onto track 12, stops on the platform and unloads passengers normally. Not long after it, a fourth train enters the adjacent 13 track normally. From then on, traffic continues to move in and out of the station like normal. Not sure what the story is with the obstructing train. Maybe just got routed to the wrong track and got confused (similar to what has been observed on Antelope Valley) or does it even belong on the timetable (some weird, phantom train with no set destination)?
In my experience, it should work if you use the arrow keys to switch interior (cab) cameras and then return to the usual camera using the arrow keys, but it's still something that should be fixed.
When my train is late the one behind me does not wait as signals. Instead it stops about 5 metres away from me at every station.
That's just a limitation with how it's programmed in the game. I think in real life they are much further away. The ai don't follow the rules otherwise they would just be hogging performance
I would like to know when the ADU in the CTC-3 cab car will be fixed. It just can't go on like this that essential features are broken by DTG, the forum is flooded with bug reports, but these are completely ignored as if everything was fine and in order. I ask for an official statement, because I think we have waited long enough and many of us may be fed up with the eternal workarounds. DTG Alex
So now that the alerter sounds have been “fixed” (it’s not fixed btw) on NYT, the Acela alerter is blaring on Boston Sprinter
I have given up hope this issue will ever be sorted. Already waited a year for this “fix”. US content has always been and will always be an afterthought with dovetail.
Signaling is still broken. I've got approach signal incab 9(NINE!) miles from Route 128 because the train ahead just stop at the platform(Route 128). I can't believe it's something about realism. With such a realism all trains on NEC would run 30 mph all the time IRL. Near Canton Junction there is a restrict signal incab, despite the fact that there are 4 signals are yellow on the map ahead. Maybe it's too early, don't you think? Departing Route 128 I've got approach medium, despite the fact that the train ahead had already arrived at Boston South a year ago.
What service are you playing? This may be due to dispatch beyond instruction not being enabled on stops for that timetable service.
And what about trains to Stoughton? It's imposible to follow schedule with incab signaling ON. Because it's 45 most of the time with some "phantom" red at Hyde Park.
The timetable in game doesnt have great timings and the inaccurate physics of the rolling stock doesn't help either.
Well from the f40ph's perspective, the brakes release ridiculously slowly and the acceleration is too low. This makes on-time performance impossible
Well that’s refreshing to hear it confirmed by a dependable source what I’ve suspected all along. Now I won’t feel bad when I can never arrive on time doing an MBTA service. Thank you Cactusjuice!
CTC-3 ADU is still broken in TSW 5, when will you finally fix it? I wish you guys would be as fast at fixing things as you are at breaking essential things and then just disappear under the radar and keep silent about problems you created with your glorious or rather infamous patches as if they didn't exist. I expect a response, because I think it's been reported more than enough to get at least a tiny response.
Thanks for reminding me not to play this route again. The CTC-3 has been broken for how long now? It must be longer than a year, because it's broken in TSW3 as well. It's ridiculous.
Total confusion! #916, Stoughton-Boston 1) Derailment for no reason out of nowhere, about 2.2 miles this side of Canton. WTF? Completely game-breaking 2) Train has almost no power, cannot break 20 mph downhill! 3) ADU, yes, still broken. Tells me 10 mph continuously Is this service playable at all?
I just looked at #916 and ran the service with both the Boston Sprinter Cab Car (ingame name CTC-3 Cab Car) and the Boston - Worcester Cab Car (ingame name CTC-3 MBTA) and was able to complete the service successfully both times. There were no signs of danger of derailment, nor did I have any problems with the brakes. Acela DLC is installed Slightly modified engine.ini Some tiny mods, nothing big or special On the subject of derailment: Maybe it's due to a mod, even if it has no impact on said route, it happens more often that some mods cause problems of this kind on some routes. I have already been able to help quite a few people with this hint who could not find any connection and were therefore on the verge of despair. On the subject of brakes: Did you maybe forget to set the cut off valve to passenger? As I had no problems with the brakes, I can't think of any other cause, maybe it's due to a mod too.
Brakes were not an issue, problem was very limited power ________________________________________ All right- the mystery deepens. Tried it again, this time the train insta-derailed on start, three times in a row! But mind you, all of these were in Journey mode. Just tried it from the timetable (today's date, weather clear), and so far have had no problems at all- everything works normally except the bugged ATC display.
Hmm, I didn't read carefully enough, so I misinterpreted the phrase “cannot break 20 mph downhill”. I can confirm immediate derailing in Journey Mode, and have already found two potential reasons. However, the train derails randomly, out of 10 restarts it derailed 4 times. I will run #916 again in Journey mode and keep a close eye on the two possible reasons mentioned. 1. On the CTC-3, the front hoses connections are glitched into the concrete. 2. There is very little space underneath the brake linkage of the F40. At this point, the floor also consists of raised concrete in which the tracks are embedded. This could possibly be due to the hitbox being too large.
And, strangely, after I completed it successfully in timetable, I ran it again in journey and had no problems. Random glitch?
DTG, this is not how you behave in polite society. Dozens of flying objects(some are in a meter radius of a train). Trees without shadows(some form forest areas without shadows). Track monitor is glitching in Providence. Signaling in services to Stoughton is about sudden yellow and red(no chance to get on time while driving with the safety systems ON). Cars from Worcester route can't open their doors on this route platforms. Shading in tunnels are glitching generating completely white cab interior. Emergency auto brakes application at South Station platforms. AI train ahead can generate approach signals in 9 miles before it. Some platforms are fully empty(even no one is disembarking). Car/loco stop signs exist only on a couple platforms. And so on. Also how many more years will required to add shading underneath the Acela cars? There is no shadows from release!
Service 904. There is two fake red signals(Route 128 and Ruggles), which allows you to proceed. What schedule are we talking about if signaling is broken and we need to crawl at 20-30 MPH cause of bugs? Also Emergency brakes at Canton Junction platform before the stop marker because another red, you know. Plus emergency brakes at Boston South platform. Plus the game does not count disembark at Boston South - you can stand there forever and the task will never be counted(I turned off the safety systems and drove to the edge of the platform, only there it was counted!). Amazing piece of trash.
Will this route get mixed formations substitution from MBTA Commuter similarly to how Antelope Valley got it from San Bernadino? It would be nice to breathe some fresh life into the route.
Well, someone did it in the form of a this mod. It is really nice! Can finally have the HSP46 and the bilevels on the route. They really bring the route alive - more train variety and mixed consists driving around. Also the better ACSES implementation and the suspension physics are a great plus over the original Boston Sprinter stock. Interestingly enough, I also saw this AI service stopped at Forest Hills. Previously I have never seen any train here ever since this route released. Could it be some disabled service that somehow got enabled by the substitution? Or was this always present and somehow I just never encountered it before? And ultimately the obvious question once again - will DTG ever enable/fix the substition for this route so these mixed consist can work straight out of the box? Why do we need mods for this?
If money was the motivator, they would be more inclined to make it work. After all this gives you a reason to buy both routes if you don't have both yet. I'd say it's just the usual case of not caring enough and forgetting. After all, they fixed the substitution on Antilope Valley. Just not here.
Just because F59PHR. If they didn't release a new addon to this route, no one would even scratch their head. Also MP36 only appeared two updates after its substitution was announced. Also#2 Bombardier's aren't there despite the fact that they are declared. So the question needs to be formulated differently: "why do modders have more professionalism than professional studio?"
