Jump to content

Systems

Hydraulics, Pneumatics, Electrical etc... Please post only one issue per post so we can follow up, do not post a list of question!


571 topics in this forum

  1. Question to CPDLC

    • 1 reply
    • 601 views
    • 7 replies
    • 964 views
    • 3 replies
    • 626 views
  2. A330 first impressions 1 2

    • 25 replies
    • 3.2k views
  3. Altimeter Warning

    • 3 replies
    • 786 views
  4. Fire warning bell

    • 2 replies
    • 671 views
  5. Fire Test 2.

    • 4 replies
    • 598 views
  6. A330 refuel midair

    • 11 replies
    • 1.7k views
    • 11 replies
    • 1.4k views
  7. Radial Fix Info

    • 6 replies
    • 1k views
  8. PDF window

    • 2 replies
    • 762 views
  9. Windshear

    • 1 reply
    • 781 views
  10. PFD secret function

    • 4 replies
    • 910 views
    • 11 replies
    • 2.8k views
    • 7 replies
    • 2.5k views
  11. Hyd Elec Pump

    • 2 replies
    • 929 views
  12. Fire Test

    • 2 replies
    • 717 views
  13. MCDU causes CTD

    • 2 replies
    • 682 views
    • 5 replies
    • 1.4k views
    • 4 replies
    • 679 views
  14. FCU Not Illuminated

    • 4 replies
    • 728 views
    • 1 reply
    • 799 views
    • 12 replies
    • 2.6k views
    • 5 replies
    • 1.3k views
    • 2 replies
    • 1.9k views
  • Popular Topics

  • Latest Posts

    • Hallo Thomas,   über den Honeycomb-Configurator kannst du dir spezifische Flugzeug-Profile für die Verwendung in XPlane einrichten, die du jeweils über den Honeycomb-Configurator "aktivieren" musst. Dein "meine.json"-File ist das Script, das per "Activate" die Konfiguration des Alphas und Bravos in XPlane vornimmt. Du musst also vor Beginn deiner XPlane-Session über den Honeycomb-Configurator das jeweils passende Profil laden, XPlane selbst kann mit "meine.json" nichts anfangen. In meinen Augen ist das Konzept des Honeycomb-Configurators viel zu umständlich: Avionics Bus 2: sim/cockpit2/electrical/cross_tie lässt sich ja direkt in den XPlane-Einstellungen für den Alpha zuweisen. Überhaupt wird für den Alpha der Honeycomb-Configurator gar nicht benötigt, weil alle Einstell-Varianten direkt in XP12 erfolgen können. Anders sieht das beim Bravo aus.   Ich verwende für meinen Bravo die PlugIn-Lösung von Jorge Uvo: https://forums.x-plane.org/index.php?/files/file/89635-honeycomb-bravo-plugin/ Diese Lösung ist für alle Betriebssysteme verwendbar und macht alle Einstellungen für den Bravo direkt in XPlane verfügbar. Es müssen lediglich die mitgelieferten File nach ../joystick configs/ verschoben werden (vorhandene Files überschreiben) und das FlyWithLua-Script installiert werden. Damit können dann der Alpha und der Bravo vollständig innerhalb der XPlane-Systematik konfiguriert werden. Noch schöner ist, dass sich über das FlyWithLua-Script ganz spezielle Anpassungen vornehmen lassen.          
    • Correct. This is also being mentioned in the documentation in the file "CRJ Flightplan Format.pdf"
    • As it turns out, I had been saving the flightplan to the wong location. This is where I they need to be saved to: C:\Users\MYNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\aerosoft-crj\work C:\Users\MYNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\aerosoft-crj\work
    • Vielen Dank, das ist ja grandios. Da kann man ja tagelang spielen. Habe diese Taste jetzt nach meinen Wünschen belegt sehe auch in der Datei Xplane... / honeycomb_profiles/ meine.json   aber wie kriege ich das in xplane zum laufen. Ich kann das Profil in Xplane nicht auswählen. Hoffe ich drücke mich verständlich aus.   Beste Grüsse Thomas  
    • The scenery is a valid XP12 scenery, WED reports some warnings and most of the have been solved internally already - anyway, this is not really an issue and this is not rendering it an 'invalid XP12 scenery'.     Overlapping parkings are not necessarily an issue if those are configured correctly. For realism we have to do this and we did this for years because the real world stands of the airport are in fact overlapping too and we can't just drop most parkings for avoiding overlapping. If configurations are messed up I will fix them for sure but I won't remove parking spots that have to be there just because of overlapping.     That's one of those configuration settings one can use to have a ramp present without having stattic or AI traffic aircraft using those parking, it's one possible solution to have parkings overlapping without causing issues.     The manual is the old XP11 manual, we did not create new ones because those are actually not needed at all as installation is done by Aerosoft One or other installers these days - anyway, this is not affecting the airport itself and a decision made by project management.     It should not be like that but I will check if I can reproduce this, in out testing this was fine and I did not see any issue when adjusting the effects. Do you mabe have a screenshot to share with me so I can see if something is wrong?     That's out of scope currently - we can't just replace custom made scenery jetways with generic white ones from the XP library. Anyway, the airport should work without SAM installed, if this does not work right (loading issues or signs showing up telling you to install latest SAM) please use my Fallback Library to solve this for now.   As far as I get this SAM is still working fine in XP12 aside from the crash on sim closing and a compatibility issue with DataRefTool (which is not necessary to be installed for normal simulator use) and it should not cause any RAM issues even on longer flights (never heard of something like this). Both of these issues mainly affect developers who are starting and closing the sim often for testing their stuff and also need a DataRef tool but SAM should not ruin normal users' experience completely. For normal users I recommend to remove DataRef Tool for now and for developers remove SAM instead (both can be done by simply moving the plugins to a "plugins disabled" folder and then activate and deactivate them as needed, this is how I deal with the situation myself).   Finally, the SAM situation is currently being investigated by project management and I have some hopes there will be a solution for this at some point in time.     Anyway, thanky you for your feedback, I will take this into account for the next LSZH update and fix things as needed.   🙂              
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use