Oh boy, do I have issues after playing the new DLCs for a few days... On one service with the Acela on NYT, I was cleared into a station with a Keystone service already in the station itself, even ACSES didn't stop me as I had an approach signal leading into the station (2159 Boston South Station - Washington) The texture baking on the Katy heritage unit is beyond horrible, almost all of the pre-existing decals are baked black on the model, which is absolutely unacceptable as even a blender beginner like me knows not to do that. There are also other details that are incorrect (the nose logo on the CNW unit reading "employee and northwestern owned", the SD70ACe text being red on the DRGW unit, etc) Some platforms along the route clip into rolling stock pretty majorly, as well as the wheels of the NJT rolling stock being embedded into the rails, both pretty major immersion-breakers On the Acela, just as you leave NYP, there's a random split second drop to 60MPH in ACSES which triggers an un-acknowledgeable overspeed warning. This happens on other non-Acela services too, but since they exit the tunnel below 60MPH it doesn't effect much unless if your very close to the limit. The ditchlight switches on the ALP-46, Acela, and Amtrak cab car are broken as well. In the Acela and ALP-46, "Auto" doesn't turn on the ditchlights with the headlights, and won't flash when the bell is rung. In the ALP-46, if the ditchlight switch is on Auto and the bell is rung, the ditchlights turn on steady but don't flash and turn off like they would have been flashing.In the Amtrak cab car, the ditchlights dont turn on at all, and only turn on to flash with the bell/horn. It's rather dissapointing that the full engine room is very clearly modeled on the Acela, but for no good reason at all it's just blocked off. It would be fun to have access to the coaches via walking through the engine. The OHLE outside of New York Penn on the Sunnyside Yard side is completely missing The tunnel just after said missing OHLE has completely broken light baking
So because its timecost there will be no update timetable or any major fix. Usual cashgrab and usual unfinished route. Sorry but less than 250 services on this route is such a shame. Again a total miss of what this route should have be immersion wise. TSW may have an excellent feeling when timetables are properly done, but no, not here. LIRR is despised because its a ghost of a route, this one has 2 time that much services, still so few... I suppose that upperstaff is happy and sellings are good enough to move along despite mixed reviews. I wanted Acela at least but no, i will spend my money elsewhere. Really disappointed (a common feeling with last DLCs...)
Now I am aware that tunnel lighting has never been a strength of TSW, but what the hell is this? How is this an improvement over what we had before?
I wonder how many weeks it took to implement all those ai layers passing outside St Pancreas in the SEHS....Someone posted MANY "Easter eggs" of ai outside that station including ICE train inside that station...And of course the high standard set of London Commuter um 1,400+ playable services???and then beyond regarding ai layers...or the branch added in the post patch of the Dresden-Riesa. And I'm thinking bout getting the Acela to try for Boston Sprinter, but even after the update, many ppl reporting many different bugs and issues on there too..
I'm just waching cActUsjUiCes stream, and man... that's rough. The amount of signaling issues he experienced just in two services... its mind boggling. It's like DTG haven't learning anything from their previous US passenger releases... I can live with some weirdness here and there, some lighting issues, and even the subpar timetable... but bugged signaling system, that makes you crawl for miles, or randomly drops your speed, applying overspeed penalty, makes the route unplayable for me.
Just a small glitch compared to other bugs but the new route is not shown in the in-game filter of USA. It is categorized in "Other". Should be a quick fix but would appreciate if this is corrected.
I don't know if someone mentioned this already but the Acela coaches are so silent even when they passing by at 150 mph. Needs some noise
That's pretty weird, here is my screen shot: I think it might have something to do with your graphic setting. I've never seen the light behave like that even before the update, and I've played around 50 MBTA services. I am running on High preset with shadow turned to Ultra. On a side note, I did play Red dead redemption 2 on a terrible PC before and that graphic finally let me changed my gear lol.
I just tried the scenario again. No speed penalties I lost 6 points for stopping accuracy and 50 points for leaving back bay a minute late. My score was 9683 gold is 10000. It’s extremely hard to leave back bay on time east to get to rt 128 and providence on time. This is definitely an impossible gold.
I don’t think this is worth the money unfortunately. This will be the last dlc I pick up. tons of pop in still in a 2023 next gen title on the most powerful console money can buy. Washed out colours Stuttering And driving the Ascela, it was just boring. Hardly any trains about, not many passengers (New York) turned it off and put something else on. DTG Alex these guys, myself, we are paying premium prices here, we are your customers and the lifeblood for your product. You guys have to do better. Your bosses need to do better. Do fewer more quality releases otherwise you are going to lose these customers in the long run. please listen.
All they care about is getting your money, buying it and complaining is the same as buying it and saying nothing. A few patches and then silence. If you really want change you have to get some ability not to buy the first thing offered hoping it will be different. I have done this for a while now, its quite liberating actually, but sadly without more people the message just doesn't get through. This isn't good enough.
On the Acela express, when you want to accelerate while the cruise control is on, you no longer have control over how much power is applied. Regardless of the position of the throttle, full power is applied while cruise control is set higher than the current speed. This makes it very difficult to control the Acela and causes massive wheel slip issues. Here is a quick video to demonstrate the issue: Strangely enough, if you want to slow down by setting the cruise control to a lower speed, you can use the throttle lever to control exactly how much dynamic brakes are applied. So you do have control over deceleration, but not over acceleration.
Alright, first off, I apologize to everyone in advance for such a long post. I took the time to take captures of the issues I experienced, as well as some new ones I discovered. All of these were captured on Xbox Series X NJT Cab Car Texture Glitch Inside Cab - I noticed that the textures for writing inside the cab of the control car glitch out. The issue worsens as you move. This is similar to the behavior of the Class 377 from London Commuter. ACS64 Extra Brake Percentages - The auto brake on the ACS64 goes from Release to 0%-100% to Suppression to 0%-100% to Full Service. The braking should just be Release, 0%-100%, Suppression, Full Service AI NJT Train Operating with Pantograph Down - I've spotted multiple NJT trains running with both pantos down... must be the new battery units? Amfleet Doors Too Loud - The Amfleet doors opening and closing are dramatically loud and lack the warning chime when closing. Below is my capture from Penn Station in game, along with a YouTube link showing an actual Amfleet closing the door, recorded by YouTuber 233CFH. Actual Amfleet - https://youtube.com/shorts/Cujk9zrIyrI?feature=share Acela Trainsets Configured Incorrectly (Both Boston and New York DLC) - Acela sets are configured so First Class is always on the south (Washington) end of the train. The consists are reversed for both Boston and NY - Trenton DLCs. ACELA SEATING by R3DWolf91 posted Feb 23, 2023 at 8:23 PM NY - WRONG ACELA CONFIG (2) by R3DWolf91 posted Feb 23, 2023 at 8:31 PM NY - WRONG ACELA CONFIG (1) by R3DWolf91 posted Feb 23, 2023 at 8:31 PM BOSTON - WRONG ACELA CONFIG (2) by R3DWolf91 posted Feb 23, 2023 at 8:29 PM BOSTON - WRONG ACELA CONFIG (1) by R3DWolf91 posted Feb 23, 2023 at 8:26 PM ASES Tutorial Typo - The ASES Tutorial describes it incorrectly as "ACES" ASES TYPO by R3DWolf91 posted Feb 23, 2023 at 8:25 PM Incorrect ACS64 History - In the ACS64 Tutorial the instructor incorrectly notes that the ACS replaced "electromotive diesels". In reality, the ACS64 replaced EMD (Electromotive Division) AEM-7 electrics, as well as the HHP-8 units. INCORRECT ACS HISTORY by R3DWolf91 posted Feb 23, 2023 at 8:29 PM Incorrect NJT Braking Info During ASES Tutorial - The ASES tutorial instructs you to apply into suppression when getting flagged for a speed reduction. NJT units do not possess a suppression state on their braking systems. INCORRECT NJT BRAKE INFO by R3DWolf91 posted Feb 23, 2023 at 8:30 PM No LIRR Services, But... - I don't understand the lack of LIRR services, especially for AI trains. An M7 is present at Penn Station, and the "placeable" route map even lists West Side Yard and Long Island City, both of which are LIRR facilities. LIRR TRAIN IN PENN DURING INTRO by R3DWolf91 posted Feb 23, 2023 at 9:02 PM LIRR YARD ON MAP by R3DWolf91 posted Feb 23, 2023 at 9:03 PM Wrong Info for Amtrak Cab Car - DTG has completely neglected to fully research the Amtrak Cab Car. For starters, it is not an "Amfleet Cab Car", it is an ex-Metroliner Cab Car and should be renamed as such. In addition the tutorial unit states that Amfleets were designed as EMUs... they were not. They were derived from the Metroliner design. I've attached excerpts from the excellent book "The Metroliners" by Bruce Goldberg and David Warner to support this evidence. INCORRECT CAB CAR NAME by R3DWolf91 posted Feb 23, 2023 at 8:30 PM INCORRECT CAB CAR HISTORY by R3DWolf91 posted Feb 23, 2023 at 8:29 PM METROLINER BOOK by R3DWolf91 posted Feb 23, 2023 at 8:30 PM AMFLEET INFO - 1 by R3DWolf91 posted Feb 23, 2023 at 8:24 PM AMFLEET INFO - 2 by R3DWolf91 posted Feb 23, 2023 at 8:24 PM CAB CAR INFO by R3DWolf91 posted Feb 23, 2023 at 8:29 PM And to prove that I'm not just some nut Googling information, I genuinely have a library that I've read/am reading that I research from... LIBRARY (2) by R3DWolf91 posted Feb 23, 2023 at 8:30 PM LIBRARY (1) by R3DWolf91 posted Feb 23, 2023 at 8:30 PM DTG, there are some mistakes here that are both simple and complicated in nature, but most of which could have been avoided with some research and better testing. I'm not going to scream and shout that you've lost my business, I want my money back, etc., but I do want it to be known that I have higher expectations of DTG than what was just released and I find these issues disappointing when the DLC was promoted so proudly. I truly hope that my grievances and those of others noted here are actually all being read and reviewed as promised, and I invite DTG to contact me privately if there is anything I can personally do to help make corrections on this newly released DLC (as well as to avoid any future mistakes in further North American content).
Noticed a strange bug with the ACS-64 today, not major but an annoying one. It happens in different ways on both versions of the ACS-64. Trenton ACS-64: when used on either route (Boston or Trenton) there is a yellow “doors open” warning light on the display screen as soon as you spawn, it stays on all the time whether your doors are open or not. Boston ACS-64: similar issue but different, ON TRENTON: it says “doors closed” when you spawn. Then when you open the doors it stays at “doors closed”. Then when you close the doors again it says “doors open”. And from that point on it is opposite of what is actually happening (says doors open when they are closed, and says doors closed when they are open). ON BOSTON: it says doors closed all the time. Amtrak 50th/TSW2 livery: behaves same as the Boston regular one.
Leading up to the release of NYC-Trenton, I was under the impression that the ATC and fixed signals were finally in a good state. But besides the almost ubiquitous non conformity between the fixed signals and the cab signals, there are many progressions that just don't make sense to me when I compare with the actual NORAC rules. Just as some examples: Approaching Trenton on the right most track (track 4 I think), the fixed signal at the end of the platform is at stop. The signal progression leading up to it: (ATC) Cab Speed 80 -> (ATC) Approach Medium 45 -> (fixed) Clear & (ATC) Approach Medium 45 -> (ATC) Approach 30 -> (fixed) Approach Medium & (ATC) Restricting 20 -> (fixed) Stop Aside from the non conformity going on everywhere, I can at least sort of follow the logic from the ATC progression, but the fixed signals progression makes no sense to me at all. For instance, shouldn't the last fixed signal before the stop signal be Approach instead of Approach Medium? Approach Medium doesn't suggest the next will be stop. Another strange one I encountered is when you leave Rahway heading for Trenton from the rightmost track (I can't remember which track number that is). You have to join the other 4 tracks just after Rahway and for that purpose the signal at the interlocking is at Medium Clear and the signal at the end of the platform at Rahway is Approach Medium. So far so good, but the progression you get in between is (fixed) Approach Medium & (ATC) Approach Medium 45 -> (ATC) Approach 30 -> (ATC) Restricting 20 -> (fixed) Medium Clear & (ATC) Approach 30 Why does ATC drop down to Restricting? Should it not just stay at Approach for the upcoming fixed Medium Clear? So I don't have access to information about the actual progressions in place, but I can't imagine it is anything like this. I've been rather disappointed so far in the signals on this route. Also about the thing some people have already mentioned on this thread about ASES giving a seemingly unprovoked emergency brake application after which you can't reset the system, even not by turning everything off and on again, I captured it on video: I turned safety systems off and continued driving and it seems that the system fixed itself when I got an ATC update.
I've said it for a while. They need to stop making new content and fix the tons of DLC's we already have. But, that can't and won't happen because that affects profits. Putting out lackluster, average DLC's upsets the consumer. But, if the consumer keeps purchasing it, should the company care if its quality? People are going to buy it regardless. Peninsula Corridor and Oakville Subdivision have apparently been being fixed for 2 years now.
Well, that was allways a thing that confuses, but is acually correct from what I found out! The first "suppresssion" is the suppression mode to reset the ATC braking panetly - this has nothing to do with the brake suppression. That's the second suppression before full service. I think the only issue here is the UI labeling of the states and that the 0%-100% starts again in the UI. The technical backround however is correct.
I totally agree here. From what I have seen so far, the conformity between wayside signal and cab signal is wrong more times than it is right. Some of the new users not as familiar with this route and NORAC rules might think this is normal behavior, but this is completely bugged. I was pretty much pleading DTG to consider this exact point when it was announced there’d be a new North American electrified route, but it seems my feedback was mostly ignored: https://forums.dovetailgames.com/th...tem-feedback-for-usa-route.61329/#post-562321 And yes, some of the wayside signal progressions on their own seem nonsensical and bugged as well. Rule 562 / HDIS signaling should only be in place in two areas of the route: 1) Ham and County interlockings (Trenton and New Brunswick) 2) Rea and A interlockings (Harrison and NY Penn) Those are are only places where you may credibly see a gap in the normal wayside signal progression like Approach Limited or Cab Speed followed directly by a Stop Signal as the cab signals can step you down between the fixed wayside signals. However, outside that territory, you you should never see anything other than Approach/Medium Approach/Slow Approach/Restricting before a Stop signal. The example you mentioned approaching a stop signal at Trenton is an example of this being bugged because once you pass into Ham interlocking and Fair Interlocking, you are out of 562 territory and a stop signal must not be proceeded by a wayside signal indication like approach medium or approach limited as those are improper progressions for that area. This is one of the aspects of the route (besides the timetable) that I would gladly try to fix myself if I was given access to the dev tools, but alas they are not available to regular users like us. It just frustrates me to no end that it was released this way and there are no visible indications that they are going to fix this.
Interior lights not working or destination not displayed. It's fatal when something that should be there isn't.
So when you get an ATC reduction to a speed below your current speed, you get this overspeed indication in cab that stays on until you have slowed to a speed below the ATC limit. However, sometimes this indicator gets stuck in the on position. When this happens, I can just keep on driving, no penalty brake application or alarms that need to be acknowledged or anything, only the lit overspeed indicator. I'm not really sure how to reproduce this, but it seems to happen when you get an ATC reduction and very shortly afterwards an ATC improvement. I've experienced this in the ALP-46: And also in the Acela: If I remember correctly, this also sometimes happened in the M7 and M3 from Harlem line. Also some more signalling weirdness, the fixed signals around Sunnyside yard seem a bit bugged:
Driving Acela service #2158 northbound, there's a MBTA train ahead of you as you leave Providence. I assume that in the real-life timetable your Acela overtakes the MBTA train at Attleboro or thereabouts, but instead the MBTA train is given priority and you're stuck behind it most of the way to Boston. Makes for an extremely frustrating run - this is exactly the reason that some of us are clamouring for real stopping times to be used instead of AI (which may hold the MBTA train at Attleboro to ensure the correct overtaking occurs). Either that or the 'dispatch beyond' instruction for the MBTA train at Attleboro should be unticked. In any case, it's pretty clearly not working as planned.
I am probably missing something but I cannot find a way to cross to a different platform at Newark Penn without going on the tracks. Is this correct? (moving this here so it's in one thread)
This seems to be an exact replica of how it was in TSW1, including the platforms you can't climb from end to end. More recent routes have added more ways to move through stations.
Access an ATC Not going down after resuming from a Save Gameplay. Basically Access or ATC Not working after resuming from save cActUsjUiCe Can you please look into this when you have the time, thanks
Feedback and bugs are splintering off into different threads again but here is a very important one for the team to look at regarding the behaviour of the ACS-64 with safety systems and signals (and it not behaving the same between the two different versions of the loco): https://forums.dovetailgames.com/threads/regarding-the-trenton-acs-64.65386/
Floating passengers in Acela Cafe Car Doors Open & Suppression Cab Alerts Won't Disappear on ACS-64 (NYC-T) Overspeed & Suppression Cab Alerts Won't Disappear on Acela (NYC-T)
I totally agree with you there. I play a lot of my routes and having to install and uninstall is frustrating...
Possibly mentioned already. Acela on the Boston route aren’t set up to show the proper off route destination. Fine for the ones headed to Boston because that’s the terminus anyway. But the ones going the other direction show their destination as Providence at the station PIS and on train PIS. Should be Washington DC. Also when you get to Providence the station PIS says “terminates here” which is incorrect since the Acela would always continue. The other Amtrak trains (ACS-64) show the proper off route destinations. Also the Acelas on Trenton show the proper off route destinations. So the issue is mainly southbound Acela on Boston route.
Finally got home from vacation and had a chance to dive into Trenton. Started with a service mode run of NJT Train 3736 (Jersey Ave. to New York Penn during the evening rush). The good: Scenery, station modeling, everything (especially the newly constructed portions south of Newark Airport) looks AMAZING. I grew up in the New Brunswick area and I am incredibly familiar with every station on the line. My jaw dropped at the accuracy of things like the Edison parking lots, the Metropark staircases, the Elizabeth parking garage...it's all stunning. I think the lighting, including in the tunnels, is SUPERB. Give me that kind of tunnel lighting over the old kind ANY day. The trains that exist in the timetabled services all seem to be accurate, and they're where they're supposed to be at the right times. The not-so-good: Scenery on the recycled portion (from the original TSW 2020 route) looks drab by comparison. For what it's worth, I would have advised DTG to take the extra time to rework this portion to be on par with everything else. There were a few errors in my scheduled tasks on Train 3736, at least according to the public NJT timetables. I should have had a few more minutes to get to Secaucus, for example. The most important thing that I discovered: While most of the pathing of my train was accurate, there were a few places where the pathing was off from real-world practice, and I think this is impacting the ATC/signaling experience. As has been well-documented, there are certainly issues with the signal progressions, slowing you down too much, too soon, and even throwing some Restricting cab signals into the mix where they shouldn't be. I encountered all of that---it's especially bad in the tunnels approaching New York from NJ. But there are also signals that are behaving mostly appropriately but are guiding you towards paths that slow you down unnecessarily. Three examples from this run: Approaching Rahway, I was routed from track 1 to track A at the beginning of Union interlocking, and was slowed to 45 well in advance of the move. But in real life, Northeast Corridor trains would stay on track 1 until the crossover AT the Rahway station platform. This is a 30mph crossover, instead of a 45mph diverging move, but because you're slowing for the station stop anyway, it has much less impact on your timekeeping, and the signal progression can start later. 95% of eastbound NJT trains use Track 1 at Newark Penn, not Track A. Trains cross from 1 to, uh, "station" 1 at the last crossover before the platforms begin. Again, track speed here is 35mph, so the 30mph crossover isn't a big hit, but the ATC progression shouldn't start too far out. I was routed to Secaucus Junction Track A via a crossover from Track 1 just before the station platforms, then routed back to Track 1 immediately after. If I had just stayed on Track 1 for the station stop, I would have had clear signals all the way, instead of a progression dropping me to 45mph well in advance of the crossover. Generally speaking, NJT trains that stop on Track A would have been routed to it (the middle of the three track main) just after the Portal Bridge, and this wouldn't happen at all during the P.M. rush. So while it is certainly true that there are some ATC/signaling bugs to iron out, some updates to the paths trains take would also help both the realism and, presumably, the engineer's experience vis a vis signals and the signal progressions. DTG Alex and/or DTG JD, is there any way I can assist with helping to re-program some of the schedule and paths? Are there user-accessible files for an experienced player to make these kinds of changes?
I posted a number of issues in the Technical reports section of the forums, where I think this thread belongs. https://forums.dovetailgames.com/th...y-systems-not-restored-after-game-save.65444/ https://forums.dovetailgames.com/threads/boston-line-timetable-issue.65355/ https://forums.dovetailgames.com/threads/boston-line-floating-poster.65356/ I think you DTG people really should be more consistent in where to report bugs.
I have noticed a lack of run sounds in the cab of the F40PH. Earlier I wasn't getting any sounds at all, it was quieter than an electric loco, this was after freeroaming for a while then deciding to have a drive. This was the 8:21 Boston to Stoughton. When I restarted the service I got engine sounds but no run sounds in the cab.
Hello, tonight I drove the 17:43 ACS-64 departure from Trenton to NY Penn (listed as the 17:41 Miami - NY Silver Star). I arrived at Newark Penn at 18:12...it was scheduled for 18:26. I was taking my time driving. I ended the run at this point as I didn't want to hang out at Newark Penn for 14 minutes.
