PRR and OpenRails V0.6.2

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • rrroberttt
    Senior Member
    • Nov 1999
    • 146
    • NYC USA

    #1

    PRR and OpenRails V0.6.2

    To the Open Rails team:

    I can tell that you guys have been working on the rail road, LOL. I am amazed at how you have the PRR Eastern Division, running with this version, 0.6.2. I only ran into two errors they are track database errors.

    One:

    This is an explore route activity from, Washington, DC - New York City.pat, And the error below seem to happen Just a bit, before entering the Waverly Yard Section, before the Newark, NJ Amtrak station.

    Image 025.jpg


    Two:

    This is an explore route activity from, New York City - Washington, DC.pat, and the error below, happen just as we are leaving the Waverly Yard area.

    Image 026.jpg

    I did another explore route activity from Altoona - Pittsburgh.pat. Needless to say, not an single error of any kind. Impressive.

    I also ran into something that seems to work only randomly. That is, the "Escape Key". It seem to work only, after the sim first load. Otherwise, it locks up and want to send home to Microsoft. Also, some trains do not want to run. Of course you already know this, from another thread.

    By the way, did I say that I'm IMPRESSED ?? You can bet on it.


    Again, Thanks to all the creators.
    Last edited by rrroberttt; 07-31-2011, 10:41. Reason: error in terminology
  • twpol
    Senior Member
    • Oct 2009
    • 434
    • United Kingdom

    #2
    Originally posted by rrroberttt
    This is an freeroam activity from, Washington, DC - New York City.pat, And the error below seem to happen Just a bit, before entering the Waverly Yard Section, before the Newark, NJ Amtrak station.

    [ATTACH=CONFIG]43750[/ATTACH]


    Two:

    This is an freeroam activity from, New York City - Washington, DC.pat, and the error below, happen just as we are leaving the Waverly Yard area.

    [ATTACH=CONFIG]43751[/ATTACH]
    I've fixed both these (same issue) so that OR will print a warning and the switch that it could not match up to the TDB will display as a static shape (i.e. not switch animation).
    James Ross
    Open Rails Management Team
    sigpic

    Comment

    • rrroberttt
      Senior Member
      • Nov 1999
      • 146
      • NYC USA

      #3
      Thank you.
      Last edited by rrroberttt; 08-01-2011, 18:39. Reason: error

      Comment

      • MIKEinNE
        Senior Member
        • Sep 2007
        • 451
        • NE

        #4
        We have been waiting for a report from Chrisvon Waggonner on such issues!

        Comment

        • MIKEinNE
          Senior Member
          • Sep 2007
          • 451
          • NE

          #5
          WE at thePRR-ER would like to know the exact location of the switch so we can look into the matter also (coordinates).

          Comment

          • twpol
            Senior Member
            • Oct 2009
            • 434
            • United Kingdom

            #6
            Originally posted by MIKEinNE
            WE at thePRR-ER would like to know the exact location of the switch so we can look into the matter also (coordinates).
            Here's a shortened (I've removed all the stacks and loading markers) log from the "New York City - Washington, DC" path to a little beyond the Waverly Yard:

            Open Rails - 0.6.2.780 - 01.08.2011 17.39.38.short.txt
            James Ross
            Open Rails Management Team
            sigpic

            Comment

            • MIKEinNE
              Senior Member
              • Sep 2007
              • 451
              • NE

              #7
              Thank you; I am curious whether or not you made it all the way to Pittsburgh?

              Comment

              • rrroberttt
                Senior Member
                • Nov 1999
                • 146
                • NYC USA

                #8
                @MIKEinNE

                Using the Altoona - Pittsburgh.pat, I made it all the way to Pittsburgh, without any errors.

                I also use another explore route path, I can't recall at the moment. and, after about 38 minutes, I got the exact same type of error as above.

                Comment

                • rpicardi1
                  3000 Post Veteran
                  • Nov 1999
                  • 3415

                  #9
                  There is an area South of the Newark station where there are switches that have adjacent track errors. They run OK but crash the RE if any attempt is made to edit them. You will notice some very crooked dynamic track connecting them in the crossovers. The entire area blew up on us after work had been done in the Zoo area until Chick Richart Dyntools was able to fix the problems with the dynamic track there. Unfortunely, there are still errors in connecting switches that would have to be hand edited, another minefield in itself, or else, they would needed to be isolated, buried, and track relaid there.

                  Those are probably the switches that OR is detecting as bad.

                  Comment

                  • MIKEinNE
                    Senior Member
                    • Sep 2007
                    • 451
                    • NE

                    #10
                    Ron, did you examine the report?

                    Comment

                    • rpicardi1
                      3000 Post Veteran
                      • Nov 1999
                      • 3415

                      #11
                      From the report and location, the 10 nodes being referred to are from an area of New Jersey where there is a yard made up of inactive track with 10 static switches. A continuing report for nearby World files would find more inactive track switches in that engine service yard.

                      When there is no TDB entries for track found in the World file, MSTS treats such track as a static object. We created inactive track to represent competitive rail lines that were in the area in order to hold down the size of the TDB. This inactive track is what the report found.

                      Comment

                      • MIKEinNE
                        Senior Member
                        • Sep 2007
                        • 451
                        • NE

                        #12
                        i will take what Ron has said a step further. there is a lot of this deactivated track all over the PRR-ER in NJ and western PA in order to keep the tdb size down. In other words, this type of track is in effect a form of static object. For test purposes, one ought to drive a train through Elizabethport, NJ. One should see a ton of this type of track creating errors.
                        Last edited by MIKEinNE; 08-03-2011, 15:41.

                        Comment

                        Working...