[sidney54]

Bonjour, depuis la version 2823, les points d'inversion semblent ne pas fonctionner correctement.
Le train ne s'arrete plus avant l'aiguille à dégager mais continue sa route jusqu'au prochain signal ou la fin de voie.


Translation per google:
Hello, since the 2823 version the reversal points seem not to work correctly.
The train stops further needle to release but continued on to the next signal or channel end.

Added by Bazza (moderator)

[Serana]

Here's a better translation :

Quote

Hello, since the 2823 version the reversal points don't seem to work correctly.
The train doesn't stop after the switch, but continues its run up to the next signal or the end of the track.

I guess its an AI problem.

[sidney54]

Serana, on 06 February 2015 - 09:22 AM, said:

Here's a better translation :




I guess its an AI problem.

Oui cela se produit avec les trains AI et de plus j'utilise une timetable, jusqu'à la version 2822 cela fonctionnait bien.

[roeter]

Do you use 'passing paths'?
Est ce que vous utiliser de 'passing paths'?

Regards,
Rob Roeterdink

[sidney54]

roeter, on 06 February 2015 - 09:53 AM, said:

Do you use 'passing paths'?
Est ce que vous utiliser de 'passing paths'?

Regards,
Rob Roeterdink

passing paths non utilisés.

[roeter]

OK - can confirm this. Not sure it's version 2823, though, but it is somewhere in that area.
I'll look into it.

Regards,
Rob Roeterdink

[roeter]

OK - found it.
Apologies, it was my error.
In the 'split' between activity and timetable, the code for calculation of reversal point also had to be split. To do this, a new method was defined with instances for both activity and timetable. The original code in AITrain was removed, but accidently the call to the new method was not inserted.
This is now corrected in version 2844.
Thanks for reporting this.

Regards,
Rob Roeterdink

[sidney54]

roeter, on 06 February 2015 - 03:14 PM, said:

OK - found it.
Apologies, it was my error.
In the 'split' between activity and timetable, the code for calculation of reversal point also had to be split. To do this, a new method was defined with instances for both activity and timetable. The original code in AITrain was removed, but accidently the call to the new method was not inserted.
This is now corrected in version 2844.
Thanks for reporting this.

Regards,
Rob Roeterdink

Bonjour, fonctionnement tout a fait normal maintenant.
Merci

Cordialement