Subset Games Forum

Very good editor, i use it to make alot of mods, but please, for the love of god, add a feature to select multiple things or im gonna go insane >~<

To all those who are still struggling to get Superluminal working with version 1.6:

FTL on the Humblebundle Store is still at version 1.5
If you get it from that site you can save the resources folder and continue to use Superluminal as it was before. The finalized custom ships can then be placed into the Slipstream Mod manager and be played in your FTL 1.6 game.

I know that isn't a prime solution but it's better than nothing.
The two files I liked in my last post are the only contents of the original Resources folder.

Before you buy on Humblebundle, Try downloading the files I linked and then create a folder in Programfiles(x86) called FTL. Inside of that folder put a folder called resources, and place both files inside. Then start up Superluminal and see if it can locate the files in there. (I am not 100% sure this will work but it is the best representation of the file structure you will get if you download another previous version of FTL from Humble).

Best of luck to all of you

For those of you who still like to mess around with modded FTL, I've just uploaded a new release to make the editor compatible with the newest version of the game. From the limited testing I have done everything seems to be working correctly, but do let me know if I've missed something. Ships saved with this version of the editor should be compatible with both new and old version of FTL.

Download: Superluminal 2.2

kartoFlane wrote:From the limited testing I have done everything seems to be working correctly, but do let me know if I've missed something.

By chance could you get Superluminal on windows to recognize java 9 as java? Trying to run it with only java 9 installed prompts a page to get java 8 update 161. Slipstream fixed this in v1.7/1.8, and judging by its changelog it looks like a simple fix?

Vhati wrote:v1.8 has been released:
...
[*]Fixed Windows exe launchers not finding Java 9.
...

mr_easy_money wrote:By chance could you get Superluminal on windows to recognize java 9 as java? [...] Slipstream fixed this

All I had to do was rebuild my executables with a newer release of Launch4J.

Java 9 changed its versioning scheme and started using different registry entries to announce its presence, so the launcher needed to be updated to find it.

I knew I missed something... Thanks for letting me know, and thanks for the answer Vhati! I've updated the release on GitHub -- simply redownload the editor.

Three bugs to report,

I loaded a ship mod created with the previous version of Superluminal (arfy's Hazmatian) into Superluminal via File -> Mod Management. When I tried to save the ship as an .ftl file, I got the following error log,

I assume this is because the 1.6 editor saves text in the new text_blueprints.xml.append file, but doesn't recognize text in the old format i.e. directly in the tag (which still works).
----------
the other bug

Let's say I open Superluminal, create a custom ship that'll replace the kestrel a, save it as an ftl file, and close the ship. If I then use Mod Management to load the mod in, and then create another custom ship that'll replace the kestrel b, save it as an ftl file and include mod files from the mod I loaded in (the ship that replaces kestrel a), it'll save and all looks well.

However, upon opening the blueprints.xml.append file, I noticed that the ship replacing kestrel a will lack its opening and closing <shipBlueprint> tags, which is problematic. I presume this happens because Superluminal sees it as a "root" tag when loading mod files containing only one ship.
----------
;edit; another bug

When using Edit -> Generate Floor Image and selecting a color for the border or floor, picking a color via the visible color picker or setting HSB values works fine, however trying to set RGB values causes Superluminal to crash (the error makes it pretty obvious the problem, with the range only being able to be between 0 and 1.0, though it doesn't auto-max either like when setting HSB values

as does a hex triplet (e.g. #FFFFFF), for the same reason (range only being able to be between 0 and 1.0, doesn't auto-max either like when setting HSB values)

oh unrelated, but it looks like the error message, "An unexpected error has occured and the editor was forced to terminate." has a typo on the word 'occured', should be 'occurred'.

Good stuff, thanks for reporting! I've released a new version to address these bugs.

Download: Superluminal 2.2.1

Changelog:

Update is much appreciated and I've encountered no issues, thank you

It just keeps crashing please help!