Forum Replies Created
-
Posts
-
simconnect.log file is very useful for errors concerning lauching of SODE: FAQ, Section D.
Hello
From a technical point of view, there is no such thing like “SODE objects”, it is still a standard FS MDL object which is injected into the sim by SODE (think of injection of an AI aircraft). So the entire rendering is handled as for any other injected MDL object and this is done by the FS rendering engine of course. Nothing I can fix.
P3D with its new Enhanced Atmospherics did introduce some incompatibilities with materials and such, so I guess re-exporting the model/material parameters could possibly solve the problem. But this must be done by the model developer as they are way more knowledgeable in these matters.
Best regards
Hi Jaap
Just checked at ICAO’s official database of aircraft identifiers: https://www.icao.int/publications/doc8643/pages/search.aspx
The proper ID is BCS1 resp. BCS3, even though they are now commercially designated as Airbus A220-100 and A220-300.
SODE uses the ICAO definitions (which is also intended to be used in the aircraft.cfg according to the FS SDKs).
So changing the IDs to BCS1, BCS3 should make the VDGSs light up correctly.
Best regards from Switzerland
Jeffrey
I guess you already tried to uninstall/re-install the VDGS pack?
Can you post the sim.cfg file from here: C:\ProgramData\12bPilot\SODE\SimObjects\SODE_VDGS ?
Thanks for the aircraft.cfg file.
Just tested it with the parsing code of the AI object part of SODE: The aircraft.cfg is correctly parsed and the exit is read.
So there must be something else. Could you post the entire SODE.log perhaps?
The message appears when SODE is not able to parse the exit data from the AI’s aircraft.cfg.
What does the whole [Exits] section look like exactly within your aircraft.cfg?
Is the VDGS pack listed in “Apps & Features”? I guess it is not installed properly, otherwise, SODE would pick it up during launch.
Hi Henri
Here’s a list of supported aircraft types: https://sode.12bpilot.ch/?document=visual-docking-guidance-system-vdgs
The MD80 – MD83 are supported.
You can also see in that table, that those aircraft belong to the group “ALL_REGIONAL”.
So, in the xml for the airport where you get the error message, the stop position for your aircraft must be defined either with the explicit type specifier (MD80, etc) OR the group name “ALL_REGIONAL” OR the master category “ALL_AIRCRAFT”.
-Jeffrey
I don’t have the WFSS Hong Kong and neither DD RJAA, so can’t really help.
Since the SODE VDGS works at RJAA, it is not something fundamentally wrong with SODE VDGS together with the FSL A320/A321.
Could you post a SODE.log file (C:\ProgramData\12bPilot\SODE\log)? Maybe the Stop positions have wrong aircraft types defined, I don’t know.
Looks like a Java issue to me…
Can you try V0.7? https://sode.12bpilot.ch/?topic=sodeplacer-0-6#post-5094
This was compiled with a newer Java version.
Hi,
I have detached your question from the other topic, since it had nothing to do with your question.
Can you post your SODE.log please? C:\ProgramData\12bPilot\SODE\log
And where do you see this message? In the SODE menu window or in the green line that shows up at the top of the simulator? Are you able to select any gate in the menu? Screenshots would help.
Hi, finally found time to inspect the log.
Flightbeam_KDEN.xml is clearly loaded by SODE, so that’s not the problem.
But it seems that the path to the folder which contains the SimObjects for all the SODE add-ons is not present in your fsx.cfg!
When you start SODEPlatformManager.exe, does the “FSX” section show two green fields?
In any case, you can inspect your fsx.cfg. The [Main] section should contain the two necessary paths used by SODE. For example my fsx.cfg looks like this.
[Main]
DisablePreload=1
User Objects=Airplane, Helicopter
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6=D:\FSADDONS\FLIGHT ONE SOFTWARE\ULTIMATE TRAFFIC LIVE\utLive Aircraft
SimObjectPaths.7=D:\FSAddons\SODE_External\SimObjects
SimObjectPaths.8=D:\FSAddons\Addon Manager\Simobjects\Misc
SimObjectPaths.9=D:\FSAddons\Addon Manager\Simobjects\Legacy
SimObjectPaths.10=C:\Program Files (x86)\12bPilot\SODE\data\SimObjects
SimObjectPaths.11=C:\ProgramData\12bPilot\SODE\SimObjects
The last two are the ones needed. Just adjust the path to where you have installed SODE to.
Hi,
Could you please attach the SODE.log? -> C:\ProgramData\12bPilot\SODE\log
This will give me some info. I have never heard of that problem before.
Hi,
1) In the log, just a couple if lines above your pasted lines, you can see where the SimObject paths are extracted from. (simobjects.cfg, add-ons.cfg, fsx.cfg -> Depending on the simulator). In those files, the paths are defined, so the AI traffic simobject container path is also defined somewhere in there.
2) You need to find the corresponding SimObject container path for those objects with the SimTitles displayed in the log (again, those paths are found in one of the files mentioned above). If you really don’t need that container path anymore, delete it. Since you say you don’t have the corresponding xml anymore, then those SimObject containers really are not needed anymore.
Hallo Manfred
Ansonsten gerne auch auf Deutsch.
Ein Eintrag in der AircraftParameters.ini ist nicht notwendig damit die Jetways docken. Die Parameter definieren eigentlich nur die Geometrie der jeweiligen Türe, damit die Haube möglichst bündig an der Türe abschliesst. Ohne Eintrag fährt die Brücke trotzdem ran, die Haube wird dann einfach nicht sehr präzis animiert.
Die Grundvoraussetzung für das Jetway-Docking ist eine definierte Exit Position in der aircraft.cfg Datei (sowohl User so wie auch AI Flugzeug). Sollte keine solche Position definiert sein, kommt die SODE AircraftExits.ini Datei als “Backup” ins Spiel: Diese definiert für gewisse Payware Flieger (korrigierte) Türpositionen.
Aber wie gesagt, eine korrekt definierte Exit Position in der aircraft.cfg genügt eigentlich, und diese sollte eigentlich auch für AI Flieger vorhanden sein. Es kann aber auch sehr gut sein, dass diese Exits für AI Flieger explizit *nicht* definiert wurden! So wurde teilweise verfahren, damit die default FS jetways (IK-Jetways) nicht an die AI Flieger andocken, weil diese default Jetways die Framerate sehr belasten.
Lösungsvorschlag also: Überprüfen der aircraft.cfg der in Frage kommenden Flieger ob diese den Eintrag haben.
Grüsse aus der Schweiz
Jeffrey