Beiträge von Ixel

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 everyone,

    For those not on the official Discord for AUXI, here's an update.


    Regarding the tomorrow.io weather problem recently, this has been fixed in the latest beta version of AUXI which I'm aiming to rollout next month generally to everyone. They changed something on their API which unfortunately broke AUXI's ability to access the API in the current generally released version.


    This beta update has a number of other changes and additions and has been in the beta phase for quite some time, so there's still a fair bit of work to be done before it can be generally released to everyone (e.g. implement new translation strings, update documentation, the usual stuff).


    Appreciate your patience and I'll get the new version out as soon as I can.


    EDIT: For some other bugs reported here, I'm hopeful that the upcoming update of AUXI will also address many of them.

    Hi,

    This isn't a bug, AUXI currently disables the sky texture as I haven't found a reliable and easy way to modify the sky texture in OMSI 2 from AUXI based on current weather conditions, so at the moment AUXI uses a combination of cloud height and visibility to try to make it appear cloudy or clear sky if its integrated weather feature is used. In an upcoming update I've reworked how the cloudiness is determined so it should hopefully be improved, although still no texture.


    Unless I eventually discover a way to change the sky texture easily and reliably, all I can potentially do is offer the user the choice to not have AUXI override the sky texture and therefore use whatever might be currently set in OMSI 2 at the time.

    I have a small problem with the Real weather feature. A few days before it was very sunny and warm where I live, but in OMSI it was just very gray cloudy but the temperatures were reproduced correctly. The correct coordinates for my city are in AUXI. Is it by chance possible that AUXI cannot display a blue sky? So far I've always had the right temperatures, but blue skies have never been displayed in conjunction with AUXI. If this can be fixed I would be happy.

    It's possible I need to tweak the parameters regarding cloud cover/visibility a little more, I'll try to make it more lenient in a future update.

    Hi all,

    I've not had any real beta feedback on Discord regarding the current beta version so I'm looking elsewhere for feedback. If you've been having problems with version 1.4 (e.g. performance issues) then please DM me and I'll try to somehow maintain a temporary list of beta testers from here as well as on Discord. I'd like to try and get the performance issues eliminated that some users have reported happening since version 1.4.


    Problem ist nicht mehr da, Post ignorieren, danke

    This looks like an unusually rare problem, possibly specific to the bus you're driving. Can you tell me more about the bus you're driving and possibly DM me a log file from AUXI (debug logging level).


    Ich kann auf einmal den Hotkey zum nach vorne lehnen (bei mir X) nicht mehr nutzen, und der Menüpunkt für den Fahrersitz ist grau und nicht benutzbar. Der Hotkey ist korrekt gesetzt, ich glaube das hängt mit dem Fahrersitz zusammen.

    That is also an odd problem. A debug log from AUXI might help but I have a feeling I might have to add some further logging to identify the cause of this specific problem.

    Hi everyone,

    Thanks for your feedback regarding version 1.4. I'm a little puzzled as to why some issues have been introduced in version 1.4 but in an effort to try and pinpoint the cause I propose making some beta versions which gradually rollback each feature or change introduced in version 1.4 one by one, starting with the ability to enable/disable OMSI logging to file.


    I'll aim to have a beta version ready later this week, but in the meantime if you aren't already a member on the official Discord for AUXI (Paulwise Ltd's Discord server) please join it and ask me for a beta role if you don't already have it. I will distribute the beta versions there and ask for feedback there. It's easier for me as beta feedback is in one place as well.


    If you need the Discord invitation URL I can provide it, otherwise you can join it via AUXI's menu.


    Thanks for your patience!

    My observation has been for some maps with tightly positioned bus stops that 20 meters generally works well. I can't say I've noticed issues with 20 meters in general so if someone was to ask me what I'd recommend trying, I'd agree with setting it at 20.

    Indeed, the ability to enable or disable OMSI logging on the fly could be handy. I'm not sure if it would conflict with "-nolog" however, that's untested. I imagine "-nolog" may override AUXI's ability to enable or disable OMSI logging. If OMSI logging is disabled in AUXI then it doesn't actually begin doing that until a vehicle is assigned to the user/player. Prior to that OMSI will continue logging as normal. I've found that disabling OMSI's ability to log to file can impact some plugins such as Bus Company Simulator, but I've added a warning about this to AUXI when someone attempts to disable OMSI's logging.


    Regarding the distance between stops, you are correct. It helps to address the issue in OMSI 2 where some maps have bus stops tightly positioned together, causing OMSI 2 to be unable to correctly identify the next bus stop at times.


    Regarding the interception of OMSI 2's ability to save, that's an interesting idea and I will see whether it's possible, I don't imagine that's going to be easy though.


    As for the weather, yeah I'm aware of the issues some users have and in a future update at some point I will make some changes to the current implementation, some of which could be:

    - Add another weather API or weather source

    - Allow the user to change the way cloud textures are applied by AUXI, specifically whether AUXI should override them (current - which can appear like a grey sky in the game if it's cloudy) or let OMSI 2 choose the texture (essentially might be considered hoping for the best with this one)

    Indeed, the value for the distance to a bus stop/station, the one which determines when the timetable says you've arrived or departed from a bus stop/station, exists in OMSI's memory and can be modified if you know where to find it. It took some time to find it though. It's not hardcoded as such, just originally not modifiable by a user.


    Similarly to disable or enable OMSI's ability to log stuff to its log file, it was possible by modifying some instructions in memory. Some safety measures were taken though, as modifying instructions or memory addresses is not for a novice. AUXI will check the signature of the addresses where the instructions are meant to be for controlling OMSI's ability to log to its log file.

    Ich denke da wirst Du nicht fündig. Ich hab den Inhalt auch kürzlich gelöscht um zu schauen ob das den Fehler behebt, es änderte aber nichts. Trotzdem könnt Ihr selber mal nachschauen, hab es aus dem Papierkorb wiederhergestellt: Buses.zip


    Im großen und ganzen habe ich die Fahrersitz-Funktion nur genutzt um schnelle Werte für die Bus-Datei zu ermitteln und diese dann fest dort einzutragen, da ich auch andere Sichten abändere. Sehr nützlich war aber der Zoom/Nach-vorne-Lehnen Hotkey, der nun nicht geht.

    Hi,

    I'll be in contact later today to send you a special beta version which presumably fixes this issue. I see what the problem potentially is thanks to the ZIP file.



    Seit heute geht der Zoom/Lehnen Hotkey wieder und das Fenster zum Einstellen des Fahrersitzes ist wieder aufrufbar. Ich hatte aber zunächst einen ganz seltsamen Fehler wo die dynamische Kamera nicht auf der Standard-Kamera war, konnte ich aber durch Löschen des Inhalts des Busses-Verzeichnisses anscheinend beheben.


    Doch zu früh gefreut. Der Menüpunkt ist wieder ausgegraut und der Hotkey zum nach vorn lehnen geht auch wieder nicht. Ziemlich seltsam, denn ausser OMSI Neuladen zwischendurch wurde nichts geändert. Version 1.3.1.1, wie vor 2 Stunden auch.

    No doubt caused by the same problem I've identified.

    I've looked into what your error message is about, as I see it's rare but not isolated to AUXI. There have been a few other threads regarding this error message but from what I can see there's been no obvious solution. AUXI just modifies certain weather settings in OMSI 2's memory. Sadly the log files weren't helpful for this particular problem.


    - Have you tried all kinds of weather conditions in OMSI 2's settings, including real weather, to see if something triggers this error message while AUXI's weather is disabled?

    - Have you tried different maps?

    - Have you tried different vehicles?

    - Have you tried both dynamic and real weather modes in AUXI?

    - Probably too long to list, but what kind of plugins and addons do you have installed for OMSI 2? One of importance is do you have OMSI Presentation Tools installed as this doesn't work at the same time as AUXI, there's a compatibility issue. While I doubt it's related to the error you're getting, I mention it because it might be a little unpredictable I guess

    Ah, sorry, I see now. I'll try that file again and look into the problem. For now to workaround the problem I would suggest setting Sunday 00:00 to have a max humans count of whatever you'd prefer it to be. That should address the problem.

    hi there is already the problem with several that auxi the number of passengers is constantly changing ask for a solution! For example, I had a factor of 200 set and when I start playing it is at 0 and my friend is the same

    Can you send me your 'OMSI 2/AUXI/ai_schedule.dat' file please? You'll have to send it in a ZIP file I imagine. I need to see how yours is configured, if it's configured at all.

    Since today I have a problem with the interior view when I use AUXI. For example, if I have spawned a MAN NLC 18C and a Mercedes Facelift GÜ and now drive with the Facelift GÜ and switch to the MAN at some point, the left mirror view on this vehicle is shifted without me doing anything. I have reinstalled the DLC several times and it only occurs when AUXI is installed. If AUXI is uninstalled, the problem does not occur. I also once got a lot of errors in the log file and the AUXI.log. A screenshot is also here.

    This is an odd issue, although it's dark, it looks like the camera is turned a bit left compared to where it should be? If so then the only feature in AUXI which can make the camera turn left or right currently the driver camera wheel turning with steering wheel feature. You could try backing up your AUXI/Buses folder and then cleaning out the AUXI/Buses folder so there are no camera offset settings saved at the moment. See what happens.


    The OMSI log errors are unrelated to AUXI. As for AUXI's log, there's something I don't like the look of:

    Code
    08, 04, 2023T23:51:02 - ERROR: Exception: System.FormatException: Die Eingabezeichenfolge hat das falsche Format.
       bei System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
       bei System.Convert.ToSingle(String value)
       bei ‏‌‫‫‪‪‬‏‮‪‏‏‌‮‫‪‍‍‏‭‌‍‬‎‬‍‮.‪‮‮‮‫‫‍‬‌‏‮‪‌‪‬‭‏‎‌‮‫‮(Int32 , String , String , Boolean )
       bei ‮‪‬‬‎‌‌‌‬‪‍‏‎‎‍‏‮‍‬‪‭‮‬‬‮‪‮.‬‍‪‬‍‪‬‪‎‮‏‎‎‫‬‍‭‮‮(DateTime )
       bei ja6$C@>}\&\&x8M2)%{'<d_?gK-.‎‫‭‫‍‫‬‌‎‎‎‭‏‬‎‮‏‮‍‏‬‮(Object , EventArgs )

    The above error might be causing unexpected behaviour such as what you showed in the screenshot. If this persists in the upcoming version then I may have to send you a special version for further debugging. If you'd like to get the latest beta version then send me a DM and I'll send you it, as it might somehow already be fixed in this version.


    Nochmal zum AI Planer:

    Auch wenn dieser wohl derzeit nicht funktioniert würde ich gerne wissen ob AUXI die Daten global speichert oder sich die Maps merkt. Es macht ja wenig Sinn für alle Maps die gleichen Daten zu nutzen. Ausserdem: sind die Sonntags-Werte auch für Feiertage gültig?


    Eine Idee zu den Sichten:

    Ich hab ja schon erwähnt dass eine Einstellung und Speicherung pro Fahrzeug auch der anderen Sichten sehr hilfreich wäre. Dazu würde ich gerne ergänzen dass es klasse wäre wenn man über AUXI weitere "Dauerfeuer"-Sichten festlegen könnte und an einen Hotkey binden. Damit meine ich Sichten wie ticket selling und schedule view, welche mit einer extra Taste verknüpft werden können. Ich könnte noch 2-3 solcher Hotkeys gut gebrauchen, zum Beispiel um an deiner Kreuzung schnell links und rechts schauen zu können, also kurz Taste drücken und wieder loslassen. Gerade wenn ich mit Lenkrad fahre wäre das sehr hilfreich. Kann mir gut vorstellen dass die AUXI Technik sowas erlaubt.

    The upcoming version of AUXI has had the logic for the AI scheduler completely rewritten from scratch so should address issues with it. It will also interpolate between values on the AI scheduler.


    At the moment it's global, there are plans to also make it map specific in the future but that's what loading and saving presets can be used for at the moment. Public holidays are not currently observed by it and will need further work in order to figure out how to implement the ability to detect that in OMSI 2. For now you could have a specific preset for public holidays.


    The hotkeys will be expanded further in future versions. An addition that's definitely planned is something you mentioned, a press and hold key to temporarily turn the camera left or right by 90 degrees. Potentially other views could also be done too, but then I guess it would then need to be bus specific hotkeys which adds a layer of complexity to the current code. It's possible but will take a bit more time.

    Hi,

    I didn't realise that it could go above 255, I believe I added a limit on the number input field itself. If I did then I'll remove the limit ideally for the upcoming patch.

    Microsoft's built-in check for some reason has not quite worked for a few people. This unfortunately isn't something I can control as it's Microsoft who adds the 'check' during the build/compile process.


    Can you confirm if you have the following version installed please?


    https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x64.exe


    The above link is to the Core 6.0 Desktop Runtime (must be the desktop variant). If you have a different version of 6.0 Runtime installed then I would uninstall it and then install this. Let me know.


    P.S. Naturally restart after uninstalling and/or installing too.

    Wie ist das mit dem AI Scheduler: die Werte die man dort einträgt überschreiben den von der global.cfg vorgegebenen Wert oder multipliziert sich das? Ich meine wenn der Kartenersteller zum Beispiel für 7:00 Uhr eine Verkehrsdichte von 0.500 festgelegt hat was würde passieren wenn ich in AUXI ebenfalls 0.500 festlege und in den Optionen 100% habe? Bekomme ich dann im Spiel eine Dichte von 0.500 oder 0.250 ?

    The values are overwritten (in memory). So if you specify a traffic multiplier of 1.5 on Sunday at 5am then that's what will be applied. Regarding the 100% and 0.5, in that scenario the 'actual value' should be 0.5. If it was 50% and 0.5 then the 'actual value' should be 0.25.


    Das mit den Sitz einstellen ist super, würde mir aber hier wünschen das auch bei den anderen Kameras auf diese Weise zu können. Es nervt mich nämlich immer für jeden Bus per trial and error alle Sichten nach meinem Wunsch zu konfigurieren, das ginge mit AUxi tausend mal schneller.

    This is planned for a future version, though I can't say when.


    Irgendwie habe ich seit dem letzen Update auch von Auxi auf einmal Performanceprobleme. Statt 30 FPS nur noch 11-15 FPS. Logfile reiche ich noch nach obwohl da keine Errors drin stehen.

    It's possible that the upcoming patch to AUXI might fix this. I've made some changes which will hopefully yield an improvement.

    I have a theory as to why it was happening. Looking at the XML file, the new columns don't exist in it. Therefore the value of the each missing column may not have been interpreted correctly by AUXI as '-1' (an ignored value). However it's just a theory but I think it's most likely why.


    In the upcoming patch, due to how the code for AI scheduler has been completely redone, this shouldn't happen as 'ignored values' aren't added to a 'points' array - which is used for interpolation between points.

    Regarding the AI scheduler, I'm hoping the upcoming patch will fix it but I find it interesting that a possibly 'corrupt' .dat file caused the increased passengers.

    Yeah thanks! But its a little strange indead! But the fix is if you delete this file and that works. But i have the idea that there is some diffrent betweem them before and after the update... I have no clue what but looks like there is :)

    Do you have the original file that was causing the increase? I can compare it if so.

    Regarding the 'late' time. I could probably change the value for what's considered early and late, however I'm concerned a little about one thing (if it's possible). I would have to most likely continue to enforce the -2 minutes and +3 minutes for early and late if BCS/BBS/CCS is currently being used. I could only allow a customised early and late threshold as long as BCS/BBS/CCS isn't currently being used too.


    In a future version I intend to allow the radius for the distance from the bus stop to be reduced from 60 meters (default) to possibly as low as 10 meters. This will be able to be customised by the user. I won't allow it to go any higher than 60 meters though for obvious reasons.


    ---


    Regarding the AI scheduler, I'm hoping the upcoming patch will fix it but I find it interesting that a possibly 'corrupt' .dat file caused the increased passengers.