Route Morristown Line New York & Hoboken - Dover - Feedback

The Arrow III is going to take some getting used to with a Rail Driver.

 

Playstation 5.
Scenario: Back in the Quiver.
Arrow III.

The pathing takes you down an unelectrified track 0.7 miles from NJT Meadows Complex. Automatic junction.

Don't think I need to say why this is a problem. Fair to say, this scenario isn't completable.

You couldn't get 1 person in the office to play this scenario on a PS5 before launch? I understand small issues, but this is unacceptable.

 

Yes I took me a few services to get use to it

 

There’s is an open Jira ticket for this issue. Spoke to one of the beta members and mentioned that until this is fixed one way to complete the scenario is with enough speed to pass that bit into the complex yard before the end.I apologize for this. I hope this information is helpful

 

Yep, we tested it and reported it.

 

My theory has been confirmed once again. The problem is not the testers.

 

Yes, it does take some getting used to. I start with the scenarios and I'm running the Arrow III ones first.

The brake handle is straightforward enough, but the master controller is a bit jittery and finicky.

But after an hour's run into Summit Yard, I think I've got a " handle " on it. Even though it's still a bit jumpy, I'm able to control the speed of the train pretty well with the RD power handle..

Brandon did a good job with the signalling and I didn't get caught out by ATC/ACSES.

And the line was pretty busy with AI. One time I squeezed between two ALP45 DP's all at speed, pretty exciting. I think Joe did the timetable.

I think I'm going to be playing Morristown a lot.

 

Ah. I take my comment about testers back. It's just the dev team etc who won't delay to fix things.

 

Extremely loud pops and clicks throughout the entire game. It sounds as if someone is hitting a steel flagpole with an aluminum baseball bat.
Context: I play on a PS5 and listen in DTS 5.1 Surround Sound. I am not listening on headphones. I tried uploading audio/video from my PS5, but the files are too large, and I don't know how to compress them, without losing audio fidelity, which is the whole point.

 

They're aware of it. I get them on my headset and TV.

 

two little things I have picked up just checking with ALP45:
1) no announcement before first station (the one before Newark Broad Street, forgot the name)
2) no reminder to change power modes at Newark Broad Street (going to test this with ALP46 also)

 

The alp 46 doesn't have dual power

 

Summit Station - If you fall to the tracks, it is impossible to hop back to any of the platforms because they are all too high.

Pc/Steam.

 

Electric cabinet collectibles - After opening the cabinets, I usually need to try to touch the cabinet several times in different positions (come close, move away, come close, move away...) before the "you fixed the cabinet" event is triggered.

Pc / Steam

 

Drop the Equalizing res to 90 to get suppression braking.

 

If it's Meadows, that's correct because it's an employee stop only.

 

It needs to be optimized for RD. The throttle range is wayyyyy off.

 

ok my bad - the voltage change is at Kearney sth ... also, I tried a different service, one that has no stop until Newark (going from Hoboken), and it displayed the notification to change power mode...

 

oh ok thx for the info

 

also, whats Kearney connection? in the Live article it is mentioned that ALP services change the power there (or voltage?)... which station is it

 

ALP45s switch between diesel and electric at Newark Broad Street.

 

Known issue

 

ok, seems like the power change with ALP45 works, mostly and from I think the preview stream I have noticed that the voltage change with ALP46 happens when it diverges from NEC, and the display shows the change - will have to test it since during my service it showed 16 kV, when it should have shown 12 ans then 25... will check when I get back home (on my way to Vienna to check new tram lines 12 [operational] and 27 [will be operational in like 2-3 weeks]; also there should be a lot of new Vectrons around, so will check those)

 

It’s a junction that allowed NJ trains on the Morris and Essex lines to join the NEC to Penn station

 

I would like to say I am glad the Arrow III has flat wheels implemented on them. I've taken some clips of this and I applaud DTG for going the extra mile in adding flat wheels on some Arrow III cars. May I ask are they random or assigned to certain car numbers?

I wasn't sure whether this was a bug or intended game feature. But if those flat wheels are intended I hope this sets the standard to include trains realistically having flat wheels or bad wheels as not all trains are the same in terms of maintenance.

 

Trying to do some yard moves in the arrow but they are on the non electrified lines how the fudge do you move them.

 

Also all jobs and trains the tail lights are not you have switch them on at the other end thats a pain.

 

so at some point you see change in voltage on the screen in the cab? like some sort of automatic neutral section and then poof it's done?

 

Yes

 

we showed it on the preview stream.
https://www.youtube.com/live/-N89AzA9v5k?si=WCKIyrpDJvn6lYmg&t=10527

 

In Penn Station the automatic switches are glow-in-the-dark bright white, including the short section of moveable track that they are connected to. The overhead wires are also glow-in-the-dark bright white, as are the wires in the entire Hudson River tunnel. Series X.

Edit: forgot to mention that the glow-in-the-dark wires are present in the Bergen Tunnels as well.

On a separate note, I did except to see some static stock in what the game refers to as "Hudson Yard" and "Meadows Complex." Even NYT managed to have static stock at Hudson Yard. These yards would never be completely empty, and it wouldn't require anything more than the base layer. Now, if someone shows up and says, well we tried it but it didn't work, then it is what it is. But unless we hear something like this, then the lack of static stock and road traffic in specified areas will remain an issue.

 

So the safety systems definitely don't work the same between NYT and Morristown, even though it is the same equipment. The question becomes, which is right? I never thought it correct on NYT that you could move to service briefly and then quickly move to lap to silence the alarm. IRL this sort of process would most likely not stay under the braking curve. In Morristown you cannot acknowledge the alarm until you have been in service long enough to get under the braking curve, which I would guess is probably correct. It takes timing and also some route knowledge, because unlike with NYT if you just wait until the safety systems tell you to brake then you will probably end up over-braking to compensate. If you do get an emergency brake application, it can be cleared by moving the automatic brake into emergency and then releasing.

However, I have noticed in the Arrow that you do not have to go all the way to suppression in order to clear the alarm, so far I have found that about 80% works although I suspect that probably 66 or 67% is the true limit. I would have thought that suppression would be required to silence the alarm. In addition, when I do mess up with the Arrow, I am seeing a lot of the Overspeed icon on the HUD even after I think I have fixed the problem, and I am wondering why Overspeed is still showing. Am I still doing something wrong, or is it just an issue with the game/HUD? It's questions and issues like these that caused me to ask for at least one run in the preview stream run using the normal HUD with safety systems, but that wasn't done. Maybe we can have a short stream just showing the safety systems, what shows up on the actual loco screens and the HUD, and how to react. So we don't have people giving up, especially considering that the signals work great on this route.

I would also add that, wherever a discrepancy exists between NYT and Morristown, it is almost certainly NYT that is wrong.

 

NateDogg7a, Brandon redid the signals from NYP to Newark Penn when he did the Morristown line, so they are correct. He has not touched Newark Penn south.

 

In the Arrow III, I received a overspeed penalty brake, deserved. Stopped, got the brakes reset and was able to move away, but no matter what I did could not get the alarm to stop, so exited the run. Had to escape that sound.

 

The overspeed still showing is an issue that we have already ticketed in JIRA.

 

Indeed you are right, and it really shows! Not having phantom cab signal drops in the tunnel on approach to NY-Penn has been a revelation! I think andrews#9848 was referring to the cab signals and safety systems more than the wayside signals. What will be interesting to see is what the units from NYT do when they are running on Morristown, and vice versa. Unfortunately on console I can't really do this sort of testing just yet.

 

I posted it on internal Discord and got this response "
So the arrows are correct.
We have established that general suppression is satisfied around 50% brake app on the handle. The suppression notch is only used to recover from penalty brake applications. The overspeed still showing is an issue that we have already ticketed in JIRA.
He is also correct that NYT is usually wrong if you’re comparing behavior to MRT"

 

That's great info and very helpful, thanks!

 

holes in the ground leaving sunnyside yard to penn station. steam.

 

NYT is broken/wrong and has been since day 1. This is well established in the forum.

The bug with overspeed light sometimes staying stuck on is an ancient bug that (as is common) has never been fixed across multiple US routes. I remember having that happen in I think Metro North, LIRR and NYT at various times.

 

The MultiLevel door controls open low and open high buttons both do the same thing. The trapdoors/steps will only automatically open when scripted to do so at specific stations when in reality which set of open buttons are pushed should dictate weather the trapdoor opens or not. This is the same as NYT which I already pointed out back then.

Also new bug with these versions. The gangway barriers are no longer clickable and are visually in the raised position at the ends with collision disabled.

 

Bit of an interesting one - train #6667 from Penn Sta to Dover instantly derails when loading into the service through the timetable menu. On foot it spawns in fine but as soon as I take it over it derails and all hell breaks lose XD
On PC, Steam but this is most likely on all gaming platforms

 

Loving most of what I've seen and played so far. ACSES and signaling work as expected. A few PIS notes from the services I've done.

• There are several eastbound Dover-to-Penn services in the A.M. where the MultiLevel PIS screens all say "Train 6602," but the services are in fact 6606, 6610, 6612, etc.
• Millburn station is misspelled on platform PIS as "Milburn."
• Platform PIS seem to be omitting the first (next) station when they show a service's upcoming destinations. I.e., at Madison, my westbound service was listed on the platform PIS as stopping at "Morristown, Morris Plains, etc." with no mention of Convent.
• Audio announcements for NEC and NJCL services (playing at Penn Station and Secaucus) announce Newark Airport as "Newark Broad Street."

Apart from that, I would note that I have also experienced door faults on the Arrow III even with faults disabled in the game menu, and I second, or third, the request to get some traffic on the highways next to Brick Church and East Orange!

Oh...I brought this up numerous times when NYT was released and I continue to not understand: NJT's MultiLevel Cab Cars are numbered 7000-7061. Why does the railcar numbering in the game continue all the way through to 7199? It's hilariously nonsensical, particularly in light of the fact that we also only get the first batch of ALP-46 road numbers. For immersion and variety's sake, I would absolutely have done the opposite--include the ALP-46A numbers (all the way through 4664) and get rid of the bogus MultiLevel numbers. Ah, I'm sure someone will fix it in a mod, but it's just silly.

 

This has been filed with internal Jira system for the devs to look at

 

This has been filed with internal Jira system for the devs to look at

 

thank you for your feedback. I have filed all issues with our internal Jira system for the devs