Ticketpack .otp Issues

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!
  • Hi there!


    I've been meaning to make my own ticketpack for my upcoming map, but I've run into an issue where omsi displays the following error:

    Code
    75 9:55:34 PM -  -   Error:           In "TicketPacks\Aberdeen\Aberdeen.otp" there was an error in line 49!

    In game, the bus only shows the first ticket entry:



    This is the .oft file which I am using:

    Any insight would be greatly appreciated. Thanks!

  • Hmm, very strange...

    Could you please upload your otp-file as attatchment here. Because I can't see any issues so.


    This is the .oft file which I am using:

    Sure oft?! Oft-Files are OMSI-Fonts. It must be a *.otp (OMSI Ticketpack) File :)

  • tealts

    Hat den Titel des Themas von „Ticketpack .oft Issues“ zu „Ticketpack .otp Issues“ geändert.
  • Sure oft?! Oft-Files are OMSI-Fonts. It must be a *.otp (OMSI Ticketpack) File :)

    Yes, *.otp haha my bad!


    Webdisk won't let me upload .otp file extensions, so I've changed it to .txt


    I've also made a few changes since creating the post, removing brackets, forward slashes, periods, etc. None of these have resolved the issue.

    • Hilfreichster Beitrag

    Hey!

    I took the file you posted above and put it into OMSI and it doesn't cause any problems. All four tickets are loaded without any problems. What happens if you take a different text encoding? As far as I know, OMSI can handle "UCS-2-LE-BOM" best.

  • Hey!

    I took the file you posted above and put it into OMSI and it doesn't cause any problems. All four tickets are loaded without any problems. What happens if you take a different text encoding? As far as I know, OMSI can handle "UCS-2-LE-BOM" best.

    Hmm that's super odd! I tried with multiple buses and it didn't seem to work for me. Maybe it is text encoding then, since you were able to get it running with no problems! I will give this a try and keep you updated, thanks!

  • okay, that can be. I am confused too, but on my PC/my OMSI it works without any problems or error messages. :/

  • So I've tried different text encodings, and from what I've found:


    UTF-8: Error Thrown, only "Adult Single" appears on the ticketbox.

    UCS-2 LE BOM: No error thrown, no tickets shown at all (see picture)


    I have also tried using ANSI encoding since the Berlin.otp files use this encoding. However, when trying to convert via. Notepad++, I open the file > convert > save > close but when I reopen, the file is automatically converted back to UTF-8.



    Would you mind sending me the file that worked for you in game please? I am at a total loss what could possibly be wrong here!

  • Would you mind sending me the file that worked for you in game please? I am at a total loss what could possibly be wrong here!

    Yes, sure. Aberdeen.txt

    This file is working without any problems. (On my PC)

  • Hmm so I've tried plugging in the file that you've sent back and maybe because it was converted from .otp to .txt to .otp the file encoding changed again. That said, the file was as before: only showing the adult ticket.


    I am almost certain that the issue is text encoding, as you suggested, but I might have to put this issue on the backburner for now :S I have spent way too many hours trying to figure this out haha


    Thank you for your quick response and help though! I'll update here if I resolve the issue.

  • I have also tried using ANSI encoding since the Berlin.otp files use this encoding. However, when trying to convert via. Notepad++, I open the file > convert > save > close but when I reopen, the file is automatically converted back to UTF-8.

    Hmm, this should not be like that. Do you try it again, for example with the Windows Notepad?

  • I have also tried using ANSI encoding since the Berlin.otp files use this encoding. However, when trying to convert via. Notepad++, I open the file > convert > save > close but when I reopen, the file is automatically converted back to UTF-8.

    Hmm, this should not be like that. Do you try it again, for example with the Windows Notepad?

    Yes, I've tried converting to ANSI using Notepad "save as" function, but after I save and close the file, it converts back to UTF-8 as well. Are there some characters that aren't supported in ANSI?