th Thats probably why the CR 8098 was nt part of the ns heritage pak since conrail still exists CASO its called
Do you have the freight layers on this route? I don't have them? I played the non reduced timetable......
I do have the freight layers, on Series S, with only SPG installed. This consists of one switching service, and some minor static stock. Non-reduced timetable only. As mentioned by trlz#8165 , it seems that HSC, CJP, and SHM and/or CC contribute stock as well, and seemingly the NS GP38 from HSC is available for use.
i think you have to have the Sand Patch DLC to get it it layers in some of the freight cars from other DLCs since i own all the u freight DLCs
i I saw cars and schemes from livery designer cn oakville bnsf box cars from cajon csx covered hopper s from sand patch an up hoppers from sherman hill cane creek
Yes that is strange. The only thing I can say is that I only very recently got TSW4. When I then installed NYT and SPG the freight layer was already there. Perhaps you were an early adopter, and if you uninstall/reinstall you will see the layer? No that doesn't make any sense but none of the rest of this does either.
Do we talk about scenarios only or also timetable mode? I have in the scenarios AI but not in timetable modus.... If you have it in both i'm not sure of DTG have upload the right version in the december update.....
it its a timetable only and just 1 service NE02 just switching in yards along side the mainline and just passenger ai trains passing by while your swtching cuts of cars
Interesting, I own SPG and I don't see that service at all in either the full or reduced timetable. Just an Xbox thing I guess? DW
I got an out of memory error on xbox series x last night when trying to access the full timetable. never had that happen in all the years Ive been playing.
I have Xbox X and I have SPG and I don't see it either. Must be some other freight requirement that activates it
This is definitely weird. The only US content I have installed on my Series S is NYT, SPG, and HAR. Like I said, I only very recently got TSW4, so perhaps that has something to do with it. In any case, I can attest that this freight layer doesn't add a huge amount, but it surely beats nothing.
I just played that timetable again it was in full timetable mode only first time ive tried full time table on my series S worked decent for when played it no crashes
I have sent a report to DTG about this issue and made a video with the bug being reproduced. They registered the bug report, so let's hope we'll see some fixes.
After one of the recent updates, speed limit scoring seems to be broken. I'm now being penalized for "driving significantly over the speed limit" when I get a cab signal drop. Anybody else?
Yes I have noticed this as well. Another thing is that the cab signals in the HUD on HAR have reverted to displaying the corresponding letter instead of "ATC," which was the original behaviour before the cab signal standardization that occurred before NYT was released. One might surmise that these changes are due to a recent update to prepare for LIRR. However, what the true cause is, whether or not DTG knows or cares about these secondary effects, and if the scoring would ever be fixed, is impossible to know.
Last time I remember layers on routes disappearing like this while all relevant routes were installed only to reappear when fewer routes were installed, was right after they released the cross-platform version of the DLC manager for TSW2.
Now that I am thinking about it, the last time I played HAR I might remember the "significant speeding" penalty for not confirming quickly enough to cab signals, regardless of civil speed limits. I will play again soon to verify. As for BPE, I haven't played it in so long I wouldn't know, simply because I have very few novel services left for that route.
Able to confirm that overspeeding penalties apply to cab signals on HAR as well, even if under track speed limit. The penalty assessment also seems unusually harsh because you will get the significant overspeeding notification even if just a few mph over the cab signal, and even if you move quickly to adjust your speed. Although this is an interesting development, I would say that it is probably not too significant because we are really only talking about score anyway, and these penalties are probably not enough to prevent a gold medal in any case. On a side note, I did not notice any excess shaking, so that seems to be good news.
The first service I played on NYT this week was a Jersey Ave. deadhead move and yes, the overspeeding penalties did prevent me from getting a gold. Is this as big a problem as the AI alerters? No. But this IS an example of the sort of thing that by itself wouldn't irk too badly but when you factor in all the ridiculous (and easily fixed) problems that NYT has had whilst we get patch after patch with fixes for the most mundane English route errata...it frustrates.
Series S. I also noticed that I have the cab sway option turned almost all the way down, so this might be the reason why the "shakiness" in HAR was not overly pronounced.
ok that makes sense. thank you for the info. we should be getting a patch soon for xbox. you can tell the difference between pc and xbox since PC did get the update.
Unfortunately, driving the Acela on NYT today I noticed that the HUD is displaying R, M, L and N instead of the ATC track speed. Of course these symbols only make sense on Metro North. The HUD display for the Acela and the Harlem Line have been tied together ever since ATC was "standardized" within TSW about a year ago, although since the cab signals are completely different between them this didn't make any sense then, and it doesn't now. This does however lend more support to the theory that background changes are taking place to support the eventual release of LIRR. Anyone who drives hudless probably wouldn't even notice.
[2024/03/08] Environment is PC Steam (Landscape) ・The station lights are on at night, but his platform is pitch black (mysterious phenomenon) feel ill
I’ve just played a ECS service on this route and could hear alerters going off when I was in NY Penn. Am I to believe that this still hasn’t been fixed? PS5.
Is still an ongoing issue, but what i can say is I don’t hear it as much as before. This last past week I did a few Trenton round trips and only hear it a few times from all the services I did. On some i got lucky enough not to hear it at all.Also no hitching and actually runs very smooth on Xbox x and PC steam.Around rush hour the amount of trains in and out of Penn station is very impressive
Oh, it's still omnipresent. It does seem to only affect trains that are NOT on the map when you launch into the sim, which means that if you do an eastbound run (starting at Trenton), you won't hear too much until you get towards Penn. But the cacophony sometimes in Penn is still ridiculous. While we're here...cab signals...
Nope and it seems to have gotten worse. It’s beyond hearing alerters of other trains inside the cab of your own, but now with ATC and ACSES turned off and even the alerter off as well, the beeping is louder and occurs more frequently. It’s coming from the consists I’m operating myself. I Wish there was at least a mod or setting to turn off alerter sounds altogether. If it’s not gonna get fixed, fine, at least let us shut it up so the route is at least somewhat playable
I don't think it's gotten worse, but it definitely hasn't improved either. I'd say it's about the same, at least on TSW4 for PC (Steam). I can usually silence the alerters on other trains with Free Cam (8) by poking in through the cab door or window if the train is stationary. Still very much a nuisance, but not enough to ruin the route for me (still very much enjoy it). After doing some more testing recently, it seems the issue is tied to resuming a saved game session, at least now. Originally it seemed to happen after I ran a session for a while, even without saving/exiting/resuming. The other day I tried running one long, continuous session without generating any saves whatsoever and I was able to bounce between services running back and forth between New York and Trenton without issues with the brakes. All applied/released normally and compressor kicked on to maintain main reservoir pressure of 120-140 psi on all trains, as it should. Exited the game and loaded a new session, this time making regular saves at various points, but still not exiting out to main menu. Again, no issues with the brakes even while generating saves, though still running a continuous session without exiting. Started to think maybe the issue got fixed even though I never saw anything about it in recent patch notes. However, upon exiting to main menu, resuming a save I had generated and started testing the brakes, boom, the bug revealed itself. The compressor would no longer kicked on and main reservoir pressure continued to drop until it eventually could no longer recharge the EQ and brake pipe. Tried switching to another train on an adject platform and same thing; brakes will obey apply/release commands, but the compressor will not kick on at all to recharge the system, eventually locking up the train. Tried doing the same tests on other routes like Antelope Valley and NEC: Boston - Providence to see if it's a bug with the Save Game feature itself, but no, brake compressor works fine on other routes after save game resume. Whatever the save game feature is breaking to cause the compressor to stop working on resume, it's specific to this route. On a related note, I noticed the main reservoir on the Amtrak ACS-64 loses pressure awfully fast, almost as if it has an actual leak, even with the brakes cut out. Seems to lose 1 psi roughly every 1-2 seconds, which seems abnormally fast for me. Causes the compressor to kick on VERY frequently. I don't recall it exhibiting that fast of pressure loss on the Boston route.
Did some more testing and no, it appears the "leak" is specific to the ACS-64 that comes with the route. The two carried over from the Boston route (standard Phase V and TSW2 wrap) maintain pressure rather well (they do lose some over time, but MUCH slower than the New York unit). I also now noticed the brake cylinder readout on the cab display of the New York ACS-64 does not match the readout on the HUD and actually bounces up and down a fair amount, so I'm wondering if it has something to do with the "leak".
I never understood why there were 2 different versions of the same loco on this route. Why not just absolve one of them cause I always get confused which is the NYT and which is the BS one. If the NYT one was updated and improved, why weren’t those improvements carried over to the BS version?
Can't answer the why, but FWIW the last time I (accidentally) chose the Boston version and ran on NYT, I got all kinds of crazy cab signal drops and errors (well beyond even the normal ). Unless (until? wink wink hope hope nudge nudge) we get signal updates, I wouldn't use that version on Trenton.
They are labeled though. There's 2 on Boston sprinter because one of them is a real life livery amtrak and dtg collaborated on to put on a real train for a bit. The issue with the trains is that they are their own entity so it would be a lot of work to then backport to an older model. It takes a full time employee and dev time. That's just how tsw is built
NJT cab car: do the dynamic brakes work? Or is there a switch toi set for them? Because the controller has a full range of braking positions, and the loco is basically a BR 101, but moving the controller into brake does nothing, and one is stuck with those meshugginah manually-lapped air brakes
