How does one ensure the paper schedule shows up in the bus

Willkommen in der OMSI-WebDisk!
Als Gast kannst du nur Inhalte in deiner ausgewählten Sprache sehen. Registrierte Nutzer können die Sichtbarkeit anderer Sprachen in ihrem Kontrollzentrum aktivieren, weitere Infos hier.
Alle Themen sind in den Foren mit einer Sprachflagge gekennzeichnet: = Englisch [EN], = Deutsch [DE], = Französisch [FR]. Wenn du die angegebene Sprache nicht beherrschst, schreibe auf Englisch!

    1. Which programme do you have a problem with? (Main application, editor, SDK tools, etc.)

    >Main application


    2. Please describe the problem in as much detail as possible. What happened or what might have led to the error?

    >I use a lot of North American buses and while I am grateful for them they are of lower quality and the community is generally not very helpful when it comes to support for them. One of the buses I use the most has gone through several updates with things changed here or there with incomplete change logs on what was added/removed. On the latest (and last) version the paper schedule has vanished. My question is what controls whether or not it is visible? Any help would be very much appreciated, thank you.


    3. Please add a log file to your post, either in a spoiler, code block or as a file attachment.


    4. If there is a helpful screenshot of the problem, you can upload and include it as a post attachment.


    5. Provide your system information if it is a performance problem. (Operating system, processor, graphics card, hard disk type, memory, etc.)

    >

    Hi,


    There are basically two script variables pre defined by omsi that all busses should use to get all information necessary about the paper schedule:

    1. schedule_active gives you the information, whether some schedule is currently enabled or not

    2. file_schedule gives you the path to the current bitmap file that should be used for the schedule


    With that information you can do everything you need, and for the very basic, you don't even need an actual omsi script for that.

    Here is an example right from the Spandau MAN which works fine:



    I would say that you can use this in every bus and it should work. The only thing you might need to change is the texture name below the [matl]-command. It needs to be exactly the same as in the o3d file.

    You usually can just open any o3d file with any text editor and you should find the texture name in plain text somewhere at the end of the file:

    (the "y" is obviously not part of the name anymore) ^^