Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Pacific Surfliner tracks issue

  1. #1

    Default Pacific Surfliner tracks issue

    Tracks look like a sandstorm is covering them. They look fine in MSTS.
    Attached Images Attached Images

  2. #2
    Join Date
    Mar 2007
    Location
    Phoenix AZ
    Posts
    378

    Default

    Check your OR log, I believe you'll see missing ace files.

  3. #3
    Join Date
    Jul 2005
    Location
    Sandwich, Illinois, USA.
    Posts
    13

    Default

    Let me know if you figure this out. I have the same issues and they just started on several routes, Cajon, Tehachapi II and PSL
    Kevin Kelleher

  4. #4
    Join Date
    Mar 2005
    Location
    Norwich, Norfolk, United Kingdom.
    Posts
    898

    Default

    I had that just recently and found it was when i moved a newer route in with some older ones and it overwrote the original Tsection.dat file in the global directory, i swapped TSections around for different versions and in the end found one they were all happy with.

    Intel i5 2400, Mobo ASUS P8H67, Win 7 Prof 64bit, 32GB Ram, Nvidia GTX960 4GB, SB Audigy, 6.25TB HDD's.

  5. #5

    Default

    I believe the FPM Surfliner route installer forces the installation of an outdated Tsection (version 26?) with no option to abort that part of the process.

  6. #6
    Join Date
    May 2010
    Location
    Worksop, UK
    Posts
    1,776

    Default

    Hi PSXE,
    I believe the FPM Surfliner route installer forces the installation of an outdated Tsection (version 26?) with no option to abort that part of the process.

    The easiest way to overcome that problem is to (1) save the outdated version, in case you need it, (2) download the version you want from here or the UKTS library and (3) install the new one.

    Unless the FPM Surfliner route uses a specialised version, it should work just as well with any later version.

    Cheers,
    Ged


  7. #7

    Default

    I am aware, I don't have the problem, but just pointing out that particular installer just blindly jams an outdated copy onto your system without performing any version testing, potentially replacing a newer version you already had installed and gumming up the other routes being run in the same installation, when people might not realize what has happened behind the scenes. Easier path is making a copy of the existing tsection before running the installer

  8. #8
    Join Date
    May 2010
    Location
    Pacific Time
    Posts
    846

    Default

    Quote Originally Posted by PXSE View Post
    I am aware, I don't have the problem, but just pointing out that particular installer just blindly jams an outdated copy onto your system without performing any version testing, potentially replacing a newer version you already had installed and gumming up the other routes being run in the same installation, when people might not realize what has happened behind the scenes. Easier path is making a copy of the existing tsection before running the installer
    That's very likely true. Making a backup copy of your current or preferred tsection is a good idea before installing any route that uses an installer that keeps you from seeing what it's doing. FPM was bad in many respects - its treatment of tsection.dat is only one of them.

  9. #9

    Default

    Not sure what any of you mean as I don't know what Tsections are or any of the dtails. Surfliner was installed years before Open Rails.

    EDIT: Just tried this route in MSTS. It took 8 minutes to load terrain buffers (usually takes 10 seconds) and crashed with error saying that several .ace files were missing. I will uninstall and reinstall from the CD.
    Last edited by Damascus; 02-24-2019 at 03:19 PM.

  10. #10
    Join Date
    Nov 1999
    Location
    Huntsville, AL
    Posts
    4,113

    Default

    Quote Originally Posted by Damascus View Post
    Not sure what any of you mean as I don't know what Tsections are or any of the dtails. Surfliner was installed years before Open Rails.

    EDIT: Just tried this route in MSTS. It took 8 minutes to load terrain buffers (usually takes 10 seconds) and crashed with error saying that several .ace files were missing. I will uninstall and reinstall from the CD.

    "
    Not sure what any of you mean as I don't know what Tsections are" Tsection.dat is a file that contains reference data for ALL track sections. As a new track type is created or as new track pieces are created this file is updated. It is located in the Global sub-folder of root folder of an MSTS installation. It is in readable text and if opened you will notice at the beginning a "Build" number. The most current build is maintained in the file library. Older builds are deleted when a new one is uploaded to the library.

    Some Route developers wrote their installation programs to install the current Tsection file without considering that later routes would require newer Tsection files. What they should have done was to tell the use to Install Tsection.dat Build ## or later.


    Question have you recently installed the route
    BNSF Seligman Route for Open Rails from TrainSimulations? If you did, did you install in into the same install that you are finding problems with? I ask this because you said"...crashed with error saying that several .ace files were missing". This new route for Open Rails should NOT be installed with other routes as it replaces ACE files in the Global\Textures folder with DDS files.
    Charles

Posting Permissions

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