Open Rails Stopped Working (file system limitation)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • geepster775
    2500 Post Veteran


    • Sep 2006
    • 2846
    • .
    • General

    #16
    My Open Rails videos https://www.youtube.com/@lakecities3663/videos

    Comment

    • crstagg
      4500 Post Veteran


      • Nov 1999
      • 4885
      • Huntsville, AL
      • Texan
      • MSOR

      #17
      Originally posted by wooohooo
      I ............................

      However, I have logging turned off as I'm afraid turning it back on might cause problems again. Is there a way to set the logging file in a different folder location? Preferably away from OneDrive folders?
      Using Regedit navigate to Computer\HKEY_CURRENT_USER\Software\OpenRails\ORTS
      Edit or enter new item named LoggingPath
      Type = REG_Z
      Data = C:\xxxxxxxxxx\XXXXX (Location of your choice.)
      Charles

      Comment

      • dnewmanjr
        Senior Member



        • Jan 2008
        • 874
        • Beaumont, Texas
        • General

        #18
        Lately, I've been getting this dreaded notification from O/R. Every time I go to test out one of the routes I recently edited, something like this POPS UP.

        copyImage.jpg
        Attached Files
        Don Newman, Jr.

        Comment

        • slipperman
          3500 Post Veteran



          • May 2010
          • 3787
          • Worksop, UK
          • MSOR

          #19
          Hi Don,
          PLEASE attach the OpenRails log file (from your Desktop) the next time you get that message.

          However, you say the message occurs when you "go to test out one of the routes I recently edited".
          Do you get the message with any route, or just this one?
          If it's only the one route, I suggest that you've probably made an error when editing it. Try running the pre-edited route - you DID back it up, didn't you?

          Cheers,
          Ged

          Comment

          • dnewmanjr
            Senior Member



            • Jan 2008
            • 874
            • Beaumont, Texas
            • General

            #20
            Just about several of my routes been getting that dreadful SYSTEM.NULL REFERENCE message, including my payware routes. Time for me to eliminate the routes is was running that were compatible to Open-Rails and start over from scratch...AGAIN!! UGGGGH!!
            Don Newman, Jr.

            Comment

            • derekmorton
              5500 Post Veteran



              • Nov 1999
              • 5699
              • Eltham, Victoria, Australia.
              • ORTS

              #21
              If you wish for assistance, attach a log file.

              The jpg you posted last time was far too small to be usefull.

              Comment

              • c44d9w
                Member
                • May 2010
                • 58

                #22
                A NullReference exception is a general exception when the code expects an object by does not find one. It can have many different causes.

                The exception shown in the JPEG references file Traveller.cs at line 867. Here is the code:

                Code:
                                // We're on a junction or end node. Use one of the links to get location and direction information.
                                var pin = trackNode.TrPins[0];
                                if (pin.Link <= 0 || pin.Link >= TrackNodes.Length)
                                    return;
                                tn = TrackNodes[pin.Link];       <--- line 867
                                tvs = tn.TrVectorNode.TrVectorSections[pin.Direction > 0 ? 0 : tn.TrVectorNode.TrVectorSections.Length - 1];
                                ts = TSectionDat.TrackSections.Get(tvs.SectionIndex);
                                if (ts == null)
                                    return; // This is really bad and we'll have unknown data in the Traveller when the code reads the location and direction!
                                to = pin.Direction > 0 ? -trackOffset : GetLength(ts) + trackOffset;
                The index into the TrackNodes array is verified in the preceding lines. Thus the expression should reference an existing element in the array. I can't see how this line could produce a NullReference exception.

                The following line could produce a NullReference exception if "tn" were null. But that would mean that there is a null element in the TrackNodes array, which in turn may imply an issue with the tracks.

                The log file should report if there were problems with track.

                Comment

                Working...