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

[Sledgehammerr]

Everytime when i try patch FTL with mods which contains new ship/gameplay (no matter which one because this happens with all ship/gameplay mods) — Slipstream Mod Manager gives me this:

Code: Select all

Patching failed: java.io.IOException: Could not guess encoding for "data.dat:data/blueprints.xml".
Failed to decode as UTF-8: java.nio.charset.MalformedInputException: Input length = 1
Failed to decode as windows-1252: java.nio.charset.UnmappableCharacterException: Input length = 1

I've tried everything: reinstall FTL, redownload SMM, redownload mods, but this isn't helped.

P.S. Sorry for my bad English

[birb]

Hallo! New birb captain here yes very excite to save spaces an thwart rebel squirrels yes o<o

I just recently got into FTL and I was told by a friend to install the Captain's Edition mod, and so I ended up grabbing SMM as instructed, but after fiddling around with several mods, reinstalling things in multiple combinations, and triple-checking my work, the game keeps crashing and I can't figure out why or a the solution to the problem :<
The thread for the Captain's Edition says to bring my problem to this thread, so I hope someone can help.

Originally I had the following Mods, arranged in this same order in the SMM as directed in the mod load order template found in the CE thread:

Better Planets and Backgrounds (1.2.1, since the thread stated that it was less prone to issues than 1.3)
CE Resource Pack
FTL Captain's Edition
CE BPaB Compatibility Patch
CE Infinite Addon
EL Texture Pack
CE Endless Loot Addon for CE Infinite
CE Non-EL Enemy Loadouts Addon

But after not even being able to get past the initial loading screen (before the title screen, with the fancy new outline of the space station) I followed one of the CE's troubleshooting suggestions and dropped all of the Endless Loot mods. After doing that and reattempting, the game now either loads the entire bar and crashes, or it gets to the title screen, repeatedly freezes every couple seconds as it attempts to load several times, and then crashes anyway. It seems to be random each time I open the game. After several redownloads and reinstallastions of everything, I still can't fix this problem, so I hope somebody knows what's going on and can tell me how to fix it (and if I can still make use of the Endless Loot mod because I sure want to).

If you need me to provide logs or anything just ask, but I don't know what I should be looking for so I need some directions on that front...

[meklozz]

@Sledgehammerr
Are you sure you completely reinstalled FTL? Like, totally removed both FTL and SMM .dat backups and got it again (important to get rid of it all at the same time or the backups may get back in)? No other ideas but corrupted/altered data files.

@birb
Does nothing work at all? Or can you get some mods to load?
http://www.ftlgame.com/forum/viewtopic. ... 700#p98311
This details the stuff you need to do to get EL running, and it can help with other resource intensive mods as well. If it's not the matter of memory, then maybe try deleting (after backing up, of course) your save. Some logs are in stdout and stderr txts in ftl folder, you can check what gets loaded successfully and what stops the game there.

[birb]

I already tried deleting and reinitializing my saves and reinstalling the game a couple times, as I said, so I know it's not that. I took a look at stdout.txt (stderr was empty) and found that every time it loads stuff it loads it just fine, but there's anywhere from 2-12 errors for every item complaining about 'double defined names' or 'repeated event names', so I don't know, maybe it is a memory problem and the game is just loading up ludicrous amounts of repeated junk files and padding the memory it has to use? I have no idea what this means exactly :S

I'll try looking at the thread and seeing what I can do with that. I'll edit this post later with my findings.

[meklozz]

Double defined names happen when you load stuff like this (CE), shouldn't be much to worry about unless they repeat themselves several times (the same ones). Is the last thing there saying that the game is running or something or does it stop before that?

You didn't mention if any mods at all can load? A single ship, some extra backgrounds even?

You can check how memory use looks in the task manager. I think that if the memory is the problem then you get the stderr, too, and stuff like can't allocate memory in there. Not sure.

[birb]

Actually, since you replied before I got to check the thread I'll just put a new post here.

All you did was link to the Captain's Edition thread. I already stated that I got all the mods I'm trying from that thread and looked at all the troubleshooting stuff in it. Did you even read my post? None of the mods seem to not be able to function, though I've only tried Captain's Edition and Better Planets and Backgrounds individually after tearing out Endless Loot. I can't get the game to work past the loading screen or, in the best case scenarios, anywhere past the title screen if it gets to that part with any of the mods; that's what I need help with.

I suppose at this point a memory issue seems to be the likeliest suspect, but I've so far had no luck fixing that with what few solutions I've found, and I really don't know why it's such a problem when I've played much more intensive games on this computer with loads more mods and I've never run into this problem. I've already tried looking at the memory using the task manager, but it doesn't seem to be any different than any given game I play, so the only way I could really check to see if that's the problem is to find a way to allocate more memory, implement that change, and see if there's a difference. Unfortunately, I can't seem to find a way to do that that I can understand x_x

As for the repeated items in stdout.txt, none of them are the same, so I suppose that isn't a problem, though the log itself does, for some reason, just cut off at a certain point.

[meklozz]

All you did was link to the Captain's Edition thread.

I suppose at this point a memory issue seems to be the likeliest suspect, but I've so far had no luck fixing that with what few solutions I've found

Unfortunately, I can't seem to find a way to do that that I can understand x_x

That's exactly what the link is for. It's supposed to go to a post with this link:

http://www.techpowerup.com/forums/threa ... re.112556/

Where you have the information on how to make it large address aware and be able to use more memory. Although if no mods work whatsoever, even the smallest ones... It could be something else, I guess; it would be good if you tried something as small as possible, like a single ship, just to see if there is some error with the manager/game that prevents anything modded from running at all.

I really don't know why it's such a problem when I've played much more intensive games on this computer with loads more mods and I've never run into this problem. I've already tried looking at the memory using the task manager, but it doesn't seem to be any different than any given game I play

It's just how the game is made, mods support isn't 'native' so it doesn't work as well for everyone. But what does it mean, just like any other game. Does it stay below ~300MB? Does it go into gigabytes even with just a single mod?

the log itself does, for some reason, just cut off at a certain point

Yes, what point? Does it get past the repeated events?

[birb]

I totally missed the link in that post. Whoops :<

So glad there's just a program to help with this. When I 'jailbroke' Fallout 3 to work on Windows 7 it was a nightmare of mods and patches. Then again, it was specifically Fallout's problem that that needed to be done in the first place... Pretty sure it's the opposite case with this issue. I'll try out the LAA program and see if it works. I'll edit this post if I get any results.

As for the stdout.txt just cutting off at a point, it actually does not get through the repeated bits. It literally just cuts off partway through another 'repeated event name' error; all it says on the line is "ERROR: Repeated Eve", and then it just stops. It's preceded by exactly 20 other 'repeat errors' for the same event, "NEBULA_SLUG_CHOOSE_DEATH". Curiously, the txt seems to cut off at a different part every time I patch through SMM, and I'm not really sure what that means. Actually, it may just cut off at a different part whenever I try to load the game... I should test that.

I should also note, just for posterity's sake, that I have the GOG version of FTL, not the Steam version, so I haven't actually been able to validate my game files either. Doubtful that would help much, but it's something to note regardless.

EDIT: It totally worked! All I had to do was jailbreak it! \o<o/
My, it sure takes a fat chunk of memory to work... But who cares Thank you for the help!

[birb]

Shit, okay, well, it was working, for like five minutes. I managed to patch in everything, get it working, and got to the title screen and was working peachy. The only thing was that there was a curious little issue with some of the graphics freaking out, so I quit out of the game and attempted to swap the Better Planets and Backgrounds mod with the 1.3.1 version (the newest one) instead, hoping it would fix the issues or something. Unfortunately, now when I keep trying to repatch the game, it gives me an error like so:

Code: Select all

And unexpected Error has occurred

Thread: Thread[Thread-6,6,main]
Error: java.lang.OutOfMemoryError: java heap space

See the log for details.

If this interrupted patching, FTL's resources were probably corrupted.
Restart Slipstream and patch without mods to restore vanilla backups.

I tried doing as it suggests at the end, but I keep retrying to patch the mods back in afterwards and it gives me the same error. I even tried to implement 1.2.1 of the BPaB mod again and it gives me the same error now. I used the LAA program to allocate extra memory for both Slipstream and the game itself, so I don't know why it's an OutOfMemoryError. I went to check the log and this is the error as it appears in there, and it always happens while it's patching in the CE Infinite Addon:

Code: Select all

[Thread-6] ERROR net.vhati.modmanager.ui.ManagerFrame - Uncaught exception in thread: Thread[Thread-6,6,main] java.lang.OutOfMemoryError: Java heap space
	at org.jdom2.ContentList.ensureCapacity(ContentList.java:414)
	at org.jdom2.ContentList.add(ContentList.java:250)
	at org.jdom2.ContentList.add(ContentList.java:79)
	at java.util.AbstractList.add(Unknown Source)
	at org.jdom2.Element.clone(Element.java:1460)
	at org.jdom2.Element.clone(Element.java:105)
	at org.jdom2.Element.clone(Element.java:1460)
	at org.jdom2.Element.clone(Element.java:105)
	at org.jdom2.Element.clone(Element.java:1460)
	at org.jdom2.Document.clone(Document.java:695)
	at net.vhati.modmanager.core.XMLPatcher.patch(XMLPatcher.java:57)
	at net.vhati.modmanager.core.ModUtilities.patchXMLFile(ModUtilities.java:246)
	at net.vhati.modmanager.core.ModPatchThread.patch(ModPatchThread.java:242)
	at net.vhati.modmanager.core.ModPatchThread.run(ModPatchThread.java:88)

I'll redownload all the CE Infinite mods right after I post this and see if that has any effect, and I'll edit the post with my results.

EDIT: Okay, so I basically just decided to reinstall everything and that sorted all that shit out, but if you have any ideas for what the hell was going on just in case it happens again, or if anyone else needs to find a solution to the same problem, go ahead and lay them out.

Unfortunately, everything is still not peachy-keen, because it seems that there's still the same sort of texture problems going on and I can't fix them. The Captain's Edition thread says in the troubleshooting suggestions that it's either Better Planets and Backgrounds and its compatibility patch being a little shit, or it's a problem with one of the resource/texture packs for CE or the Endless Loot add-on. I made sure all the mods were in the correct order, so it's not that, and I also took BPaB out of the equation and it's still happening (though it seems to be slightly less apparent?) so I'm assuming it's one of the resource/texture packs. No idea how I'd go about fixing that, since I reinstalled both of them several times now, but if you have any ideas about this new issue, I'd love to hear them!

[meklozz]

Well, glad you got it working. There was something about specifically increasing java heap space in the troubleshooting, too, I'm not sure if it's the same method as LAA, but since it's working, I guess no point going on about it.

I've also seen that stdout cuts off for me when working, too, if there is to much stuff, again, never mind that.

I'm not sure what could be the problem now. I take no errors are appearing anymore? You could try deleting the backups, data and resource, inside the smm/backups folder. After that, you'd have to reinstall clean from gog (it's pretty much like verifying files). That would mean you'd have to do the LAA thing again.

Oh, here's an idea to try first instead, disable dynamic backgrounds or play with some other in-game settings. I think there was a problem with the BPaB there somewhere.

You could try one mod after another (starting with no mods at all) and see what's causing it exactly. And, anyway, just what exactly is the problem? Black boxes, missing stuff, ships, weapons, what is it? Screenshot wouldn't hurt either.