Announcement

Collapse
No announcement yet.

TrItemRData Value of position Z is too large!

Collapse
Only viewable if you're a logged in user
X
Collapse
First Prev Next Last
 
  • Filter
  • Time
  • Show
Clear All
new posts

    TrItemRData Value of position Z is too large!

    Can anyone explain the following error reported in Route Riter TSutil reports:

    TrItemRData': Value of position Z (1102.8303) is too large!

    #2
    I want to say that's more of a nuisance than an actual runtime problem.

    The max value for that should be 1024, but it's not unusual for things to be slightly off the edge tile of W file it's saved in...

    ORTS seems to be a lot more tolerant of this than MSTS was.
    If you like what you see here at Trainsim.com, be it the discussions and knowledge in the forums, items saved in our library or the ongoing development of our TSRE Fork, I hope you'll consider a paid membership to help support keeping the site operating.... Thanks!

    Comment


      #3
      Thanks. Have you any comment on this one?

      TrackPath(41111-1)': Section-Reference is NOT an even number

      Comment


        #4
        Hi,

        From the context, that's a piece of dynamic track, listed in the route tsection.dat file. MSTS could only have even numbers for the second variable. Goku figured out how to utilize the odd numbers (like in your example), but I doubt Route-Riter and TSUtils know about that.

        Doug
        Making stuff that works, using outdated Software on outdated Hardware.sigpic

        Comment


          #5
          Thank you both. Does either of you know of any sort of "manual" for TsUtils? I am trying to understand more and to use it to correct errors.

          Comment


            #6
            Hi,

            I do not know of one, a manual for TSUtils that explains what the various errors are, and how to correct them. IE where in which file a particular item is located and what to do to fix it.

            WRT the odd number, as long as there is not another error associated with that tsection.dat entry, and it renders correctly in the Sims, it can also be viewed as a nuisance and not as a fatal error.

            Doug
            Making stuff that works, using outdated Software on outdated Hardware.sigpic

            Comment


              #7
              Yup, neither should be a fatal error in ORTS. Neither are the dynamic track sections which have negative values for curves... also introduced by TSRE.

              Because the older tools like TSUtils and RouteRiter that only knew what worked with the MSTS-RE and MSTS, I've pretty much stopped using them except for the occasional head-scratcher.
              If you like what you see here at Trainsim.com, be it the discussions and knowledge in the forums, items saved in our library or the ongoing development of our TSRE Fork, I hope you'll consider a paid membership to help support keeping the site operating.... Thanks!

              Comment


                #8
                Originally posted by eric View Post
                I want to say that's more of a nuisance than an actual runtime problem.

                The max value for that should be 1024, but it's not unusual for things to be slightly off the edge tile of W file it's saved in...

                ORTS seems to be a lot more tolerant of this than MSTS was.
                It seems to happen with track layed in TSRE.

                Comment

                Working...
                X