Modders actually care, lol. Like sure, this route has some good aspects, but it is also full of issues and is very unpolished. Scenery is straight out not finished at places, like the platform end at Canton Junction, which is obvious as hell, yet it has never been fixed. The ToD update also completely broke the already bad lighting at Boston South and other covered areas. Timetable still has issues where Acelas get held up behind commuter services. Stopping points are also all over the place, despite the physical stop markers being mostly okay at most places where they are present. Thankfully the Worcester line is more well made. If this route got some scenery and timetable fixes, it would be pretty close to it as well.
Nope. All trains have 5 passenger cars. This means that on some platforms you have to stop at sign 4, on some at sign 6, on some it doesn't matter at all which sign you stop at, none of the doors will fit on the high platform anyway. There are a few platforms where the sign is actually in the right place, but some platforms don't have stop signs at all. Also, if I'm not mistaken, there are about 2 engine stop signs on the entire route (Route 128). One of which is just for Amtrak? So it's a DTG of the TSW 2 era in all its glory.
I did a few runs in the past few days and they were correct on suprisingly more stations than I expected them to be. Of course the in-game stopping points (the blue marker thingy) are incorrect for most, they are all over the place. But all of the stop markers are missing for the locomotives when going south. And of course there are stations where the cab car stop markers are incorrect as well. Worst offender is Back Bay where they are even the wrong way around, lol. I wish they would fix them to be properly positioned like on the Worcester line. Trackside signage being incorrect in a TRAIN SIMULATOR is quite a sin.
South Attleboro and Mansfiled. I don't remember exactly which is which, but at one of these stations the correct stop is at sign 4, and at the other at sign 6. And I don't use interface markers, I always stop at physical signs where possible. Isn't the black sign with the white E are the engine stop marker? Or is that for Amtrak?
No, I mean the "1" marker after the high level ramps - so you know where to stop with your locomotive for the coach doors to align with the ramp - like the ones we have on the Worcester line. I assume they should be there on the Providence line as well?
Because in the days of TSW2 there were no stops beyond the platforms. I am also glad that DTG solved this problem. On LIRR 2.0 there were just poles(which is already great for me), and on Worcester even the stop marker in the interface indicates the correct spot.
Just a basic question: is it accurate that the brakes on the F40 make virtually no hissing air sound when they are engaged? The only time they really make a noise is after they have been fully released.
I am getting no ATCS/ACSES functionality in the CTC-3 cab car. The box turns on, and it beeps at changes, but the readouts are permanently stuck on 10 and 0, and I get no penalty for overspeed. Is this a bug? Is anyone else having this problem?
Known bug. Reported. Nothing happens. Typical. You can force it to update by changing the view. Just press 1 key and it will lock on the current speed.
The problem with Boston Sprinter that you need the Boston Commuter to play it normally. Cause rolling stock from the old route is emh... bad. But since this is DTG, the substitution of rolling stock brings additional bugs in the form of not working doors. So...
All right, new(?) issue- does anyone else have a problem with the wipers in the ACS-64? For me, they cycle once in Intermittent then stop and don't move again; in Slow and Fast they do nothing at all. In a snowstorm I have to keep riding the switch just to see!
I have also noticed some weird graphics glitches with the lighting lately where the scenery may pop or turn black for a split second, most notably around the Boston South Station in the Boston to Providence route.
I have bell sound stuttering and disappearing when departure from South Station. Only at South Station and only on departure. Weird bug.
The signaling is *censored*. Left Providence following the Aсela. Aсela has already passed Attleboro, and I'm a couple miles from Providence still going on approach signal. It seems like the signals just don't want to update on time.