I have a hard time with can't or will not__, you can see that with the one video where I spent 12 hours, if not more, to figure out it was a save game causing the Red Light Bug. And right now I'm not feeling well. Or I would have tried this.
I understand that it’s just that they had access to all the trains it seems copy paste to me and these are my local trains
so I just completed a run - and the 5 mph kinda helped, cos I didnt get a penalty application before stopping, HOWEVER, once I stopped I got beeps and my PCS opened for some reason, as if I got a penalty
That is odd, and did you try to acknowledge the beeps/alarm? Maybe caatusjuice can take a look at this, if he has the time. By the way, which run did you do? I will try the same run on my Xbox Series X
Just to clear things up, the signal system is separate from the train safety systems. The train interprets what the signal system sends to it and decides what to do (do nothing, enforce a penalty brake, etc). The only train setup stuff I'm ever involved in is getting the basic cab signaling to function. The safety systems are handled by others at DTG.
So, would that mean that entering the station at 5mph rather than 15 or higher before coming to a stop is how it is set up? And not getting a penalty brake at 5mph compared to 15.
I don't know all the programming behind it, but the train safety system is generating a "braking curve" of sorts. It's likely a function of distance to the signal and current speed. It makes sense that coming in at a slower speed allows you to get closer to the signal without violating that braking curve.
In any case, it is definitely programmed incorrectly. It's something we've been vocal about for years.
Then there is a much lower speed restriction, than what is displayed on the dash readout. I have also noticed that many times, the mini HUD speed indication does not match the speed indications on the acses and ATC.
yes I did, and I was going like 4 mph, then I got exactly at the stop marker, pressed acknowledge one more time and hit the brakes, and I stopped right at the marker, which is where PCS opened up for some reason lol... even tho I was going slow, stopped, and opened the doors so if I got this at that 4-5 mph speed, then it doesnt really matter... previous runs I would do like 10-15, got close to stop marker, and got this also... so as we see, it isnt a fault on cactus' side, but rather sth with the loco/safety stuff it seems... I mean, as long as it doesnt stop me from getting nicely on the marker, not a big deal, but still sth I am noticing havent tried if it behaves the same on Boston Providence HSP46 timetable, but on Boston Worcester I get this every single time, both in HSP46 and F40PH
Try going under 3 mph. The "Velocity Zero" light comes on then, and the systems usually have a 3 mph buffer.
I can't disagree with ya there, yet it is still something that has to get corrected, But, with DTG now putting more effort into getting TSW6 ready for launch and putting less effort into what is broken or just now working properly in TSW5, if we want to keep playing these routes, we either walk away or suck it up play. And as catusjuice said, this has been discussed for some time; it's almost like you're better off running without the safety systems. Either way, which service did you do this on? Now that would be a bit odd Yes? to have it set so low.
II just encountered the same issue with P520. As I have manual switches set to AI to change, would have thought that should have happened automatically. The root cause is P520 being routed on the left hand track as the outbound services are calling at the stations with just one platform, but seems something slipped with the timetable routing here. And not been fixed. Hoping I haven't gone too far down the adjacent line so I can reverse without a SPAD.
I mean I don't know if the real railway infrastructure is like this, but what sort of messed up operation has an unsecured (as in no ground frame release as we have in the UK) in the middle of a 79 MPH section of line on a busy commuter railway, leading onto a 10 MPH side track. Seems to be contrary to all health and safety design criteria. Anyhow the solution worked and I was (just) able to back out on to the main line and continue after changing the points. Even if it is like that in reality, for simulation purposes those points should be maintained in the normal position.
ok, so I can kinda confirm that the issue is with the locomotive HSP46... I have just completed a run on Boston Providence on the new free timetable, and I got my PCS open like a second before I actually stopped lol... and I was going super slow, so yeah, sth causes HSP46 to get its PCS open when STOP aspect is in the cab, no matter how slow you go (and I had no chance of overshooting the signal)
That shouldn't happen in real life. PCS opening is indicative of the safety system doing an emergency brake application, which the safety system shouldn't do. If the ACSES braking curve is violated, a full service brake application should immediately occur, which won't open the PCS.
well, as I understand it, the point of safety systems is to ensure the driver can stop in safe manner before a signal (in this case), so like, not going 30 mph shortly before buffer lets say lol... but when you already go like 20, and as you approach platform hit like 10, or even 5 mph, even if the STOP aspect is illuminated, it should let you stop precisely, because at that speed you can pretty much safely stop on the spot should you want to so... yeah, atm it is annoying, but at least I can make accurate stops all the same, so I can live with this (as long as it does this only at the very end of runs, it is a minor annoyance)... honestly, even with this, the fact that we got US diesels in this game with safety systems is awesome... as much as I love Metrolink and Caltrain routes, the total absence of safety systems and their enforcement (except alerter) always kinda bugs me (I would actually love to have the train force me to actually learn the proper signals )
Here are some illustrations showing how ACSES calculates braking curves. OBC = On-board Computer (the ACSES computer equipment in the locomotive) PSR = Permanent Speed Restriction Alert Curve = the speed the engineer must follow when approaching a speed restriction (speed limit +3mph) Braking Curve = if violated, an immediate full service penalty brake applies (speed limit +6mph) When approaching a Stop signal at an interlocking, the system is designed to enforce 0mph at a distance 100 feet from the signal. This distance is reduced to 6.6 feet when the Stop signal is in close proximity to a platform. Oh, and almost none of this works as intended in TSW.
PS5 I want to ask if there is a way to set the CTC-3 so that when opening the door, the "cabin" door remains closed? The CTC-5 does not open, but the CTC-3 does.....
Same behavior on PC (Steam) Not sure if there's a way to set it. Might be a scripting thing. It's specific to the CTC-3 from the Worcester DLC as the one from the Providence DLC keeps the cab door closed.
I tried to select CTC-3 from the Boston-Providence on Worcester Line, although the cabin doors remained closed, only the doors of the first two cars opened, sometimes three. So it somehow didn't work at all again.......
From what I've observed, the game often mixes Worcester and Providence BTC-3 coaches into the same consists rather than keeping them separate. If you're using the Providence F40 or CTC-3 cab, any Worcester BTC-3 coaches that get mixes in (against your will) won't work properly. It's not just the doors, but also the interior lights that don't work correctly. They are not compatible with each other from a coding perspective, it seems. Something similar was brought up on the Providence HSP46 feedback thread as that behavior was observed on the Providence route since the HSP46 expansion was released. The only workaround seems to be to strictly use the Worcester F40/HSP/CTC units, regardless of whether you're on the Worcester or Providence routes, at least for those who own both the Providence and Worcester DLCs. Not sure if folks who only own the Providence DLC have experienced the same behavior. Yay, bugs...
This is exactly it I think. It was an issue even before the HSP add on, just with the MBB cars from Worcester, they would spawn in on Providence with broken doors. I only connected the dots because when Worcester first came out the MBBs from that add on had the wrong fleet numbers so you could tell they came from that DLC and not Providence. The way TSW DLC all seems to be glued together with chewing gum and popsicle sticks sometimes it must be a total disaster to beta test this stuff, some bugs only happen with a certain combination of DLC. It's all so tiring.
To help me figure this out, how can I get the Boston - Worcester line to only have rolling stock from Worcester in the train? By selecting the driver vehicle from DLC Worcester or is the solution to remove Boston - Providence? That would then remove the Amtrak trains in Boston South from service
There's no way to do it without uninstalling the Providence DLC. Which like you mentioned will remove all the AI Amtrak I think. At least you don't have to worry about AI Acelas disappearing, since they've been bugged since launch and never appear anyway, lol.
Im in the acela going towards boston south and the one next to me is going in reverse to Providence. Now thats not at all is it.
PS5 I removed the Boston - Providence map ...... on the AI train we noticed that the front doors of neither the CTC-3 nor the CTC-5 open, that's fine ...... but when I drive the CTC-3, unfortunately the front doors are on both sides at the station and on the CTC-5 only on the left, i.e. not on the right side of the driver, so at least two of them make some real sense ... these are the results
