PilotOne

Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • 25. December 2018 at 14:32 in reply to: Sode module fault #3167
    PilotOne
    Participant

    If all that you write is true, it does not surprise me that you have crashed.

    Take a close look:

    1) “I am having a problem with a CTD at aerosofts EGLL professional with p3dv4.”
    2) SODE protocol: “[10:32:03.724] INFO SODE.XML : xml File Found: UK2000 Heathrow Xtreme.xml!”

    Do you notice something? You have installed 2 different scenarios at the same time for Heathrow Airport – EGLL – and apparently also active! Once Aerosoft Heathrow Professional – as you write at the beginning of this thread, and according to the SODE protocol also UK2000 Heathrow Xtreme.

    THAT can not go well and is also the cause of your crashes. It has absolutely NOTHING to do with SODE.
    I myself run the same configuration, P3D4.4 and SODE 1.64 and the Aerosoft Mega Airport London Heathrow Professional, without any problems.

    Deactivate one of the two scenes and try again. I think it will work.

    Merry Christmas

    21. December 2018 at 12:54 in reply to: jetways don't moving anymore #3153
    PilotOne
    Participant

    Go to the SODE Platform Manager and check the registrations. Unregister all and then register ONLY P3D4.

    It is suspected that the “wrong”. Dll file is called. This will be corrected with the re-registration. Then everything should work again.

    You can find the call to SODE in the addons.cfg file -> C: \ ProgramData \ Lockheed Martin \ Prepar3D v4.

    If in this file the path does NOT refer to the folder “P3D v4”. this is NOT the simulator path but a subfolder in the installation directory of SODE!

    This entry in the addons.cfg is made by the SODE Platform Manager. If this path is not correct, the required 64bit – .dll for P3D4 (64bit) will not be called.

    • This reply was modified 5 years, 4 months ago by PilotOne.
    14. December 2018 at 15:07 in reply to: Registration problem #3137
    PilotOne
    Participant

    The problem is easy to solve.

    SODE can only be correctly registered for 1 (!) simulator. A multiple choice creates only chaos, since only the last clicked variant makes the corresponding correct entry in the addons.cfg of the corresponding folder.

    It’s best to go to the sode platform manager, unregister all variants and register ONLY the simulator that is active or you want to use. Only then does it work.

    Why? Well, this “registration” is just an entry in the “addons.cfg” file that specifies the path for the corresponding .xml file. Into this xml-file the correct .dll file is called.

    If you use P3D3, the addons.cfg of the folder C: \ ProgramData \ Lockheed Martin \ Prepar3D v3) will contain the entry “Your Install Path \ 12bPilot \ SODE \ P3Dv3”. Into this folder (P3Dv3) is the corresponding addon.xml. This .xml file activates the corresponding .dll file. For P3Dv3 is this the “SimObjectAnimationModule.dll”, a 32bit file.

    If you use P3D4, the addons.cfg of the folder C: \ ProgramData \ Lockheed Martin \ Prepar3D v4) will contain the entry “Your Install Path \ 12bPilot \ SODE \ P3Dv4”. Into this folder (P3Dv4) is the corresponding addon.xml. This .xml file activates the corresponding .dll file. In contrast to P3D3, here the called file “SimObjectAnimationModule64.dll” is a 64bit file.

    So if you have first registered p3d3 and then p3d4, only the last entry is made into the addons.cfg. these entry is ONLY valid for p3d4. in this case this will call the 64bit .dll, which is NOT running into p3d3.

    That’s all.

    • This reply was modified 5 years, 5 months ago by PilotOne.
    28. November 2018 at 13:45 in reply to: Problem with "Enable AI Traffic Detection" #3073
    PilotOne
    Participant

    Ich möchte Dir hier nochmals für Deine rasche Hilfe danken, alles läuft jetzt wunderbar.

    Eine Frage hätte ich noch. Nachdem ja der SODE-Placer ebenfalls super läuft – im Vergleich zu GSX kann man hier auch die Höhe der Jetways einstellen – wollte ich dich fragen, ob du ihm auch den Umgang mit den Jetway-Brücken beibringen kannst. GSXLevel2 kann das, jedoch gibts bei GSX einen gravierenden Nachteil. Wenn man es nicht hat, geht gar nichts.

    Im Gegensatz dazu funktioniert der SODE-Placer mit der passenden XML-Lösung auf Dauer. Hab das selbst schon bei mehreren Flughäfen gemacht, ist eindeutig besser als die “GSX-Lösung”. Weil, man kann diese Files auch selbst speichern, an die Flugplätze koppeln und auch verschicken. Ein Riesenvorteil, der deine Lösung eindeutig zur besseren macht.

     

    Mit liebem Gruß aus Wien

    21. November 2018 at 12:57 in reply to: QW 787 SODE Jetways way too high #3056
    PilotOne
    Participant

    Tip:

    Download the AI-Aircraft Editor from  “The Owl’s Nest 2017” = Freeware.

    With this Editor you can check and edit your every plane (aircraft.cfg) on a simply way via a very good graphical user interface.
    Check the vertikal distance of the door, if necessary, correct it.

    If you do not know the exact values, google it or just try different values.

    21. November 2018 at 12:43 in reply to: Not easy to get this working #3055
    PilotOne
    Participant

    I have installed EPWA Warsaw Chopin Airport X from DrzewieckiDesign in P3D4.3 with the original setup file and everything runs smoothly.
    All entries were made correctly.

    For functioning SODE jetways, the following files and folders must be present:

    File 1:    C: \ ProgramData \ 12bPilot \ SODE \ cfg \ DrzewieckiDesign.sdx
    File 2:    C: \ ProgramData \ 12bPilot \ SODE \ sdx \ DrzewieckiDesign \ EPWA_X.sdx (Jetway Placement)
    File 3     C: \ Program Data \ 12bPilot \ SODE \ sdx \ DrzewieckiDesign \ DDWC_X.sdx

    Folder                        C: \ ProgramData \ 12bPilot \ SODE \ SimObjects \ DrzewieckiDesign_EPWA (Jetways)
    Folder (optional)     C: \ ProgramData \ 12bPilot \ SODE \ SimObjects \ DrzewieckiDesign_WCX (Trees)

     

    Please check that.

    21. November 2018 at 12:04 in reply to: Another fail to activate post instal #3053
    PilotOne
    Participant

    I already had a similar mistake. SODE did not work after uninstalling and reinstalling, even though the registry was correctly displayed in the SODE Platform Manager.

     

    The reason for this was an incorrect entry in addon.cfg in the directory C: \ ProgramData \ Lockheed Martin \ Prepar3D v4

     

    This read:

     

    [Package.1]

    PATH = C: \ Program Files (x86 \ 12bPilot \ SODE \ P3Dv3 (!) Instead of P3D4

    TITLE = SODE

    ACTIVE = true

    REQUIRED = false

     

    The result of this is that the wrong (!) .Dll file, namely the SimObjectAnimationModule.dll (for P3D) is called in the SODE program folder “P3D” instead of the SimObjectAnimationModule64.dll (for P3D4, 64bit) in the folder “P3D4”.

     

    And then nothing works, even though it seems correct in the SODE platform Manage. Wrong dll file, no function.

     

    Check that out.

    • This reply was modified 5 years, 5 months ago by PilotOne.
    15. November 2018 at 13:38 in reply to: Problem with "Enable AI Traffic Detection" #3047
    PilotOne
    Participant

    Hallo Jeffrey,

    ich nehme dein Angebot gerne an. Doch zuerst möchte ich dir sagen, das ich vor Leuten wie dir den Hut ziehe. Was du und auch andere Entwickler aus dem Flugsimulator gemacht haben ist einfach sensationell.

    Ich teste deinen Fix sehr gerne, da ich ja in der glücklichen Lage bin, dies unter 2 völlig unterschiedlichen Bedingungen machen zu können. Zum Einen unter “Standardbedingungen” – eine kommerzielle Szenerie mit kommerziellem AI – und zum Anderen unter individuellen Bedingungen – einem selbst erstellten Airport mit eigenem AI, der im FS nicht existiert und den es in der Natur nicht gibt. Hier probiere ich  all die Zusatzprogramme und Dinge, die es im Netz gibt, aus. Beginnend vom Start weg mit der Erstellung von AFCAD’s, Szenerieerstellung, Photoszenerie, Gebäudeerstellung und eigenem AI). Das natürlich alles als “Laie”, doch ich muss sagen, es läuft gut.

    Wenn du mir den Fix über Email (Anhang < 10 MB) zukommen lässt, teste ich ihn gerne. Alternativ, bei größerer Datenmenge geht auch Dropbox. Am besten wäre, wenn du mir zusätzlich Informationen gibst, unter welchen Bedingungen ich testen soll und welche Protokolle du brauchst.

    Liebe Grüsse aus Wien, Bernhard.

    13. November 2018 at 21:27 in reply to: Problem with "Enable AI Traffic Detection" #3043
    PilotOne
    Participant

    I saw it in the log. But I can not say if that is a peculiarity of the pmdg 737/800 WL, because I have just installed this aircraft and a comparison with other aircraft is not possible.

    Apart from that, it has to be said that this log UTL was NOT in operation.

     

    I can not say which id will be returned when UTL is running.

     

    That is only one part of the problem. I still do not know why the jetways dock on their own AI (their own schedules) and why not with UTL AI aircraft.

    But there you are the professional. I’m just a “technically interested layman”. However, I have been a trained electronics engineer, pc user for 35 years and have been working with the flight simulator since 1994.

     

    Due to my education, I have only learned to circle in an error systematically. However, I have no idea of ​​the programming, of whatever kind. However, if I look at config or xml files, the logic is not completely alien to me.

     

    It also helped me to fix the most common bug in UTL, the multiple startup in p3d – caused by erroneous setup files that caused a multiple entry in the dll.xml and exe.xml. This bug has been officially corrected.

     

    Here, too, the result was achieved in cooperation with the support.

    I hope you also find a way to solve the problem. If necessary, I am quite willing to test a correction.

     

    greetings to switzerland.

    • This reply was modified 5 years, 6 months ago by PilotOne.
    • This reply was modified 5 years, 6 months ago by PilotOne.
    13. November 2018 at 17:05 in reply to: Problem with "Enable AI Traffic Detection" #3041
    PilotOne
    Participant

    In case I forgot to say it:

     

    All tests were done with and without AI-traffic.

    The logfile was created WITHOUT AI traffic.

     

    as far as I can remember, the function “Enable AI Traffic Detection” was the version 1.53 in order. in any case, the UTL ai aircraft were docked with 90% security. I can not say anymore if that was the case with my own airplane. However I would like to avoid the “crash test”, an installation of this “old” SODE-version (1.53), because of my p3d4.3 configuration, as far as possible.

    13. November 2018 at 16:44 in reply to: Problem with "Enable AI Traffic Detection" #3035
    PilotOne
    Participant

    For a better understanding, I’m trying here to send you the screenshots.

     

    Test environment 1, picture 1 and 2. Start state and after opening the SODE menu.

     

    Test environment 2, Figure 5 and 6. Start state and after opening the SODE menu.

     

    The difference is clearly visible.

    • This reply was modified 5 years, 6 months ago by PilotOne.
    Attachments:
    You must be logged in to view attached files.
    13. November 2018 at 16:29 in reply to: Problem with "Enable AI Traffic Detection" #3033
    PilotOne
    Participant

    OK. I have spent hours now to analyze the problem accurately.
    Basically, it does not matter if the AI ​​traffic is active or not or the GSX is avtive or not.

    I deactivated UTL, deactivated the local traffic (own traffic files) and set the P3d aircraft ai traffic to 0 – no difference.

     

    However, there is a huge difference in the flaw between your own scenery and a commercial scene.

     

    Test environment 1:

     

    A private airport that is not included or to be acquired in P3D (non-commercial)

    The jetways (foreign products) were set with the SodePlacer.

    A proprietary ai-traffic was used – the airport does not appear in any UTL traffic file and is not used by UTL either.

     

    Test 1: Enable AI Traffic Detection “true”:

    a) the “own” jetway docks independently.

    b) all other existing AI aircraft dock immediately the SODE Jetways.

    c) when you open the SODE menu, your “own” jetway will suddenly return to its resting position, but remains visible.

    d) in the menu appear the points “dock jetway” and “autodock jetways ”

    e) after activating one of the two points the jetway is docked, but the menu remains and does not show the progress. Also, the option “EXIT” does not appear in the menu.

    f) The SODE menu can only be left via the item “No available Service Facilities found”.

    g) the undocking works, but in the menu the option “undock” is not displayed, only the function “docking”. So the SODE expiration was obviously not recognized that the jetway is already docked.

    h) the menu does not show the progress and stops, the option “EXIT” does not appear in the menu. The SODE menu can only be left via the item “No available Service Facilities found”.

     

    IMPORTANT! Despite this error, all GSX functions – docking and undocking via the GSX menu – remain upright.

     

     

    Test 2: Enable AI Traffic Detection “false”:

    a) the jetway does NOT dock on its own aircraft

    b) All other existing AI aircraft are NOT docking the SODE Jetways.

    c) all menu functions of the SODE menu, docking and undocking, are normal.

     

     

    Test environment 2:

     

    Fly Tampa, Vienna 2.9 LOWW, Gate F09

    The jetways are configured in an xml.file.

    UTL is running, no individual AI traffic.

     

    Test 1: Enable AI Traffic Detection “true”:

    a) the “own” jetway docks independently.

    b) NO other existing UTL-AI aircraft docked to the SODE Jetways.

    c) When you open the SODE menu, your own jetway disappears immediately, it becomes invisible.

    d) in the menu appear the points “dock jetway” and “autodock jetways”

    e) after activating one of the two points nothing happens.the menu remains and does not show the progress. Also, the option “EXIT” does not appear in the menu.The SODE menu can only be left via the item “No available Service Facilities found”

    f) if you open the SODE menu again, only the (ativating)item “autodock jetways” will be displayed – not the item “dock jetways”.

    g)if the function “autodock jetways”, as the only possible option, is operated, does not happen. Instead, the menu item “Unable to perform automatic docking!” Appears.

    h)The SODE menu can only be left via the item “No available Service Facilities found”.

    i)The invisible jetway can only be made visible via the function “reload all”.

     

    IMPORTANT! When using the GSX function via the GSX menu – docking and undocking – the jetway also disappears immediately, but it only seems to become invisible.

    The GSX menu always reports the execution of the command and completion with “jetway docked” or “jetway undocked.” Sure, nothing happens that you could see.

     

     

    Test 2: Enable AI Traffic Detection “false”:

    a) the jetway does NOT dock on its own aircraft

    b) All other existing AI aircraft are NOT docking the SODE Jetways.

    c) all menu functions of the SODE menu, docking and undocking, are normal.

     

    IMPORTANT! All GSX functions – docking and undocking via the GSX menu – remain upright.

     

     

    I added the SODE log as desired.

     

    I only started P3d here and selected my own airport (Test environment 1).

    After the appearance of the scene, NOTHING was operated or changed. It was just the jetway automatically docked. P3d was immediately closed again afterwards..

     

     

    If there are any grammatical errors, please excuse me. The text was translated by google from German into English.

    Attachments:
    You must be logged in to view attached files.
    12. November 2018 at 18:34 in reply to: Problem with "Enable AI Traffic Detection" #3020
    PilotOne
    Participant

    No, the “Enable Aircraft State Triggered Auto-Docking” function was always disabled.

    The self-docking effect occurs whenever the “Enable AI Traffic Detection” option is enabled. Interestingly, the AI ​​aircraft are not docked, their Jetways remain in the rest position.

     

    I use the SimConnect 10.0.61259.0 SP2 / X_Pack and the AI ​​traffic Ultimate Live. I also have GSX and GSX Level 2 in use.

     

    Test Airports used: Fly Tampa Vienna 2.9, LOWW, Gate F09 and JustSim Brussels P3D4, EBBR, Gate 146, each with a PMDG 737/800 WL.

    The airports have their own SODE jetways with their own configuration files.

     

    At first I thought the problem came from GSX. But I completely uninstalled it and the error was the same. I have then uninstalled and reinstalled everything – GSX, GSX2, SODE, so that any malfunction of a possibly damaged DLL file is excluded. The error is clear and always reproducible.

     

    I did the tests (20, 10 per option) with uninstalled GSX and GSX2. Only SODE was installed.

    • This reply was modified 5 years, 6 months ago by PilotOne.
  • Author
    Posts
Viewing 13 posts - 1 through 13 (of 13 total)