signals show wrong animations at German route Pro Train 6 Vogelfluglinie (X.1716)

[Thomas Pilder]

With all activities on that route the semaphore signals show the wrong animations. The lights are correct.
I figured out the reason.

This is part of the original sigcfg.dat (I added two comments):

  SignalDrawStates ( 2
   SignalDrawState ( 0
    "Hp0"
    DrawLights ( 1
     DrawLight ( 0 )
    )
    SemaphorePos ( 1 ) //MSTS shows position 0, OR shows position 1
   )
   SignalDrawState ( 1
    "Hp1"
    DrawLights ( 1
     DrawLight ( 1 )
    )
    SemaphorePos ( 2 ) //MSTS shows position 1, OR shows position 0
   )
  )

MSTS seems to do an internal renumbering if SemaphorePos index doesn't start with zero. OR does not.
I changed the indizes starting with zero and OR shows the correct animations.

I think the behaviour of OR is correct, but it would help very much if OR would be as tolerant as MSTS.

Greetings from Germany

Thomas Pilder

[James Ross (twpol)]

That's very interesting... I wonder if that's also what is going on in bug #1096831 (comment #9 especially).

[Thomas Pilder (v200)]

Sorry, I did'nt see that bug report before. It seems to be the same issue. Attachment Hanau.jpg (comment #1) shows a similar situation. Several Pro Train routes use the same sigcfg data with frame numbers starting at 1 instead of 0. IMO comment #9 is correct. But it is still unfixed.

[James Ross (twpol)]

Yeah, that bug did fix the animation for some things but the switch stands are animating backwards (nobody bothered to reply to my question on that in bug 1096831 :( ) in the case of these "odd" values. We'll use this bug to track that oddity.

[Tim Holliday (tialho)]

Just flagged a similar issue on the UKTS forum and was advised to post here - I'm seeing this issue on a number of German commercial routes (GR and ProTrain), even with the latest OR version x2299

A bit of independent fiddling with sigcfg.dat found that a straight reversal of the values of the SemaphorePos parameter (1 to 2 and vice versa) fixed the issue for OR, as did replacing the value 2 with zero; however, n both cases, the amended sigcfg.dat caused incorrect signal displays in MSTS. To clarify:

Original parameters:

SemaphorePos ( 2 )
SemaphorePos ( 1 ) MSTS correct, OR incorrect

Change to:

SemaphorePos ( 1 )
SemaphorePos ( 2 ) MSTS incorrect, OR correct

Or:

SemaphorePos ( 0 )
SemaphorePos ( 1 ) MSTS incorrect, OR correct

Hope this may shed some light on what is going on!

[James Bradley, Jr. (jbrad1974)]

This is exactly the same bug I reported for the Train Order Boards on the Monon route. The signal's lights were displaying correctly, but the semaphore arms were backwards. After reversing the SemaphorePos variables, the order board displays correctly now. It would appear that the SemaphorePos variable is reversed in OR.

[James Bradley, Jr. (jbrad1974)]

https://bugs.launchpad.net/or/+bug/1449839

[James Ross (twpol)]

Tim, what happens if you replace the original:

SemaphorePos ( 2 )
SemaphorePos ( 1 ) MSTS correct, OR incorrect

With:

SemaphorePos ( 1 )
SemaphorePos ( 0 )

[Cédric GNIEWEK (sharpeserana)]

Does the problem still happen with version 1.4?

[Launchpad Janitor (janitor)]

[Expired for Open Rails because there has been no activity for 60 days.]