AMUAV.CNAVO.MV.U error code when playing on Liestal V3

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 add-on or mod (map, vehicle, modification) do you have a problem with? Check whether there is already a freeware thread or a DLC thread about it.

    >Liestal V3


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

    >When driving on the map for a few minutes, I start seeing my fps drop significantly, to the point where OMSI becomes unplayable. I tried fiddling around with the ailist, putting back the original ailist, tried to fix other errors with a bus or two, added entries to the varlist of a bus, nothing worked, it keeps doing it. I was able to complete a few runs before, for some reason not anymore.


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


    I've only copied a section of the logfile, because the entirety of the rest of it is literally just the same error code repeating 20 times every second for a few thousand times, along with some tiles loading without errors. The thread was too long to be posted with the whole logfile.


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

    reboot.omsi-webdisk.de/net/attachment/226958/

    Zitat von Prototype001

    My first guess would be to install the 4GB Patch, if not done already. Try to reinstall the objects for the map

    I already run the 4gb patch since a long time, and reapply it every time I add something significant like a bus or a map. Already tried to reinstall the whole map too, twice, including objects and the additional fixes.

    Zitat von Prototype001

    Could you send the ailist as the whole file?

    Sure, here you go. It's basically the base ailist that comes from the original files, but I edited some bus names, since I wanted to keep other versions from those same buses beforehand. They're properly named according to how I've named them in my folders. I.E.: "vehicles\MB_O530_Facelift v2\12M EM 2D M.bus" would typically only be MB_O530_Facelift without the "v2". I also changed some repaint names, since several simply did not exist.


    ailists.cfg

    Zitat von Prototype001

    My guess would be that a bus or train is faulty, that can happen

    Shouldn't it say which one causes problems in the logfile? I had issues with a train before, because it wasn't included with the map, so i had to look for it on the internet. Apart from that, didn't have issues with the map during the first two days I played on it, until some point on the map that apparently needed the Bremen addon bus so a tile didn't load. So I removed it and replaced it with another, and that's when it started going haywire. Bit the bullet and bought the Bremen addon, and added the bus back in the ailist, but it didn't do anything. Now it simply refuses to work properly.

    The first error I see, is that some object is missing. Right after that, OMSI says that the "ZOB_Dach.sco" has a missing glass texture.

    The real error came after

    "191 9:07:02 PM - - Information: Try placing random bus:

    192 9:07:02 PM - - Information: Menu pos set", which could be an indicator that maybe some AI buses could cause the problem.

    Alles was 4 oder mehr Räder hat und Menschen befördert ist entweder ein Taxi, Bus etc., aber definitiv kein TukTuk!

    Zitat von Prototype001

    The first error I see, is that some object is missing. Right after that, OMSI says that the "ZOB_Dach.sco" has a missing glass texture.

    The real error came after

    "191 9:07:02 PM - - Information: Try placing random bus:

    192 9:07:02 PM - - Information: Menu pos set", which could be an indicator that maybe some AI buses could cause the problem.

    But it still doesn't say which one, or why. So now it would be a matter of removing one bus at a time and adding it back until I find the culprit?

    So after around an hour of playing around with the ailist trying to find which vehicle caused the issue, I got annoyed and just decided to try and go all in all at once and replaced every single bus with the MAN EN92 from the base OMSI, along with every ai cars again from base OMSI. Didn't worry about repaints, since OMSI usually just uses a default repaint if it can't find the specified one, without errors. Also removed all trains and the airplane (there was one), and made sure to not leave a space in every blank spots I left. And well guess what? :S


    Here's the ailist with only base OMSI vehicles, if you wanna see it

    At this point I thought maybe OMSI got corrupted and is the problem itself. So tried to play on two different maps, Lemmental and Ahlheim Laurenzbach Updated, both for around half an hour. No major error codes at all. So now I'm 99% convinced the Liestal map is the problem. Any ideas what I should do now?

    No, I didn't see the point since on other maps it works just as usual. Just tried again on Ruhrau this time, no error codes again.


    I just thought about the fact that Liestal is the first map I have played so far that has trams on it. Could the game version not being the "tram version" be what causes all this?

    No, the tram version is just advised if you drive the tram itself. The bus you drive could have an impact too, have you tried different buses?

    Alles was 4 oder mehr Räder hat und Menschen befördert ist entweder ein Taxi, Bus etc., aber definitiv kein TukTuk!

    Yes, the last time I tried on Liestal I was also driving the EN92, to make sure if it was a bus or not that was causing the problem and to make it so only base OMSI vehicles were on the map. So apparently the issue is not a vehicle.