- Ftl faster than light repairing install#
- Ftl faster than light repairing update#
- Ftl faster than light repairing Patch#
- Ftl faster than light repairing mods#
Your computer does not like the default renderer FTL uses, so you should add -directx as a launch option this can be done in steam by just going to its properties and adding it there, but you can also do it in a shortcut by adding it to the end of the target textbox in its properties, after the quotation mark and with a space in-between (and then launching with that shortcut). Symptom: FTL seems to crash on load with a mysteriously empty white box (that is labeled as a MingW Runtime Error) You have a non-Steam version of the game, in which case you need to use that version's downgrader (also found on the forums) or an alternative method (in the case of GOG, using GOG Galaxy to select 1.6.9 for example).
Ftl faster than light repairing Patch#
If this is the case, try manually running the patch using flips (go to the patch folder, run flips, select "apply patch", select the patch, at the bottom right change it to "all files" and select FTLGame.exe, then name the file whatever, then rename the original FTLGame.exe to something else and rename the new file to that). You ran the downgrade.bat, but it simply didn't work. You ran the downgrade.bat, but it wasn't in the right place (it should be in the same place as the exe, not inside the folder it came in). If this is the case, just make sure you copied it (and the other hyperspace files) to the folder. You simply haven't ran the downgrade.bat (included with the hyperspace zip). This means that you haven't downgraded correctly this could be for a variety of reasons, such as: Symptom: The game never loads, giving an error that mentions failing to find an address for GetShipAchievements This could be due to not patching Multiverse in slipstream (make sure it's checked and then hit patch), or due to patching a secondary copy of the game if the latter is the case, just change the target in slipstream's preferences to the FTL.dat in the folder of whichever copy you're running. Symptom: Vanilla FTL is running (or appears to be running) instead of Multiverse/Hyperspace The easiest way to check for this is to verify the game files in Steam, or for non-steam, grab a new copy of the game, and then delete the in Slipstream's backup folder (and reinstall hyperspace in both cases). Slipstream's backup and/or FTL are outdated, causing it to fail. Make sure your Slipstream is version 1.9.1. Slipstream is outdated, causing it to fail when patching. This can often be resolved through a redownload of Multiverse if this is the case. Multiverse itself has been messed up somehow, be it from extracting/zipping the folder incorrectly, a corrupted download, etc. There are a few different reasons this may be: Symptom: Multiverse fails to patch for whatever reason
Ftl faster than light repairing mods#
If Multiverse is seemingly in a bunch of folders like audio/img/data instead of a zip, you've extracted the zip instead of just putting the zip in Slipstream's mods folder either take the original zip and put it in the mods folder, or zip up those folders into a zip yourself and do the same! You'll have to restart Slipstream after doing this but it should show up afterwards! ftl files (and they're both the same thing anyways, just renamed to make it clearer which type is for what). Symptom: Multiverse doesn't show up in Slipstream despite being in the mods folderĮnable the "allow_zip" option in Slipstream's preferences this will let Slipstream see.
Ftl faster than light repairing update#
If I've forgotten anything, I'll update this post as needed.
Ftl faster than light repairing install#
This post also assumes you're trying to install this on Windows, as the Linux install has pretty inconsistent issues that we haven't been able to resolve successfully (although some shady solutions have worked for a few people.), and the Mac install is Windows but worse, considering it can't use WINE anymore and the best solution tends to be a virtual machine. If you're completely fresh, my recommendation is Baertaffy's install guide ( ) but leaving Hyperspace.ftl unpatched instead of patching it before MV (if you're installing MV, otherwise patch it) as it's pointless and can cause issues if you get it wrong. This post assumes you've already followed either the official install guide on the forum or one of the various youtube guides out there, and that you sorta kinda know how FTL modding works (using slipstream, putting the mods in slipstream, etc), although if that's a common issue I can add that here too. Hey there! I'm one of the Hyperspace devs and I figured what the community needed was a big troubleshooting guide for Hyperspace/Multiverse that catalogs most of the specific issues I've seen, since install guides alone aren't always enough.