Horse Shoe Curve

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • rrroberttt
    Senior Member
    • Nov 1999
    • 146
    • NYC USA

    #1

    Horse Shoe Curve

    To the ORTS team:

    I just ran the new route Horse Shoe Curve in ORTS V0.6.1.677, and, for the first time with ORTS, I got an out of memory error. The route ran nicely for the time that it ran, approximately 18 minutes. Maybe the team might want to take an look at this.

    Computer Specs.

    Biostar A770E3 Motherboard
    AMD 965BE quad core cpu 3.4Ghz @ 3.9Ghz
    ATI 4670 Video Card 1 gig
    4 Gigs of Crucial Ram 1333 only 3.3gig being used by win XP
    Windows XP, Sp3, latest updates
    700 watt power supply
    Last edited by rrroberttt; 06-23-2011, 11:08. Reason: error
  • longiron
    1000 Post Veteran and Moderator

    • Jan 2007
    • 1453
    • Just south of NYC

    #2
    Originally posted by rrroberttt
    To the ORTS team:
    for the first time with ORTS, I got an out of memory error. The route ran nicely for the time that it ran, approximately 18 minutes.
    Please zip up the complete OR log file and attach to this thread. It contains vital information to assist in debugging this issue.

    Once there's a lull in download activity, we will add it to the routes on which we do testing.
    Chris
    "True rail fans have two favorite railroads. The B&O and one other."

    Comment

    • twpol
      Senior Member
      • Oct 2009
      • 434
      • United Kingdom

      #3
      Originally posted by rrroberttt
      The route ran nicely for the time that it ran, approximately 18 minutes.
      I am aware of certain memory leaks OR has while running along routes, especially those with a lot of custom scenery, so that's probably "all" that's going wrong here. There are (unsurprisingly) plans to improve the situation.
      James Ross
      Open Rails Management Team
      sigpic

      Comment

      • MIKEinNE
        Senior Member
        • Sep 2007
        • 451
        • NE

        #4
        A while back it was reported that OR crashed when users loaded the PRR-ER. It could be that there is a limit to the size that a route will have under OR (I am guessing). The design team of the PRR-ER have not had this problem with the PRR-ER when using it with MSTS, although some have reported memory issues with low end machines. We have heard that there has been testing of the PRR-ER with OR and the results are encouraging.
        Last edited by MIKEinNE; 06-23-2011, 15:56.

        Comment

        • OTTODAD
          1
          • Feb 2001
          • 32344
          • England
          • General

          #5
          Originally posted by MIKEinNE
          We have heard that there has been testing of the PRR-ER with OR and the results are encouraging.
          No major problems here with this rig:

          WIN XP Home - SP3
          AMD Phenom-2 X2 - 3.00Ghz/6MB CACHE
          2 GB CORSAIR DUAL-DDR3 1333 MHz
          1GB ATI RADEON HD 4870
          3 WD VelociRaptors, partitioned

          other than ongoing ORTS W.I.P.

          O t t o



          Comment

          • Train-a-Mania
            1500 Post Veteran
            • Jun 2008
            • 1830
            • General

            #6
            I'm having some sort of issue with an NS consist and the Pittsburgh Line. I wasn't sure how to decipher the problem. I've attached the log below.

            ORPittsburgh.zip
            Nick - Creator of the Virtual Railroading Review Show
            sigpic

            Comment

            • longiron
              1000 Post Veteran and Moderator

              • Jan 2007
              • 1453
              • Just south of NYC

              #7
              Originally posted by Train-a-Mania
              I'm having some sort of issue with an NS consist and the Pittsburgh Line. I wasn't sure how to decipher the problem. I've attached the log below.
              Thanks for attaching the full OR log file. The problem is at the end of the file: "Signal type jjhprrpl3light1 has invalid light texture Ltex2". The PRR_ER team will need to help decipher. OR is certainly less tolerant of missing textures or other issues than MSTS.
              Chris
              "True rail fans have two favorite railroads. The B&O and one other."

              Comment

              • Train-a-Mania
                1500 Post Veteran
                • Jun 2008
                • 1830
                • General

                #8
                Originally posted by longiron
                Thanks for attaching the full OR log file. The problem is at the end of the file: "Signal type jjhprrpl3light1 has invalid light texture Ltex2". The PRR_ER team will need to help decipher. OR is certainly less tolerant of missing textures or other issues than MSTS.
                This is Austin Yoder's Horseshoe route, not the PRR Eastern Region.

                I believe Jovet was one of the folks who worked on signalling. Perhaps he could be contacted.
                Nick - Creator of the Virtual Railroading Review Show
                sigpic

                Comment

                • MIKEinNE
                  Senior Member
                  • Sep 2007
                  • 451
                  • NE

                  #9
                  Nick is correct; Yoder's route was signaled using Jovet's signals; all sigs on the PRR-ER were designed by Signalmaster.

                  Comment

                  • jovet
                    3000 Post Veteran
                    • May 2006
                    • 3050

                    #10
                    Originally posted by Train-a-Mania
                    This is Austin Yoder's Horseshoe route, not the PRR Eastern Region.
                    I believe Jovet was one of the folks who worked on signalling. Perhaps he could be contacted.
                    That error message is a bit crass. "Ltex2" should be a valid texture alias...as the texture is defined as "LTex2". Capitalization shouldn't matter--MSTS has enough of those problems that OR doesn't need to perpetuate or invent more!

                    To get around it, simply open the sigcfg.dat file and do a case-sensitive Search and Replace to change Ltex2 into LTex2.

                    Comment

                    • Train-a-Mania
                      1500 Post Veteran
                      • Jun 2008
                      • 1830
                      • General

                      #11
                      Having changed the case as Joseph suggested, I am now getting a tile error. I've attached the log below.

                      ORPittsburghLog.zip
                      Nick - Creator of the Virtual Railroading Review Show
                      sigpic

                      Comment

                      • TBlake
                        Senior Member
                        • Feb 2009
                        • 266
                        • Western Pacific - 2nd Sub

                        #12
                        Originally posted by Train-a-Mania
                        Having changed the case as Joseph suggested, I am now getting a tile error. I've attached the log below.

                        [ATTACH=CONFIG]42967[/ATTACH]
                        One thing you might check in sigcfg.dat is
                        runactivity.exe : Warning : 0 : Unknown SignalSubObj flag DEFALUT in STF C:\Program Files (x86)\Microsoft Games\Train Simulator\ROUTES\Horseshoe\sigcfg.dat

                        Shouldn't that be DEFAULT ?

                        also, runactivity.exe : Error : 0 : Signal type vl_switchstand has invalid light texture Ltex.

                        I changed all of my Ltex* to LTex*

                        TBlake
                        'Tony'

                        Comment

                        Working...