Troubleshooting Swifty 2.X.X Legacy Build

This is a troubleshooting FAQ for Swifty 2.0 Builds. This guide is not compatible with 3.0 Builds. We Currently only support 2.X.X builds.

Log files

Swifty log files can be found in your Appdata. To easily find this folder type %Appdata% into your windows search bar. This will put you into your Appdata/roaming folder.

The full Path to the swifty log is as follows: C:\Users\username\AppData\Roaming\Swifty

You will then see a text document titled swifty. This is your log file! Simply open it in notepad to read it. If you do not know what to look for yourself, toss the file straight into our tech support channel in discord.

Cache folder

This folder holds files that allow swifty to know the status of each mod it has downloaded. If you have an error that is the result of a corrupted file, its best to clear this cache to ensure it is redownloaded.

again this is found in appdata. The full path is: C:\Users\username\AppData\Roaming\Swifty\Cache

inside you will see subfolders for every repository you have.

Temp directory

Swifty uses the temp directory to download the files it needs, and then patch them into the existing folders. Ensure you have enough space on the drive you chose for this, as sometimes it can temporarily use several gigabytes of space.

If a download suddenly stops, you may need to clear these files to ensure no corrupt files are moved into your mod directory.

You can find where you set this directory to under the wrench icon.

Error messages

Data file too short

While a fault with swifty is causing this, its actually an ArmA Launch error. This error occurs even if your mods appear to match the repository and swifty reads green. The cause is unknown, but the result is one or more corrupt files that didn't fully download. More often than not, multiple files are gonna cause this if one already did.

The best solution we currently know of for this error is to pay attention to the exact size the file says it is. For reference the full error message will be similar to the following:

Data file too short
'C:\Users\username\documents\COALITION\@Terrains\addons\Blud_cordelia.pbo'. Expected 298037572 B, Got 140834460 B

This example is telling you that the game expected one of the map files to be 298mb in size but since it's corrupt, it's only 140mb. 140.083446mb to be exact. So you can look for files in the same mod, in this case @terrains that match that exact size. These will be your problem files. Delete them.

Now, instead of rerunning swifty because it will likely just repeat the same error. You can download these specific files directly from the repository one at a time by going to the repository address in your internet browser.

http://coalitiongroup.net/repo/

Ran out of file

This error is a catch all. The most common causes are as follows:

• Too many parallel downloads, set this setting to 1 or 2. Especially if you are on wifi.

• Unstable, but not total loss of connection. This results in a corrupt file that you must check your log to find. You can then delete that file, clear your temp and cache folders and try again.

Ran out of memory

This means you either do not have enough space at your install directory, or not enough space at your designated Temp location.

System exception: Could not connect to repository

Double check to make sure you are using the correct repository address and there are no spaces before or after the address.

If the address is correct it is likely the repository is down while being updated.

If you still get this error and have checked with us to ensure the repository is up, you may have something blocking your connection to our server.

System exception: failed to download

This means the connection to the server was lost at some point. Restart your download and try again.

System nullreference

This is the result of clicking "New" instead of "Import" when inputting the Repository information.