Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: MSTS/real world length discrepancy? How to deal with it?

  1. #11
    Join Date
    Dec 2006
    Location
    Brockville, ON, CA
    Posts
    2,487

    Default

    I'm pretty sure this is a Google Earth/MSTS problem, just the marker skew the further east or west of Chicago your route is.

    On the DAR the distances for the north/south portion are pretty close, the new 86 mile Annapolis Royal to Yarmouth section is about 2 miles out. The Windsor to Windsor Junction section is east/west, it's should be 30 miles according to the CP ETT but in MSTS it came to 39 miles. What I ended up doing it to place my mile posts every 1.3 MSTS mile to get only 30 mile posts.

    Keeping a passenger train on schedule is a little tough for that 30 miles but there isn't much else you can do.

    Paul :-)

  2. #12

    Default

    After roughly a month of thinking this over, if this new projection method allows for true to life distances, then I'm willing to it all over again, I could care less about the coordinates. With TSRE laying the track isn't that much of an issue now, but I need to know if this will work properly with Google Earth imagery and .hgt files because I'd rather have the right elevation data regardless of co-ordinates.

    So far I've tried this line in .trk file:

    TsreGeoProjection ( 48.8485 2.29143 -12340224 30290944 )

    ...and the terrtex imported from GE is completely wrong. I bet I have to modify this line a bit. When using this one, the game thinks I'm somewhere south of Brest, Belarus.

  3. #13
    Join Date
    Jun 2013
    Location
    Minnesota
    Posts
    1,291

    Default

    I tried that world projection trick and it does seem to work. I tried it in Japan and the trackwork I've done so far looks nowhere near as skewed as MSTS

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •