Slipstream Mod Manager v1.9.1 (2018-01-07)

[ironhideforever]

SMM does not work for me.

Both the modman.exe and the modmanadmin.exe just flash for a second. The .jar file seems to work, opening the program and seemingly patching the mods into the game, but then there are no mods present in game.

I've seen some suggest that I should be opening it from the .jar file, and others suggest to not do that, but neither of those options seem to work.

Java is up to date, and I am not getting any error messages, so I have no idea what the problem is. Using AE, so I suppose it could be related to that in some way?

I've seen other users describe things that sounded like these issues, but I haven't been able to find anything similar or a solution.

Any ideas would be much appreciated!

[kartoFlane]

Looks like it's crashing at startup, but it's difficult to say anything more specific without the error log. Find modman-log.txt in SMM's folder, and post its contents here, between [ code ][ /code ] tags.

[ironhideforever]

Looks like it's crashing at startup, but it's difficult to say anything more specific without the error log. Find modman-log.txt in SMM's folder, and post its contents here, between [ code ][ /code ] tags.

Thanks for the reply. This is the only thing that shows up in the log.

Code: Select all

 19:13:32.804 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Slipstream Mod Manager v1.6
19:13:32.805 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Windows 7 6.1
19:13:32.805 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Java HotSpot(TM) Client VM, 1.8.0_25, x86
19:13:32.843 [AWT-EventQueue-0] INFO  net.vhati.modmanager.FTLModManager - Using FTL dats path from config: E:\gog\bg2gamedir\FTL - Advanced Edition\resources
19:13:33.335 [Thread-4] DEBUG net.vhati.modmanager.ui.ManagerInitThread - Catalog isn't stale yet.
19:13:33.339 [Thread-4] DEBUG net.vhati.modmanager.ui.ManagerInitThread - App update info isn't stale yet.
19:13:33.344 [Thread-5] INFO  net.vhati.modmanager.core.ModsScanThread - Background hashing finished.
19:13:33.344 [Thread-5] INFO  net.vhati.modmanager.core.ModsScanThread - Background metadata caching finished.
19:13:37.430 [Thread-6] INFO  net.vhati.modmanager.core.ModsScanThread - Background hashing finished.
19:13:37.430 [Thread-6] INFO  net.vhati.modmanager.core.ModsScanThread - Background metadata caching finished.
19:14:04.899 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame - 
19:14:04.899 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame - Patching...
19:14:04.900 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame - 
19:14:04.904 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - Restoring vanilla "data.dat"...
19:14:05.081 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - Restoring vanilla "resource.dat"...
19:14:30.595 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - 
19:14:30.595 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - Installing mod: 03_K64_Firefly_v1.1.ftl
19:14:31.232 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - Repacked "data.dat" (155929 bytes affected)
19:14:31.251 [Thread-8] INFO  net.vhati.modmanager.core.ModPatchThread - Repacked "resource.dat" (625832 bytes affected) 

[agigabyte]

How do I save as a .shp?

[agigabyte]

How do I save as a .shp?

[NarnKar]

@agigabyte: such questions are better asked in the Superluminal thread, since it's a Superluminal format. Well, was, anyway. It used to be a file format for unfinished FTL ships, but was since dummied out; it can only be opened in new versions of SL, and no longer saved.

[agigabyte]

Ah, how do I open .ftl files?

[kartoFlane]

@agigabyte
See FAQ.6

@ironhideforever
Well, the info in this log is telling me that SMM has launched, and that it patched the archives successfully... I guess that it could be an old log, which would imply that SMM crashes before it even gets to the point where it sets up logging facilites (basically the very beginning of the program).
If that's the case, download this batch script, put it inside SMM's directory, and double click on it. It will launch SMM indirectly, preventing the command prompt from disappearing the instant the manager crashes, allowing you to screencap any error messages -- post them here.

[ironhideforever]

@kartoFlane



Thank you so much for this. Seems like a java issue, but let me know what you suggest!

[kartoFlane]

Yup, something's wrong with Java. Reinstalling it should fix it. In case it doesn't, there's this thread at minecraft forums, with a lot of potential solutions.