CumulusX!
Discussion related to all aspects of this exciting new program that puts thermals in FSX and creates ridge lift using CCS slope files.
170 topics in this forum
-
- 3 replies
- 2.2k views
-
- 3 replies
- 1.9k views
-
- 3 replies
- 2.3k views
-
- 3 replies
- 5.8k views
-
- 3 replies
- 1.3k views
-
- 3 replies
- 7.2k views
-
- 3 replies
- 5.2k views
-
- 3 replies
- 5k views
-
- 2 replies
- 1.9k views
-
- 2 replies
- 1.5k views
-
- 2 replies
- 1.6k views
-
- 2 replies
- 1.4k views
-
- 2 replies
- 1.6k views
-
- 2 replies
- 1.6k views
-
- 2 replies
- 2.1k views
-
- 2 replies
- 2.3k views
-
- 2 replies
- 3.8k views
-
- 2 replies
- 2.2k views
-
- 2 replies
- 2k views
-
- 2 replies
- 2.3k views
-
- 2 replies
- 2.3k views
-
- 2 replies
- 2.1k views
-
- 2 replies
- 1.8k views
-
- 2 replies
- 1.8k views
-
- 2 replies
- 1.8k views
-
Popular Topics
-
-
Latest Posts
-
Thanks Ben - I assume they will tidy up the software when the action slows down a little. Hope you enjoy fair skies and plenty of daylight under your wheels - Cheers Pete -
The SODE Jetways for Sim-wings LEPA are developed based on the roles of the SODE SDK and connect correct to any Aircraft, where the aircraft.cfg or the Sode "AircraftExits.ini" below C:\ProgramData\12bPilot\SODE has the correct offset for the base of the doors. In your case it looks like the [EXITS] Values in the aircraft.cfg are set correct to the center of the door (thats the standard for all Ctrl+J Jetways, but the Aircraft exits are not correct in the Sode AircraftExits.ini, as Sode needs the coordinates set to the base of the exit. When SODE don't find this values it may connect based on the aircraft.cfg values, so that the base is in the middle of the door. My Values in the AircraftExits.ini for the Aerosoft Airbus looks like this: [Aerosoft:A318] exit.0 = 0.4, 28.5, -6.5, 0.0, 0 exit.1 = 0.4, 28.5, 6.5, 0.0, 0 [Aerosoft:A319] exit.0 = 0.4, 30.0, -6.5, 0.0, 0 exit.1 = 0.4, 30.0, 6.5, 0.0, 0 [Aerosoft:A320] exit.0 = 0.4, 35.5, -6.5, 0.0, 0 exit.1 = 0.4, 35.5, 6.5, 0.0, 0 [Aerosoft:A321] exit.0 = 0.4, 45.15, -6.5, 0.0, 0 exit.1 = 0.4, 45.15, 6.5, 0.0, 0 -
.. da hast du recht, aber wenn man mit X-Plane rumwerkelt, sollte man sich sowieso tiefergehende Kenntnisse aneignen, damit das ganze Freude macht.... nicht so wie bei anderen "Simulatoren", wo man dumm bleiben darf 😉 -
Den Flughafen "Hersteller" angehen und um Korrektur nachfragen. Hast Du mal ein Beispiel für solche Abweichungen? -
... also ich hab das mit dem Einschalten der Strobe-Lights verbunden und mit einem kleinen LUA-Script gelöst: das LUA-Script: if (PLANE_ICAO == "B738") then function zibo_strobe_lights_on() command_once("laminar/B738/toggle_switch/position_light_up") command_once("laminar/B738/toggle_switch/position_light_up") command_once("laminar/B738/toggle_switch/position_light_up") command_once("laminar/B738/knob/transponder_mode_up") command_once("laminar/B738/knob/transponder_mode_up") command_once("laminar/B738/knob/transponder_mode_up") command_once("laminar/B738/knob/transponder_mode_up") command_once("laminar/B738/knob/transponder_mode_up") end function zibo_strobe_lights_off() command_once("laminar/B738/toggle_switch/position_light_up") command_once("laminar/B738/toggle_switch/position_light_up") command_once("laminar/B738/toggle_switch/position_light_down") command_once("laminar/B738/knob/transponder_mode_dn") command_once("laminar/B738/knob/transponder_mode_dn") command_once("laminar/B738/knob/transponder_mode_dn") command_once("laminar/B738/knob/transponder_mode_dn") command_once("laminar/B738/knob/transponder_mode_dn") command_once("laminar/B738/knob/transponder_mode_up") end create_command("Zibo/StrobesOn", -- Schalter 9 (links) "Zibo Turn on StrobeLights", "zibo_strobe_lights_on()", "", "") create_command("Zibo/StrobesOff", -- Schalter 9 (links) "Zibo Turn off StrobeLights", "zibo_strobe_lights_off()", "", "") end dann einem Schalter dem Strobe-Lights zugeordnet (hier Schalter 9):
-
