How to Fix 3D Model Error on TrainSimulations ATSF GP60s

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pschlik
    Senior Member



    • Jun 2011
    • 289
    • Missouri
    • MSOR

    #1

    How to Fix 3D Model Error on TrainSimulations ATSF GP60s

    Some of you who got the TrainSimulations EMD GP60 Engine Pack might have noticed an error in the 3D model of the ATSF units, causing a hole to appear at the rear of the conductor's side walkway.

    Open-Rails-2026-09-25-06-41-48.png
    This is due to just a couple of misplaced vertices, and since it is just a couple, this is feasible to fix at home using shape file editing.

    First, back up all the ATSF GP60 shapes (this is only a problem with the ATSF models, the others are all good). You wouldn't want to reinstall the whole pack after making a mistake, after all.
    Then, uncompress all of the ATSF GP60 shapes. Depending on your choice of compression/decompression tool, you might see numbers with a different number of decimal places than I have listed here, but the first 3-4 digits of each value should match.
    Now open each of the uncompressed shapes in your text editor of choice, and Control + F find the line that says "point ( -1.379497 1.697678 -6.061648 )". This line should exist only once, and if you can't find it, try searching for "point ( -1.379" (ie: just the first few digits) and finding the line that matches the first few digits of all 3 values. Then replace that line with "point ( -1.527325 1.697678 -6.061648 )" in each of the files.

    image.png

    Then, do something similar for the line that says "point ( -1.379511 1.945827 -6.06165 )​", which should be just a few lines below the first point you replaced, but this time replace that line with "point ( -1.527339 1.945827 -6.06165 )​".

    image.png
    ​​​
    That will fix the position of the broken vertices, note how the only value changed is the X value, both the Y and Z values are actually fine already. However, the lighting will still be wrong as it assumes the walkway is at a funky angle.
    Next, to fix the lighting, in each of the files find the line that says "vector ( -0.999892 -0.000631 -0.01465 )" and replace that with "vector ( -1 -0.000631 0 )".

    image.png

    Then find the line that says "vector ( -0.861251 0.50818 0 )", which should be just a couple lines below the previous one, and replace that with "vector ( -1 -0.000531 0 )".

    image.png

    Finally, the very next line should say "vector ( -0.999893 -0.000147 -0.014638 )", this should be replaced with "vector ( -1 -0.000147 0 )".

    image.png​
    Then open up the compressed shape in your favorite shape viewer (plenty of choices there these days) and verify the hole is gone on all 3 shapes.

    Open-Rails-2026-09-27-12-26-55.png

    And finally, recompress the shapes to save on file space.


    I hope that helps make these units look a bit more pleasing so they can get their fair share in screenshots, as there probably won't be any fix other than this manual approach.
    Last edited by pschlik; 09-27-2026, 18:50.

    Contributing to ORTS since 2023
    Find me on GitHub @SteelFill

    Like what I do? Join my Patreon to help me do more!
  • dcarleton
    1000 Post Veteran


    • Nov 2008
    • 1004
    • MSOR

    #2
    What if we can't find those two points on our copy of the shape? I have ATSF_GP60_4029.s uncompressed, and when I search for point ( -1.379497 1.697678 -6.061648 ) there is no such line of text. Same thing when searching for point ( -1.379511 1.945827 -6.06165 ).

    Wouldn't it be best if TS could release a patch?

    Comment

    • MMCdude
      Senior Member


      • Sep 2009
      • 497
      • west central Illinois
      • General

      #3
      Try searching for these:

      point ( -1.3795 1.69768 -6.06165 ) (Line 3749)
      Replace with: point ( -1.527325 1.697678 -6.061648 )

      point ( -1.37951 1.94583 -6.06165 ) (Line 3755)
      Replace with: point ( -1.527339 1.945827 -6.06165 )

      vector ( -0.999892 -0.000631 -0.01465 ) (Line 78968)
      Replace with: vector ( -1 -0.000631 0 )

      vector ( -0.861251 0.50818 0 ) (Line 78970)
      Replace with: vector ( -1 -0.000531 0 )

      vector ( -0.999893 -0.000147 -0.014638 ) (Line 78971)
      Replace with: vector ( -1 -0.000147 0 )
      __________________________________
      MMC(SS), USN (Ret.)

      Comment

      • dcarleton
        1000 Post Veteran


        • Nov 2008
        • 1004
        • MSOR

        #4
        Thank you, using those numbers it worked just fine.

        Comment

        • pschlik
          Senior Member



          • Jun 2011
          • 289
          • Missouri
          • MSOR

          #5
          Different compressors/uncompressors produce values with different levels of precision and different line numbers. But the first few digits of each value will always be the same and the points/normals will be in the same order.

          Originally posted by dcarleton
          Wouldn't it be best if TS could release a patch?
          While that might be best, that is not how TS operates.

          Contributing to ORTS since 2023
          Find me on GitHub @SteelFill

          Like what I do? Join my Patreon to help me do more!

          Comment

          • UP6706
            Active Member
            • Jun 2026
            • 152
            • Los Angeles or somewhere near it, CA.
            • English
            • General

            #6
            I suggest TS make an official patch for it so users won't have to work hard modifying them. (not forcing)
            Clayton Wong

            Comment

            • Whatever2006
              Senior Member

              • Aug 2022
              • 615
              • Philippines
              • English, Nonsensical Things and Passive Spitefulness.
              • General

              #7
              I held off from running the ATSF GP60s due to the misalinged walkway bugging me and at the time, I thought the fix is either using an FA or fixing the shape itself were the solution. Until Phillip discovered another way that doesn't involve the two I mentioned which is fixing the shape with a shape file manager utility and a text editor. Because of the fix, the walkway becomes less glaring and more pleasing. I would be running with them again.
              Last edited by Whatever2006; 09-27-2026, 23:45.
              Motto: Loneliness stands by with me and my own isolation.

              Comment

              • burgerbern
                1000 Post Veteran



                • Mar 2005
                • 1088
                • United Kingdom.
                • UK English
                • MSOR

                #8
                the second option worked for me, thanks
                ​
                Processor: Intel 13th Gen i5-13400F, - Mobo: MSI PRO Z790-P​, - OS: Win 11 Prof 64bit. - Memory: Corsair Vengeance 64GB​ Ram, - Graphics MSI RTX 4060 Ventus 2x Black OC 8GB, - Sound: Asus STRIX SOAR Gaming Soundcard​, - Storage: 7TB SSD's. - Case: BeQuiet! Pure Base 500 Black​.

                Comment

                Working...