Page 44 of 77

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 2:56 am
by nimde
Hey there,
I'm running OS X and I'm having a little difficulty running the mod manager for the first time. I was wondering if you guys could help?

After unpacking the files and running modman.command, my command prompt opens and displays the message
"No Java runtime present, requesting install". Here's a screenshot:Image

I have the most up to date verison of Java. Is there something I'm doing wrong? I'd really appreciate your help.

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 3:07 am
by nimde
Ignore me I downloaded the wrong version of Java. I am a fool.

Thanks for the awesome program!

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 8:29 pm
by ITzMeek
I've been having trouble with running FTL after installing mods. i get an assertion error after FTL finishes loading. After a while i noticed that you say that SMM is for FTL v1.01-1.01.3, and I'm running FTL (AE) 1.5.13
I can only assume that this would be the problem, and i just wanted to check in to see if that indeed was why my game won't working after running SMM

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 9:10 pm
by kartoFlane
SMM works fine with later versions of FTL, it's just that no one ever bothered to update the version requirement section. The game crashing usually means a problem with the mod(s) you are installing (due to them being either out of date / uncompatible with each other / having flatout wrong code). Try dropping mods from your modorder one by one until you find the culprit.
Generally if a mod thread has been posted before 4th of April 2014 (or whatever AE's release date was), it will not work.

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 9:24 pm
by ITzMeek
okay, well good to know then. Thanks :)

*EDIT: okay...well just simply patching SMM (clicking patch without any mods checked) will cause FTL to have an assertion error...sooo idk what that's all about. My guess is that FTL isn't reading the modified resource files properly?
Image

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Sun Dec 21, 2014 11:10 pm
by kartoFlane
Try this.

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Mon Dec 22, 2014 4:05 am
by ITzMeek
that fixed it ^.^
thank you very much. I appreciate that you actively help out on your software here

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Tue Dec 30, 2014 11:13 am
by Yoshiquest
ITzMeek wrote:okay, well good to know then. Thanks :)

*EDIT: okay...well just simply patching SMM (clicking patch without any mods checked) will cause FTL to have an assertion error...sooo idk what that's all about. My guess is that FTL isn't reading the modified resource files properly?
Image
Apparantly I'm having the same problem. I have already tried the solution suggested (I've probably redownloaded the resources folder a dozen times now, and the patcher isn't making any backup files before the crash). Please let me know if there is a better fix. Thanks.

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Tue Dec 30, 2014 11:34 am
by kartoFlane
@Yoshiquest
This:
The game crashing usually means a problem with the mod(s) you are installing (due to them being either out of date / not compatible with each other / having flatout wrong code). Try dropping mods from your modorder one by one until you find the culprit.
Generally if a mod thread has been posted before 4th of April 2014 (or whatever AE's release date was), it will not work.
You can also tell SMM to "patch" the game without selecting any mods -- this will cause it to create backups without making any changes, or, if it already has backups, restore them to the game (meaning you don't have to redownload/reinstall)

Re: Slipstream Mod Manager v1.6 (2014-10-25)

Posted: Tue Dec 30, 2014 7:17 pm
by Yoshiquest
kartoFlane wrote:@Yoshiquest
This:
The game crashing usually means a problem with the mod(s) you are installing (due to them being either out of date / not compatible with each other / having flatout wrong code). Try dropping mods from your modorder one by one until you find the culprit.
Generally if a mod thread has been posted before 4th of April 2014 (or whatever AE's release date was), it will not work.
You can also tell SMM to "patch" the game without selecting any mods -- this will cause it to create backups without making any changes, or, if it already has backups, restore them to the game (meaning you don't have to redownload/reinstall)
Ummm that's what I did. It crashes and fails to make backups, even without any mods selected.

EDIT: Actually, the console does give an error...

13:19:12.335 [Thread-4] ERROR net.vhati.modmanager.json.JacksonCatalogReader - While processing "current_catalog.json", json parsing failed: Unexpected end-of-input in VALUE_STRING
at [Source: .\backup\current_catalog.json; line: 1, column: 142529] com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input in VALUE_STRING
at [Source: .\backup\current_catalog.json; line: 1, column: 142529]
at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1284)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:588)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:521)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:515)
at com.fasterxml.jackson.core.base.ParserBase.loadMoreGuaranteed(ParserBase.java:432)
at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishString2(UTF8StreamJsonParser.java:1930)
at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishString(UTF8StreamJsonParser.java:1911)
at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.getText(UTF8StreamJsonParser.java:276)
at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:203)
at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeArray(JsonNodeDeserializer.java:228)
at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:200)
at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:197)
at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:58)
at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:15)
at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:2575)
at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:1550)
at net.vhati.modmanager.json.JacksonCatalogReader.parse(JacksonCatalogReader.java:34)
at net.vhati.modmanager.ui.ManagerInitThread.reloadCatalog(ManagerInitThread.java:210)
at net.vhati.modmanager.ui.ManagerInitThread.init(ManagerInitThread.java:110)
at net.vhati.modmanager.ui.ManagerInitThread.run(ManagerInitThread.java:71)