Bahn 3.89 compared to 3.88

[1993matias]

How nice to see the new version out!
Are there any differences between this version and 3.88 important to routing, coupling and signalling (not itineraries)?
What is there of important changes? I have read the change log on the website, it is quite long, with some notes being difficult for me to understand.
Also, what is the new feature about compound trains? How does it work?

[Seb144]

Also, what is the new feature about compound trains? How does it work?

Hello,

compound trains might be useful for you. E. g. IC2 and IC8 couple in a certain station. So far one of these trains lost its data, eg. IC8 became IC2. Now they remain what they are, basically two seperate trains coupled and running as one. The advantage is when you decouple at another station you have the trains as they were before.
For the rest: What exactly are your questions?

Regards,


Sebastian
_________________
Berlin und Umgebung im Jahr 1989

http://www.bahn1989.berlin

[1993matias]

Does compound trains work like that for all couplings now? Or only if you specifically ask for them?

About the other questions, anything you have noticed that has changed?

[Seb144]

Does compound trains work like that for all couplings now? Or only if you specifically ask for them?

About the other questions, anything you have noticed that has changed?

Only if you check the option in the shunting point.

Yes, a lot, like train names, train delays, via destinations (probably also useful for you), requesting itineraries at stopping points and shunting points, itineraries with direction indicator ...

Get the new version, you won't regret it!
_________________
Berlin und Umgebung im Jahr 1989

http://www.bahn1989.berlin

[Chris]

One of the things that has made my life easier is distant signals accepting a switching function. This meant that three-aspect signals at junctions required an additional hidden signal. The one improvement I'd like to this feature would be the ability to use both at once to avoid repeating potentially complex expressions, e.g. (!Itin1&Sig3)|(!Itin2&Sig4) rather than (!Itin1&(Sig3Fn))(!Itin2&(Sig4Fn)). Especially when I have expressions such as the following:

Code: Alles auswählen

CF2015: ~CF-2015-P4|~CF-2015-P0|~CF-2015-P1|~CF-2015-P2 
        ^           ^           ^           ^
        |           |           |           \ CF2231: ~CF-2231-3|~CF-2231-4
        |           |           \ CF2019: ~CF-2019-C|~CF-2019-3
        |           \ CF2617: ~CF-2617-B|~CF-2617-2
        \ CF2713: ~CF-2713-0|~CF-2713-1|~CF-2713-2

Thankfully, the signal with the following function only has one signal leading to it:

Code: Alles auswählen

CF2030: ~CF-2030-0|~CF-2030-1|~CF-2030-2|~CF-2030-C|~CF-2030-D|~CF-2030-3|~CF-2030-4|~CF-2030-6|~CF-2030-7|~CF-2030-8