Frage zu door.osc

Der dritte Eintrag ist für die 2. Tür, nicht für die erste und dort wollen Passagiere nunmal aussteigen. Ohne den Eintrag wissen diese aber nicht wann die Tür offen ist. Wozu willst du die ganze Geschichte überhaupt bearbeiten?

Hello,

Quote from M.Baraniak

Woher weiß ich, welche Zahl hinter dem L.L.door stehen muss?

In every* door_X variable, X stands for the real door wing index, as we perceive it by looking at the physical ordering of doors, beginning from 0, from front to rear. So door_0 reflects the opening state of the first wing, door_1 of the second wing, ..., door_7 of the eighth wing.

Quote from M.Baraniak

Was hat es mit der 5 auf sich? Es gibt doch gar keinen 5.Türflügel.... (eigentlich doch nur 0,1,2 und 3)

Indeed, if all doors combined only yield 4 wings total, then the door_4, door_5 variables are useless. But perhaps the author intended to reuse the same code with 3-door vehicle variants. Or they just didn't bother cleaning up the redundant code.

Quote from M.Baraniak

Wo ist L.L.door_4?

This is likely a shortcut because the author thinks that both wings will be opening/closing (almost) synchronously, and hence deems it appropriate to just check whether one wing, likely the slowest one, is sufficiently open to allow boarding/disembarking. But of course that will fail if one decides to manually (e.g. via the emergency opening valves) open just these individual wings (door_3, door_5) while leaving the other two (door_2, door_4) closed, in which case passengers will magically be able to walk through the closed latter ones as well.

So the proper expression would be:

...or better yet, for individual control:

Quote from M.Baraniak

Der dritte Eintrag heißt ja meines Wissens, dass die 1.Tür zum Ausstieg freigegeben ist, wenn der 3.Türflügel (2.Tür also) zu 0.9 offen ist.

Wenn ich diesen Eintrag rausgelöscht habe, sind die Fahrgäste nicht mehr hinten ausgestiegen. Dabei ist in der passengercabin.cfg gar kein Ausstieg an der ersten Tür vermerkt und dieser dritte Eintrag doch eigentlich überflüssig?

No, the index X in the PAX_[Entry|Exit]X_[Open|Req] variable names is not necessarily equivalent to the X in door_X. Here X means strictly according to the ordering of the passengercabin.cfg. And the ordering in the .cfg represents priority, and not (necessarily) physical door wing order.

For example, suppose that we have a bus with 5 doors (let's forget about door wings for a moment, for clarity's sake). Suppose also that we want our passengers to be able to board the vehicle from doors 3, 1, and 5, in that exact priority. And we would also want them to be able to disembark from doors 1 and 4 (here there's no notion of priority -- passengers in OMSI always choose the nearest exit). As for the spare 2^nd door, we want it to be purely cosmetic, i.e., to neither serve as an entry nor as an exit to passengers.

Here's how the .cfg would look like:

And here's how the .osc would look like:

Note that there's no door_1 above. This doesn't mean that the variable is useless though, since it would still be used to animate the 2^nd physical door, in another part of the script. It just hasn't been mapped to any entry or exit used by passengers, since we don't want passengers to ever use it.

* * *

* Strictly technically speaking, that's not true. door_X are non-standard variables, and as such they can represent anything the script/bus author wants them to represent. But in practice X indeed virtually always follows the physical door (wing) ordering, as do the actual values assigned to those variables.