X2635 and PRR Eastern Region

[ckawahara]

Does everyone's version of PRR ER end at Gallitzin? I ask because in trying to resolve my error, I generated another error, this new one apparently due to a broken path. It turns our that the versions at CLW and here are not the same version as the one I have. My version ends farther west of Gallitzin, in Pittsburgh Yard. This doesn't resolve my explore route error, but would explain the new broken path error.

[Vince]

RE:Eastern Region . . . before I start, Mike, can you call me? I lost your phone number Thks. v

Ok now to the PRR. . . .

OR X2637

I decided to take a break from building the LIRR so I figured something nice and relaxing like running the PRR NEC (which I never had dine!) was the thing to do . . . I d/l'd the route from the f/l here installed without a hitch, broke out Route_Riter and used the [CHECK ROUTE] test to correct several hundred misplaced sound sources.

It took several runs of RR to finally end up with a perfectly clean [CHECK ROUTE] test.
I didn't bother with the [ICHK] test as Mike had warned me about this years ago.

I have made many signal modifications between the Bergan Tunnels exit all the way to Philadelphia correcting signal links and incorrect usage of the "Use Advanced Approach" checkbox on distant signals.
This checkbox being checked caused many slowdowns to 45 mph for no apparent reasons with no reset to track speed possible for (in a few cases) many miles. I didn't even think of attempting to modify any track . . . modding the signals gave me enough MSTS crashing experiences to last me for quite some time. Just like the good 'ole days I tell 'ya.

Reasons: I wanted to generate an activity that would only run under OR.
Loose consists on every visible siding along the path from NY Penn to Washington and so far running 65 AI traffic trains over the two hour run.
See my post at Elvas Tower for some problems I had with that. (You must be logged in to view)

So the activity runs well.
So, Ladies and Gents, if you want activities to run as you designed then OR is the way to go. The AI traffic trains actually do what you want for a change. But there ARE differences between MSTS and OR and it does take time to become familiar with the wonderful set of new commands available,

I can have trains coupling and un-coupling and re-coupling to a different engine and then leaving on a run, something impossible to do with MSTS.

OR? Oh yeah, it's still a work-in-progress and bugs do surface from time to time but hey, it'd be boring otherwise.
I'm running a I5 Quad core 8Gig Ram and 2 SSHD's GTX650 video. This system is perfect for OR. Case in point: Sunnyside Yards, New York. . . I'd get 18-22 fps on my new system with MSTS. Open Rails . . . 50-70!! Some improvement no?

So is Open Rails the way to go? It certainly is fo me.
And for you prototypical freaks out there (I'm one of them) no more having to set your coupler break strength to 5.40E7N ( 12,139,683 pounds! )
Now you can set them to ACTUAL real world break force FRA Class E Shock Load of 500,000 pounds - 2.22E6N with no more worry about 'over length track node distances.

Sorry weenies, no more crashing trains thank the Lord!
Testing this activity I had accidently dragged a loose consist (PRR B5+30 freight cars on the main. Here I come at 99 mph 10 miles south of Newark, N.J. and uh oh! . . . ended up neatly coupled to the B5 and pushing the freight at about 3 mph! The shock of seeing that train on the main was enough thank you. I didn't need a visible crash.

enjoy!



Anything less your gonna see less performance

[baldwin]

Does everyone's version of PRR ER end at Gallitzin? I ask because in trying to resolve my error, I generated another error, this new one apparently due to a broken path. It turns our that the versions at CLW and here are not the same version as the one I have. My version ends farther west of Gallitzin, in Pittsburgh Yard. This doesn't resolve my explore route error, but would explain the new broken path error.

Mine ends in Pittsburgh yard.

[R. Steele]

Mine also ends in Pittsburg. Screenshot taken with OR Track Viewer (if anyone has not tried this - you should, very nice.)

Also I think I have found the spot Mike is talking about - see other two screenshots taken of the OR Trackviewer. Overbrook is a little ways away from the 30th Street Overcrossing where the stations are. I'm going to poke around there this afternoon and try to find the signals causing the trouble.
30th Street.jpg cursor points to near where Overbrook is, red box outlines enlarged area. Overbrook_30th.jpg relative distance between 30th St and Overbrook
Pittsburg yard .jpg end of PRR-ER in Pittsburg Yards

[ckawahara]

To one and all.

The OR Team has resolved whatever the cause of my inability to run PRR was.

Otto...your screen of the error appears to be the same as the one I had.

X2643 will have the fix applied.

Thanks OR. Thanks to all who replied to the posts in this issue.

Craig

[OTTODAD]

Thanks, ORTS team !

http://www.otto-wipfel.co.uk/video/orts-prr.wmv