Route Morristown Line New York & Hoboken - Dover - Feedback

Should the cab door on Arrow open at stations? It looks weird.

 

fan railer might be able to help answer this one

 

I don't know why the landscape artists at DTG can't figure out American road markings. They aren't hard! Yet they still, 9 years after Sand Patch, can't seem to get them right.



YELLOW lines separate opposite-moving lanes of traffic- down the middle. Either a double yellow in the center of single carriageways, or a single yellow on either side of the median in dual carriageways. ALL other lane markings are WHITE. Why is this so difficult to understand.?

 

many of us bug these early on and mentioned this. Hoping it can be fixed

 

Haven't played much on the route, but I'm guessing the highways and freeways are still lacking any big rig trucks amongst the moving vehicles?

 

DTG are equal opportunities when it comes to US freight.
Only fair that if we don't get any more by rail, the roads don't get any either.

 

Good Job Guys, I can see how this was missed, it's just so close to the trains

 

haha. that wasn't missed. we bug that a while ago

 

Found a bug with the multi-level coaches:

There is an invisible wall in roughly the middle of the cab car, and a prompt simply called 'barrier' (the prompt is quite small, on the floor in the middle of the aisle). Clicking on it makes the invisible wall go away. I tested this on free roam, I don't know if this happens on other game modes.



To reproduce, simply spawn a multi-level cab car in free roam and try to walk through it.

The non cab-car coaches spawn without the invisible wall - however the prompt still exists, and if you click on it the invisible wall will become solid.

As far as I can tell, this bug does not affect the multi-levels from New York - Trenton.


Edit: Did some extra testing; the prompt and collision seem to be for the end gangway bars, but have somehow got placed in the middle of the coach instead. Toggling the barrier prompt on the cab car causes the front gangway bar to move.

 

this should be fix in a future patch. had this issue on service mode too

 

A real problem for conductor mode...

 

they got sucked in by the greedy ALP45 fans

 

Running service 3513 Sunnyside Yard to NY Penn in the Arrow - it was raining in the tunnel approach to Penn. Not initially but about half way along.

 

Replayed the service without the yard move. Still got held at NBS for train 312 instead of getting the signal right away, but it did clear for me after 312 passed (unlike the first attempt).

There was an issue at Penn, though. Similar to a timetable problem I reported with the Trenton route, it seems like the funneling of trains at Swift can get out of order. When I got to Penn around 8:25 there was a standoff on track 7 between an inbound and an outbound train. After I finished the service I spawned back in at Penn on foot at 8:20, and the sequence of trains coming out of the tunnel was different...no standoff. Not sure how to recreate or document this further.

 

All non-active cab doors should open.

 

Don’t know if anyone’s said anything about this. But, during night runs, most of the OHLE for some reason has this orange hue lighting on it. Don’t know if this is an actual thing on the line but it’s kind of immersion breaking going from pitch black in the country side to random orange lighting..

 

So it's a bug when passengers are break in to my cab.

 

I am wondering about Service 1002 in Journey Mode, Series X. When you start the service in the cab car, the game wants you to put the ALP45 into electric mode. I thought trains to Hoboken ran diesel-only? Also, wouldn't you need to be changing here from electric TO diesel, since the train would have been running under catenary starting at Little Falls?

Also, during this service I stood up and flew right out of the cab car, forced to watch as my train continued on without me. It was rather disconcerting.

 

PS5. Sooo I updated the game (free advise: don't).
First service on the Arrow, could not get moving out of Hoboken, kept rolling backwards and accidently discovered the buffers (at least on track 13) don't exist and the train proceeds into the terminal
Then figured out the patch actually disabled the train fault notifications, so I turned them on and set the train faults to low. Got 4 pantograph drops and 1 fuse trip between Hoboken and Meadows
Also, now when you approach Meadows the announcement plays "the next station stop is [silence]. please watch the gap when exiting the train" (there shouldn't be any announcement here at all, it was correct pre-patch)
Whoever approved that patch, give them a promotion

Also
- Fixed an issue causing PIS to have low draw distance at close range. This probably applies to the station PIS but the multilevel coaches still have very low LOD distance for the cabcar PIS-nothing was fixed here.
- Added better lighting across Morristown so there are less areas of severe darkness. Didnt see any change. Hoboken as dark at night as it was pre-patch.

 

So I can confirm that the update has broken the Arrow III on PS5. Had the exact same problem that I can't get any traction out of Hoboken. Before the update there used to be two control plugs you inserted but now it only lets you put in one. Could that be an issue?

Edit: Just tried a service from Summit and there is no power at all even though the pantograph is up. Fortunately the downhill means you at least go forward but don't really fancy trying to get to Newark at 5mph!

 

I would suggest disabling the train faults. I had the panto go down 5 times from Hoboken before I got to mmc. You won’t get any notice. The control plug is now correct per irl so that’s not the issue

 

so what was the reset plug for? I saw it in the preview stream as sth that is inserted at the start, or was this incorrect?

 

The pantograph was up in each case but I'm just not getting any power, but it's possible the whole train is just in a permanent fault. So I will try with faults disabled and report back.

 

I’ll let fan railer explain it better

 

I know it wasn't in the patch notes but I checked the ALP's if they are still doing dynamic braking on truck 1 when coasting... they are. As per the explanation before, the correct real world behaviour is for one truck to brake and 1 truck to keep power (balancing eachother out) but the implementation of that is still wrong.

 

So I disabled train faults and everything was fine. I also hadn't realised that the default setting for faults had been changed so you didn't get a notification. So it looks like the patch has caused the train to go into some kind of permanent fault with traction if you have train faults enabled. At least I can keep doing Arrow runs for now. Thanks for your help!

 

The reset plug is ONLY to reset the control system should a fault occur, like traction motor fault or controller fault. You CANNOT have the pin in both the control plug and the reset plug at the same time, as there is A, only 1 pin on the controller handle, and B, the reset plug is basically the engineer's way of "have you tried to turn it off and on again". If the pin is inserted into the reset plug, the controller does not work, even if there were another pin in the control plug.

 

Train 6324 with the ALP45 says Dover to New York Penn even though it starts at Summit.

 

I know this isn’t the Morristown Line, but, I’ve discovered this morning that using the Morristown version of the ALP-46 on New York - Trenton will feature both suspension, On Board passenger announcements, and cab announcements through the whole route.
It took me by surprise when I heard the announcement system say “Newark Liberty International Airport” I don’t remember anything in patch notes saying that passenger announcements would work on this route?

 

The stations are in the announcement library.

 

Service 881.
AI 6437 decided to stands forever at Maplewood. I waited for a long time, but I got tired of it, since it was already 6 minutes late, and I deleted it.

I don't know where your clumsy hands have gotten to this time, but after the patch, the frame rate in the Chatham area dropped to 23-25. Before the patch, it was 70+.

 

I know I mentioned it on the stream.Yea that was a nice bonus.

 

Arrow service 481 has some deadlock towards east orange.

Also weird, in this run the train had a very annoying knocking sound, so i saved and reloaded, and the sound was gone.
Maybe the reload caused that offpath train, although i did that just before this situation

 

No. I don't use saves, and faced the same bug.

 

This one is already on jira.in the meantime to avoid issue spawn on foot 5 or 10 minutes prior at hoboken

 

The Train off path or the weird sound thingy?

 

TRAIN SIM WORLD FIX...oops i meant six..I want to buy this route but i'm not a beta tester.

 

I need to clarify about Chatham low FPS. It happens only at night(23-25). At day everything is perfect(70-75).

 

I can confirm this happened when I tried running 881 as well. The dispatcher incorrectly lets 6437 go first past Millburn Interlocking. If you let it go ahead like this without deleting, you will be delayed by ~14 mins by the time you reach Summit. Obviously, 881 should have had priority in this case.
This is the pileup that results from letting 6437 go first:


Also, I'm sure others have already noticed this, but with volumetric fog on, having any amount of headlights activated will make it impossible to see ahead of the train by a few yards. Not sure, how realistic this is, but being from the NJ area, I do not think we get this level of fog with any real frequency. There is fog, but not this thick...

 

PseudoStalker I just ran a night service Dover to NYP and, on my system, did not experience any fps decrease at Chatham.
This is my system:
Processor AMD Ryzen 9 7950X3D 16-Core Processor (4.20 GHz)
Installed RAM 64.0 GB (63.2 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Also running a NVidia 4090 video card.

 

Sharon E, I'm glad that you have so powerful PC. I don't have such one. Before the patch everything was fine, FPS drops starts after patch.

 

The traffic is also left-hand drive on Passaic Ave, the first bridge over a roadway that is encountered west of the junction with the Gladstone Branch.

 

PS5. I did a rush hour morning service from Dover to NY in ALP-46 and the frame rates average around 35 for the route before Newark. After Newark all the way to Penn, they drop to mid 20 and at Penn I get around 18. Is this normal performance for consoles??

Hoboken is no better. Around 17-19 fps at 4:30pm. On PS5! I deleted all the trains in Hoboken and the frames rates jumped to upper 30’s. Maybe all those alp45s are the cause for low frame rates?