Open Rails can't find BNSF Scenic GE locomotives?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • menchman

    #1

    Open Rails can't find BNSF Scenic GE locomotives?

    Can anyone help me with the issue? I downloaded the most recent version of Open Rails. When it couldn't find the locomotives at first, I reinstalled the BNSF Scenic v2 route but it will still not find them now.

    GELocoIssue.jpg
  • davebridges
    Senior Member
    • May 2010
    • 203
    • Somewhere in Indiana near the Indianapolis Line

    #2
    I'm having the exact same problem with the new SLI P42DC's that I just installed. Anyone have any suggestions/ideas?

    Comment

    • lindsayts
      Senior Member
      • May 2010
      • 194

      #3
      Have you checked this.....................

      OR does not list the trains by the loco name but by the consist name (I think, I am on my Linux machine at the moment). So if one has a lot of consists listed it can be tough to find a particular loco, unless the consist has been named after the loco. For this reason one has to look real carefully to find a particular loco class as consists are usually not named after the loco haulling it.

      lindsay
      Last edited by lindsayts; 09-12-2011, 02:30.

      Comment

      • davebridges
        Senior Member
        • May 2010
        • 203
        • Somewhere in Indiana near the Indianapolis Line

        #4
        I have the right consist and loco. When I open OR and select the activity, under locomotive it says "unknown" and "n/a" under consist

        Comment

        • longiron
          1000 Post Veteran and Moderator

          • Jan 2007
          • 1453
          • Just south of NYC

          #5
          The way OR determines what to list in the Menu views is entirely different from MSTS. Here's the process that OR uses:

          1) OpenRails reads all consist files
          2) For each consist file if it contains an engine, then the engine is recovered as the "engine name" and "the folder name" (like in the CON file)
          3) OpenRails checks if the related ENG file exists in TRAINSET\"the folder name".
          4) If it exists, OpenRails reads the ENG file and recovers some data such as: the engine's long name, the description, the type of the engine (electric, diesel, steam), and whether it is drivable or not.
          5) If the engine is drivable and it is compatible with the route (can theoretically run on the route given its type), then it is added to the list of engines, and the consist is added to engine's list of consists.

          When you choose Explore Route, and select the engine, the consist selection box is populated with all the consists for the given engine.

          When you select an activity, OpenRails, runs through the activity files (player service: Train_Config gives the name of the CON file to search, so if the names do not match = ERROR). Then in the Consist file, it identifies the engine by splitting the value between the brackets EngineData ( engfile "Folder Name" ) by the "space" character so we get: engfile and "Folder Name". If engfile was something like "eng file", the method would fail. This will be upgraded in the next release.

          So once the engine is identified, then it is compared with the list in the engine selection box (which is hidden at this time). If a match is found then the engine name is displayed. If no match is found, then it displays "UNKNOWN", and the consist is "n/a".
          Chris
          "True rail fans have two favorite railroads. The B&O and one other."

          Comment

          Working...