Announcement

Collapse
No announcement yet.

Arosa Linie: Bug & Support Thread

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Not sure this has been reported before, the I think the speedometer HUD of the GE 4/4 II can be improved. There's two things 'wrong' with the current situation.

    1. The throttle indicator in the HUD doesn't match the actual throttle lever. As seen in pictures below, the HUD can show a "4" when the throttle lever is set in positions 1.5 (15km/h) or 2 (20km/h)

    Click image for larger version  Name:	15kmh.jpg Views:	0 Size:	741.2 KB ID:	4556 Click image for larger version  Name:	20kmh.jpg Views:	0 Size:	753.8 KB ID:	4558


    2. The speedometer doesn't display the selected cruise control speed. There's no way to tell what speed the throttle lever is set to, just by looking at the HUD. Even when you'd think that a number "6" would indicate you're set to 30km/h, the 'bug' mentioned above makes this workaround unreliable.

    I'd suggest to do two things;

    - A. Use the throttle indicator to display the same numbers as the throttle lever mouse-over tooltip (so, 3 when set to 30km/h, a 2.5 when set to 25km/h)
    - B. Use the same system the German trains do for AFB (so the blue bar).

    In comparison, I've attached screenshots of the GE 4/4 II and the DB BR143 both set to 30km/h. Both locomotives use their throttle lever as a cruise control, so I think the HUD should also reflect this in a similar fashion. The only difference is that the BR143 actually throttles up or down notches, and thus the speedometer reflects the same number as on the dashboard of the train (in this case, "2").
    Click image for larger version  Name:	30kmh.jpg Views:	0 Size:	909.2 KB ID:	4559 Click image for larger version  Name:	br143.jpg Views:	0 Size:	912.5 KB ID:	4557

    I think adjusting the HUD of the GE 4/4 II in this way makes it less frustrating and annoying to operate. I consider these 'quality of life' improvements.

    Comment


    • Jasper_Rivet
      Jasper_Rivet commented
      Editing a comment
      Hi Purno, thanks for reporting! We'll have a look into the way the speedometer and the hud interact with each other.

      On the other hand, I don't think that we'll add the blue bar as you're used to from other German add-ons, as the driving control wheel does only acts as a speed selector when going uphill. In comparison to the German train: The RhB speed selector does not slows the train down.

  • #32
    Hi, I have a problem with the livery designer on the Ge 4/4 II. The front part has a little area which decals ignore. I'll attach a picture of a square decal so you see what happens clearly. I hope this gets fixed soon! 😀

    Click image for larger version

Name:	Captura de pantalla 2021-05-06 164443.jpg
Views:	285
Size:	74.5 KB
ID:	4566

    Comment


    • #33
      I love this line and have played many times and compared my journey to this video https://www.youtube.com/watch?v=ClIdWYE9wRU
      One glaring mistake, and the reason I keep spadding at Untersax northbound is you've missed a distant signal at the start of the passing loop. Also the signal at the end of the loop is too far around the corner. In the video it is visible from the loop straight. Check it out at 45mins and you will see what I am talking about.
      Luen Castiel also has only one stop board northbound on the left of the line. I keep spadding past the one on the right as it shouldn't be there and blends in to well with the station building. It's in the video at 37 mins.
      Lovely route though and still playing it to chill out.
      Last edited by 1938Tubestock; 05-06-2021, 09:53 PM.

      Comment


      • Jasper_Rivet
        Jasper_Rivet commented
        Editing a comment
        Hi and thanks for the feedback! I'll forward this to our devs, so they can have a look at it. And it's great to hear that you're enjoying the route!

        Cheers!

    • #34
      Hi, I've encountered a strange problem at some stations on an uphill run. once I get the green signal and the correct departure indication I get a Spad when I go past the red/ white chequer board sign. This occurs even if I contact the signaller (whereupon I get a proceed as signals indicate). If I ask a second time I get proceed at restricted speed at which point I can pass the sign. is this working correctly? Please note that the service that I am on has the engine back to front (with the usual confusion over the HUD indications, e.g. the door open showing on the wrong side).
      I do not recall having this issue before the patch.

      Comment


      • Jasper_Rivet
        Jasper_Rivet commented
        Editing a comment
        That is strange, once you got a green signal, the shared signal signs should do that. Can you please give us a couple more details: Has this happened to you in scenarios or timetable mode? Do you have an exact service/scenario it happened on? And what system are you on? Thanks for your help!

    • #35
      When can we expect the Arosa Line to be patched ?
      It has been out for some time now.

      Comment


    • #36
      I recently tried a scenario, taking some logs to St. Peter. This scenario was a hot mess, for lack of a better term. I am including a link to my YouTube where I uploaded the video of the scenario so you can see all the problems encountered. I play TSW2 on Xbox Series S.

      https://youtu.be/UaG_Ooz8zLo

      Thanks
      Last edited by RBrimer; 05-22-2021, 04:16 PM.

      Comment


      • AmScot01324_Rivet
        AmScot01324_Rivet commented
        Editing a comment
        Hi, thanks for your report. I've not seen this reported before and I have turned it over to our dev team to check out. Really appreciate you including the platform you use and the YouTube video, which will no doubt prove helpful!

    • #37
      Hi guys.

      There appear to be serious passenger behaviour issues on Arosa. Based on my testing of several morning timetable services (between 7am - 9am and 5pm - 6pm):
      1. There are zero passengers spawning at Arosa Station. It is a ghost town.
      2. A small number of passengers spawn at Chur station, however passengers never board the train.
      Please advise if this is a route issue (and will be updated by Rivet) or a Core issue (and will be updated by DTG). As a customer, it's very confusing to know where to report bugs to for this route, as I have no idea whose responsibility it is to update issue like this.

      Thank you.

      *All testing done on Steam version 4.26

      Comment


      • AmScot01324_Rivet
        AmScot01324_Rivet commented
        Editing a comment
        Hi, thanks for reporting this. Your report is the first instance of this I have seen and I will advise our dev team of the issue.

      • Paulie
        Paulie commented
        Editing a comment
        A little more detail for your dev team with regards to the Arosa spawning issue:

        Two passengers spawn in the distance (the spawn point?) but they do not move. Instead, they disappear and are immediately replaced with another passenger. They remain rooted to the spot. It's like they are being teleported in and out in quick succession.

        This issue can be easily reproduced by choosing one of the morning services departing from Arosa between 7am and 9am, and moving the free cam to the passenger spawn point.

        It is easy to reproduce passengers not boarding the train. They walk up to the train and stand there.

        Thank you

    • #38
      Thanks again Paulie this additional info is helpful.

      Comment


      • #39
        With the very last version (Steam 4.26), the horn function is now broken.

        when I press the horn button, I hear the whistle broken in two parts or, if you prefer, the sound is interrupted by an uggly silence. It is like if this whistle sound is composed of two different sounds files (whistle start & whistle loop) and the program is not able to play the sequence in a continuous manner as it should be.

        Thanks in forward to correct this problem, which is really unworthy for an addon of this quality.

        Comment


        • #40
          Hi ACSoft, thanks for your report. I don't know if it's been already signalled by someone else, in any case we'll take a look into it.

          Comment


          • #41
            Originally posted by matteomo View Post
            Hi ACSoft, thanks for your report. I don't know if it's been already signalled by someone else, in any case we'll take a look into it.
            For your information, I asked to a friend to check if he has the problem too and he confirmed to me it is the case. So, it is not a problem specific to my machine. This is why I have signaled this problem here.

            Comment


            • matteomo
              matteomo commented
              Editing a comment
              Thanks a lot for the clarification.

            • Jasper_Rivet
              Jasper_Rivet commented
              Editing a comment
              I can confirm the horn issue. Although it's not completely broken, but it has a interruption when starting the middle loop... We'll have a look into it, I can't promise anything though.

          • #42
            Hi Jasper_Rivet

            Following the update to 4.26, there is an issue with loco acceleration. It "explodes" into life from a complete stop, which is very jarring.

            Here's a video from another user, who posted this on the DTG support forum, which shows this explosive acceleration in action.



            Thank you,

            Paulie

            Comment


            • AmScot01324_Rivet
              AmScot01324_Rivet commented
              Editing a comment
              Hi, Thanks - this has been reported to our dev team already. As it's happened with the update, I'm not sure who will issue the fix and when. Agree, it is definitely jarring! Please be patient as the problems are worked through.

            • Paulie
              Paulie commented
              Editing a comment
              Thank you AmScot01324_Rivet

          • #43
            Notice how the posts regarding the incorrect timetable were just ignored. Typical Rivet couldn’t care less.

            Comment


            • #44
              Hi - FYI we're not ignoring any of the issues reported - the long-standing timetable issue is still being worked on, although there's clearly been some additional issues with 4.26 that the team are looking into. We're not sure yet whether it's something in Arosa that we need to fix, or something in the engine that Dovetail need to fix, or both. But really appreciate the detail of the issues reported from folks, please keep letting us know about any other issues, and we'll hopefully get them all fixed, and let you know once we know!

              C.

              Comment


              • #45
                Originally posted by ColinM_Rivet View Post
                Hi - FYI we're not ignoring any of the issues reported - the long-standing timetable issue is still being worked on,
                C.
                You will excuse our doubts over your words, when another Rivet employer denied any work was being done on this issue not 2 weeks ago.

                Click image for larger version

Name:	Rivet.png
Views:	64
Size:	38.2 KB
ID:	5160

                Comment


                • ColinM_Rivet
                  ColinM_Rivet commented
                  Editing a comment
                  Absolutely - we're gutted this couldn't be fixed long ago, unfortunately it's been a complicated issue, and we've not been clear on whether we're working on it *right now*, or generally (as in, not *right now*, but it's part of people's task list to work through). Either way, we know you just want it fixed (as do we!) so keep bearing with us, and we'll turn your doubt around in the end I'm sure...

                • RedRev1917
                  RedRev1917 commented
                  Editing a comment
                  thank you for the reassurance Colin, I hope you stick to your word as I know many like myself are hesitant in purchasing any further routes produced by yourselves, and I would dearly love to be able to purchase your Cornwall route with confidence that any release bugs (and lets face it *all* software has bugs in it on release regardless how much testing is done prior to release- Im a realist in this matter) will be addressed in the following weeks, few months.
              Working...
              X