Read this Checklist: Check before your 1st flight
- Could be a Virus scanner/Security suite issue, maybe check if swift needs some permission there
- Firewall, ports open ....
- if you see something like "ASSERT failure in QList <T>::operator "index out of range", file C:\QT\5.12.0\msvc2017_64\include\ Qtcore/qlist.h,line 552" your settings could be corrupt, solution Reset the screen size
- sometimes it can help to uncheck and check again the simulator again (simulator settings)
- could be that the screen geometry values are incorrect, see Reset the screen size
- or even Delete swift registry values (Windows only)
- also we had people having issues with
- malware protection
- recently some reports with TrueImage Active protection came up (that blocking swift)
- Troubleshoot voice (no ATC, no MIC, no sound, sample rates, WASAPI)
- MacOS user? See No sound on macOS (loopback not working)
- Windows: Microphone not working on Windows
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.
- I only see "Constellations". Most likely you have no model set, an improper model set, see Model set - creating or recreate a model set
- If the simulator does NOT connect, see Configure / select the used simulator, P3D version FSX version
- make sure you have the correct swift version, Which version to install, 32 bit or 64 bit installer?
- If you cannot connect the simulator and swift: If you run P3D "as admin", run swift "as admin"
- make sure you use the correct P3D driver version. If this version does not (yet) exists, selected the version which comes closest.
- Warn of XSquawkBox/xPilot conflict
- XSwiftBus doesn't work properly if xsquawkbox or x-ivap is also installed since only one can have control of X-Plane multiplayer aircraft. swift will raise a warning in case another plugin is controlling the multiplayer aircraft.
- Remove or disable the conflicting plugin and restart X-Plane. Plugins are still loaded even if they are disabled. Disabled just means that any callbacks registered by the plugin will not be called. Some people have to remove the plugins from the folder, some do not.
- Maybe you consider a 3rd party tool like XPlane plugins xOrganizer
- 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. Moving the XPlane models might require to reload your swift model cache, then recreating the model set.
- 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
- Aircraft animation as gear down not working:
- There are some known conflicts with other XPlane add-ons as those keep common multiplayer animation datarefs (being shared between all pilot clients) locked and the swift dataref registration fails.
- In order to resolve the problem move the conflicting plugin out of your plugin folder and restart. The conflict is known to cause trouble with gear animations and such.
- Problems with the following plugins have been reported: all other client plugins like XSB, x-ivap, fscloud, fs2play
- FS9 needs two connections: DirectPlay Multiplayer and FSUIPC since DP MP doesn't have all required details
- DirectPlay is auto connected if swift runs on the same machine and has been properly installed (adding itself as "lobby-able" application on windows registry)
- See Connecting FS9 manually through multiplayer
- When you run FS9 as admin, then FSUIPC isn't connecting, because swift running as non admin blocks the connection. Run both as admin.
- Some people have have reported issues with models not from the aircraft folder of FS9
- some users have problems with the auto-connect to FS9 since Win10 1909 update, see Connecting FS9 manually through multiplayer
Not validated: Installation in Application failt, but in XPlane directory it works.
I keep getting the following in the log
I was able to connect a few days ago now I dont know what is different.
When I open up swift it goes through the initial boot stuff in the log then I keep getting this over and over
FSUIPC Connected : FSUIPC 126.96.36.199z (FS2004)
Closing FSUIPC : FSUIPC 188.8.131.52z (FS2004)
Now I cannot connect my sim computer through the FS multiplayer portal and swift is not picking up the sim.
I have my FS9 running on a win xp machine
Swift is running on a win 7 laptop.
WideFS is running on the win 7 laptop
And is registered along with FSUIPC on the sim computer.
Both are connected to the same wifi router
I have both computers in a workgroup called FLIGHT.
I have looked through the troubleshooting guides and done what has been said to try and I still get the same result.
I am stumped as to what has changed.
Any help would be appreciated.