My collection of issues - maybe bugs?

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

    • May 2010
    • 989
    • Pacific Time
    • ORTS

    #1

    My collection of issues - maybe bugs?

    OR 0.9.0.1648
    MSTS fully patched with Bin doesn't do these things. Annoying. Some started in 0.9 and were OK in 0.8.

    Practically all routes - some kind of error or warning is thrown, even on default routes, though most (not all) eventually start. A guaranteed fail-to-load is Donner Pass (the abandonware version in the f/l) which does work (with some glitches) in MSTS-bin; throws a ton of exceptions then bombs without even getting to an open window.

    Air (using keyboard): to release, must press ; until reaching 0%, then release, then press again to get the BC to decline, and hold until it reaches 0. Handle animation follows the %, not the actual release. Occurs on both diesels and electrics (haven't tried steam). Occurs whether the model has self-lapping brakes or old-style. Started occurring in 0.9; worked as expected in 0.8.

    L&PS Coal Extra activity - when backing out of pocket track at start get undesired emergency crossing the trailing-point switch that can't be reset. Stays in emergency requiring exit from simulator. Switch appears to be properly lined.

    Electrics - in external (2 or 3 or 4) view, pantographs do not rise when pressing P.

    Digital instrument panels: better than v0.8, but the numbers still don't fit the 'glass cockpit' fields as they do in MSTS.

    No needles on analog air gages. Many analog speedometers also have no needle.

    Amtrak locomotives (P42, electrics) have an accel/decel gage that doesn't work at all in OR.

    Semaphore signals do not work at all. Signal aspect shows in track monitor window (F4) and if the semaphore also has a color light it shows there, but the semaphores themselves do not operate. Don't remember whether this is a change from 0.8 behavior. For an example, check the Grand Canyon route - but it occurs on all routes with semaphore signals.

    FPS never exceeds 25; drops to 20-21 in complex scenery areas. MSTS on the same routes runs generally in the 30-50 range though with its usual hesitations when loading the next tile. OR 0.8 ran much more smoothly with higher apparent FPS rates (in the 30s).

    Short blasts of the horn don't work for steam or most diesels - blasts are all the same length, just like the default engines - regardless of how it works in MSTS. Case: Pac Surfliner F59s from Facing Point set (also from the original designer now) have a very responsive horn in MSTS, but it is not at all responsive (has default gp38 characteristics) in OR. Funny, though, the horns on the electrics work fine in L&PS. This behavior started in 0.9; did not occur in 0.8.

    On the plus side, distant mountains work well, and greatly improve the realism of scenery on western and mountain routes.

    All of these glitches occurred before the most recent OS and Catalyst patches as well as now. System is not an issue.

    Computer: Core 2 Extreme X9650, 3GHz; 6G RAM; Win 7 Pro 64-bit fully patched; ATI HD5450, Catalyst 13.4
  • seagoon
    5000 Post Veteran

    • Jun 2001
    • 5161
    • Yamba, N.S.WALES, Australia

    #2
    Originally posted by cbff33
    .....And you expect it to work in Open Rails?
    Why not? - it works in MSTS and so far what works in MSTS works in OR....at least, it does for me.

    By-the-way.....your location is "here", not "hear".
    IBM XT i386; 512Kb RAM; 5.25" FDD; 1.4Mb FDD; 5Mb HDD; VGA 256-colour graphics card; AdLib soundcard; DR DOS 6.0; Windows 3.0

    Comment

    • baldwin
      6000 Post Veteran


      • Nov 1999
      • 6358
      • Chippenham, Wiltshire, UK.
      • ORTS

      #3
      There are things that will work in MSTS, but not in OR because the error checking in OR is much more detailed. OR is very good at showing up things that should not work in MSTS and gives the reason why it might not work in OR.

      Short horn blasts are only possible in OR if the cue points are in the right places. I have found on used in the RMD east rolling stock that will give very short sounds from the horn if needed.

      Pantographs do work in 0.9.

      While I agree that FPS can be low in detailed areas, I get as low as 30 in places, I do also get at least 200 FPS in areas that are low in scenery objects. I am running an E7500 @ 2.9Ghz.

      I have only had one route that would not start, and that was because the trk was missing. However, it only takes one fatal error to stop a route from running, but OR does give you an option to send in a bug report for investigation and produces a log file to look at, if the logging option is checked.
      Beer is not a matter of life or death, it is much more serious than that.

      Comment

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

        #4
        Originally posted by mikeebb
        Air (using keyboard): to release, must press ; until reaching 0%, then release, then press again to get the BC to decline, and hold until it reaches 0. Handle animation follows the %, not the actual release. Occurs on both diesels and electrics (haven't tried steam).
        Happy to see that I am not the only one to comment on the peculiar way how the Train Brakes control now works in ORTS and until it performs like in real diesel and e-locos ORTS is of no interest to me, despite the better distant mountains, other terrain textures along the tracks being replaced with odd looking ones, the ORTS team leader has been made aware of.

        Comment

        • motormaster532
          Senior Member
          • Jan 2011
          • 465
          • New York

          #5
          As long as the subject of brakes comes up.Anybody run into this.I was running a custom Activity on MONON-2 using Utah Railway F45s{Dont ask me why!!!!!} and I experienced difficulty in using the Dynamic Brake after Throttle and vice versa.The dynamic brake would not engage after cutting the throttle back to zero.I noticed that even at zero if you depress the "A" key the clicking that indicates that you are throttling back continues un-abated.This causes the Dynamic to not engage.I found a non-reliable way around the problem by centering and then forwarding the reverser and highlighting the area in the cab with the cursor.I did the same thing going from Dynamic to Throttle.However it only works about 75 percent of the time.The Activity is quite large and I have to admit that I am still working out Open Rails but if anybody else is experiencing something like that I would love to know how to correct it.I have to say that when I work out all of its nuances,I probably will use MSTS just to create Activities.Open Rails is just so superior to it.

          Comment

          • scamel
            Member
            • May 2010
            • 68
            • Calgary, AB

            #6
            Originally posted by motormaster532
            ... I experienced difficulty in using the Dynamic Brake after Throttle and vice versa...
            I noticed the same thing, but I think it's already been reported. It might be this one: https://bugs.launchpad.net/or/+bug/1160292

            Also, this may be a stupid question, but are you waiting for the dynamic to set up?
            Last edited by scamel; 07-20-2013, 16:28. Reason: Stupid question added
            sigpic
            Andrew Underwood

            Comment

            • motormaster532
              Senior Member
              • Jan 2011
              • 465
              • New York

              #7
              Originally posted by scamel
              I noticed the same thing, but I think it's already been reported. It might be this one: https://bugs.launchpad.net/or/+bug/1160292

              Also, this may be a stupid question, but are you waiting for the dynamic to set up?
              Thank you Andrew for the reply.Yeah,the problem is that the Dynamic cant set up when the throttle key is able to decrease into infinity.As I said,I was able to "fool" it by centering and forwarding the reverser most of the time but it still is annoying.I am going to check out the link you gave me and see what the deal is.As I said,it also happens going from Dynamic back into power mode as well.Brian

              Comment

              • scamel
                Member
                • May 2010
                • 68
                • Calgary, AB

                #8
                Originally posted by mikeebb
                Air (using keyboard): to release, must press ; until reaching 0%, then release, then press again to get the BC to decline, and hold until it reaches 0. Handle animation follows the %, not the actual release. Occurs on both diesels and electrics (haven't tried steam). Occurs whether the model has self-lapping brakes or old-style. Started occurring in 0.9; worked as expected in 0.8.
                I noticed this as well. I've been wandering through my frequently used .ENG files looking for it.

                Originally posted by mikeebb
                L&PS Coal Extra activity - when backing out of pocket track at start get undesired emergency crossing the trailing-point switch that can't be reset. Stays in emergency requiring exit from simulator. Switch appears to be properly lined.
                I had this problem as well, but then I discovered CTL+M. Some routes, particularly those that use short paths for the players, need this. Do it again, but this time when the train goes into emergency, press CTL+M and try to recover the air. That should at least get you moving again.

                Originally posted by mikeebb
                Electrics - in external (2 or 3 or 4) view, pantographs do not rise when pressing P.
                I do not have this issue with the default routes, I can see them raising and lowering in the MSTS NE Corridor, but I have other difficulties getting them moving. I don't play in the default routes hardly at all, but these are my only electric locos.

                Originally posted by mikeebb
                Digital instrument panels: better than v0.8, but the numbers still don't fit the 'glass cockpit' fields as they do in MSTS.
                I've noticed some controls don't fit properly either.

                That's an interesting problem, Brian. I wonder if it's a combination of things, like something in the .ENG file that MSTS overlooked (or didn't care about) or if it might actually be an OR bug unrelated to the one I posted previously!
                sigpic
                Andrew Underwood

                Comment

                • rdamurphy
                  8000 Post Veteran
                  • Nov 1999
                  • 8429
                  • Where Standard Gauge is 3 feet between the rails.

                  #9
                  Originally posted by mikeebb
                  OR 0.9.0.1648
                  MSTS fully patched with Bin doesn't do these things. Annoying. Some started in 0.9 and were OK in 0.8.

                  Practically all routes - some kind of error or warning is thrown, even on default routes, though most (not all) eventually start. A guaranteed fail-to-load is Donner Pass (the abandonware version in the f/l) which does work (with some glitches) in MSTS-bin; throws a ton of exceptions then bombs without even getting to an open window.

                  Air (using keyboard): to release, must press ; until reaching 0%, then release, then press again to get the BC to decline, and hold until it reaches 0. Handle animation follows the %, not the actual release. Occurs on both diesels and electrics (haven't tried steam). Occurs whether the model has self-lapping brakes or old-style. Started occurring in 0.9; worked as expected in 0.8.

                  L&PS Coal Extra activity - when backing out of pocket track at start get undesired emergency crossing the trailing-point switch that can't be reset. Stays in emergency requiring exit from simulator. Switch appears to be properly lined.

                  Electrics - in external (2 or 3 or 4) view, pantographs do not rise when pressing P.

                  Digital instrument panels: better than v0.8, but the numbers still don't fit the 'glass cockpit' fields as they do in MSTS.

                  No needles on analog air gages. Many analog speedometers also have no needle.

                  Amtrak locomotives (P42, electrics) have an accel/decel gage that doesn't work at all in OR.

                  Semaphore signals do not work at all. Signal aspect shows in track monitor window (F4) and if the semaphore also has a color light it shows there, but the semaphores themselves do not operate. Don't remember whether this is a change from 0.8 behavior. For an example, check the Grand Canyon route - but it occurs on all routes with semaphore signals.

                  FPS never exceeds 25; drops to 20-21 in complex scenery areas. MSTS on the same routes runs generally in the 30-50 range though with its usual hesitations when loading the next tile. OR 0.8 ran much more smoothly with higher apparent FPS rates (in the 30s).

                  Short blasts of the horn don't work for steam or most diesels - blasts are all the same length, just like the default engines - regardless of how it works in MSTS. Case: Pac Surfliner F59s from Facing Point set (also from the original designer now) have a very responsive horn in MSTS, but it is not at all responsive (has default gp38 characteristics) in OR. Funny, though, the horns on the electrics work fine in L&PS. This behavior started in 0.9; did not occur in 0.8.

                  On the plus side, distant mountains work well, and greatly improve the realism of scenery on western and mountain routes.

                  All of these glitches occurred before the most recent OS and Catalyst patches as well as now. System is not an issue.

                  Computer: Core 2 Extreme X9650, 3GHz; 6G RAM; Win 7 Pro 64-bit fully patched; ATI HD5450, Catalyst 13.4
                  Thanks for your comments!

                  A lot of these issues have been fixed, or are in the process of being bug-squashed.

                  Might I suggest you download the latest experimental release?

                  This is the official home of Open Rails with news and links to content, vendors and the community. Open Rails is a totally free train simulator that supports the world’s largest range of rail content.


                  There's also a list of bug fixes on the page.

                  Thank you, Robert
                  sigpic

                  Comment

                  • gpz
                    Member
                    • Jul 2012
                    • 49
                    • Budapest, Hungary

                    #10
                    Originally posted by mikeebb
                    Short blasts of the horn don't work for steam or most diesels - blasts are all the same length, just like the default engines - regardless of how it works in MSTS. Case: Pac Surfliner F59s from Facing Point set (also from the original designer now) have a very responsive horn in MSTS, but it is not at all responsive (has default gp38 characteristics) in OR. Funny, though, the horns on the electrics work fine in L&PS. This behavior started in 0.9; did not occur in 0.8.
                    Mike,

                    Would it be possible that you uploaded the horn wav file in question with its corresponding sms file, and sent a PM to me with the link, so that I can download them? I would be interested in finding the problem with these sound files, but I see that these sounds are payware, and I have no other chance to look on them. (I will not buy them just to debug OR's sound code, and I will also not buy them to play with, being from Europe, and knowing not too much of American trains.) So I promise I will delete them as soon as they become useless to me in maintaining OR program code.

                    Peter Gulyas
                    Last edited by gpz; 07-21-2013, 13:46.
                    Peter Gulyas

                    sigpic

                    Comment

                    • mikeebb
                      Senior Member

                      • May 2010
                      • 989
                      • Pacific Time
                      • ORTS

                      #11
                      More strangeness. I crawled through most of what I have installed in 4 'mini'routes and found that the problem of practically constant horn 'blow' length regardless of how short your try to cut it off occurs only with:

                      - Default locomotives (GP38, SD40, Dash 9, electrics) - also in MSTS so it's not a OR problem.
                      - Most but not all of the diesels supplied with the payware Cajon Pass/Hi Desert and Tehachapi routes; most work correctly in MSTS.
                      - Some but not all of the F59PHIs supplied with the payware Facing Point Surfliner route (originally developed by Marc at 3dtrains and now available from him); all of them work correctly in MSTS.
                      - The freight locomotives from the Facing Point route.
                      - The GG1s from CLW or the PRR-ER route - same in MSTS so it's not a OR problem.
                      - Some but not all of NALW's P42's - same in MSTS so it's not a OR problem.
                      - Steam whistles, especially those that are based on NALW's UP steam megapack (beautiful steamboat whistle sound; but it's on for the same length of time no matter how long or short you tap the space bar - same in MSTS so it's not a OR problem).
                      - Some but not all of NALW's F40s - but the MBTA cab car works perfectly.

                      All of the other freeware locomotives I tried worked properly, with reasonably controllable horn blow length, unless they were aliased to the default diesels (makes sense).

                      If it's OK with the vendors who I still have to check with, I could send you some of the sms files to look at, but at this point I suspect that for the F59s I can just copy the one that worked right to the other Amtrak engines. Will need to examine it and figure out what needs to be changed in the Metrolink engines separately because they use a different horn sound than the Amtrak engines. The cab cars work perfectly.

                      On the pantograph operating front - it's true that the default electrics (Acela, HHP) and the CLW/PRR-ER GG1s work as expected. The interurbans and electric locos in the L&PS and BCER (both fully freeware) routes don't - the pan visually stays down or up as it starts out regardless of pressing P. P does, however, correctly cut off or reconnect power from a cab view and driving standpoint.

                      Strange: while most of my nitpicks were there a week ago, even after installing 0.9, the glass cockpit stuff and accel/decel gages (except on one of NALW's (freeware) P42s) now seem to work. Still some without needles though, and in at least one case errors are logged that might provide a clue. And the semaphores work in the AZCA route - will need to check Grand Canyon again maybe it's a route issue not OR itself.

                      FPS is still limited - crept up to 27-28 in the AZCA route but that one has little detail in the scenery across the desert.

                      Thanks for the offer, but your response led me to look at things more closely and the result is that much of the problem may not be with OR itself, at least with regard to the horn sounds. More news as it develops...

                      Comment

                      • scamel
                        Member
                        • May 2010
                        • 68
                        • Calgary, AB

                        #12
                        Your problems were a part of what inspired me to download the Natal Mainline route (sapd.zip - there were other personal reasons, my girlfriend is South African). It is electrified, you see, so I thought it would be a good way to examine the pantograph issue in closer detail. When I press P, the pantograph (Pantograph 1) goes up and down, and it correctly cuts or applies power. Pantograph 2, on the other hand, will raise and lower, but it doesn't register a connection.

                        I have issues with some cab views in OR, very similar to you in terms of where and how things are displayed. Needles aren't in the same spots, some things in MFDs over run their boundaries and my big one is missing control handles! I get a lot of errors to do with texture sizes and what not, but since everything works, I ignore it and carry on happily. I think a large part of things in cabs not rendering properly is that OR can support a larger screen size then MSTS could.
                        sigpic
                        Andrew Underwood

                        Comment

                        • gpz
                          Member
                          • Jul 2012
                          • 49
                          • Budapest, Hungary

                          #13
                          Mike, please don't forget the wav files (beyond sms), because I need to check the way cue points are defined in them. And only the ones work in MSTS but not in OR are interesting, the others that don't work in MSTS should be considered as "works as designed". (And I don't need the whole loco, I don't want to "steal" them.)
                          Peter Gulyas

                          sigpic

                          Comment

                          Working...