Read this Checklist: Check before your 1st flight
If you see messages like No network access point or No network and you are using WIFI then you likely suffer from a Qt bug. In some versions the Qt framework (the library swift uses) is broken. Qt has promised to fix that. However, you can try the following workaround. In your swift installation directory you will see a directory bearer, just remove this directory and try again.
- Warn of XSquawkBox conflict
- XSwiftBus doesn't work properly if xsquawkbox is also installed. Ideally XSwiftBus could detect this situation and somehow tell the user "please disable/remove xsquawkbox".
- For reference, the conflicted state is: XSwiftBus is available in the plugins menu, and the moment you hit "start server on session bus", then the swift gui shows "Simulator plugin loaded: X-Plane", and Settings/Simulator/Loaded goes from "No plugin" to "Support for the X-Plane simulator via the XSwiftBus plugin" but nothing else works: the gui's "sim" light remains off, the radio and transponder are not synchronised between GUI and x-plane; the aircraft type does not fill in even if you change it after connection.
- Bluebell CSL models sunken in ground (vertical offset fix) , see XPlane aircraft too high or too low (wrong offset/CG)
- XPlane models in model set, but not rendered. Solution: CSL files need to be inside the XPlane folder
- swift cannot connect to XPlane simulator side plugin: Check if the settings of the swift side and XPlane side do match, XSwiftBus settings. If the simulator LED is "on" the simulator can be connected:
- HINT: Some users did have problems with spaces in their model directory paths
Not validated: Installation in Application failt, but in XPlane directory it works.