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

Discuss and distribute tools and methods for modding. Moderator - Grognak
Stefive
Posts: 2
Joined: Thu Nov 07, 2013 5:10 am

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby Stefive » Thu Nov 07, 2013 4:15 pm

kartoFlane wrote:@Stefive
You have to run SMM as admin. Right-click on the .exe and select "Run as administrator".
If you don't have admin privileges on your account, you'll have to keep your FTL installation outside of Program Files, since that folder is protected by Windows.

Okay, thanks
Laminxar
Posts: 1
Joined: Sun Nov 10, 2013 6:40 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby Laminxar » Sun Nov 10, 2013 6:46 pm

I've had an issue with the mod manager, and it involves with a fail on patching. Apparently access is denied to this, and the code that was given is:

java.io.FileNotFoundException: C:\Program Files (x86)\FTL\resources\data.dat (Access is denied)

Any clues on how to fix this? I've re-installed FTL to get the unmodded version and yet it still occurs...
User avatar
kartoFlane
Posts: 1479
Joined: Mon Jan 14, 2013 10:20 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby kartoFlane » Sun Nov 10, 2013 8:52 pm

@Laminxar
You have to run SMM as admin. Right-click on the .exe and select "Run as administrator".
If you don't have admin privileges on your account, you'll have to keep your FTL installation outside of Program Files, since that folder is protected by Windows.
Superluminal2 - a ship editor for FTL
TurtleWatson
Posts: 2
Joined: Tue Nov 12, 2013 3:54 am

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby TurtleWatson » Tue Nov 12, 2013 4:00 am

Hello. This looks pretty promising, but I keep getting a java.io.EOFException error when I try to activate mods. If I run FTL with them activated it crashes. I have no mods installed and have played the game. I searched it up with no results. Are there any solutions to this?
User avatar
kartoFlane
Posts: 1479
Joined: Mon Jan 14, 2013 10:20 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby kartoFlane » Tue Nov 12, 2013 11:24 am

@TurtleWatson
Open up modman-log.txt in SMM's directory, and post its contents here inside [ code ] ... [ /code ] tags. This'll give us the information we need to be able to help.
Superluminal2 - a ship editor for FTL
TurtleWatson
Posts: 2
Joined: Tue Nov 12, 2013 3:54 am

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby TurtleWatson » Tue Nov 12, 2013 10:27 pm

Code: Select all

22:50:08.178 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Slipstream Mod Manager v1.4
22:50:08.178 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Windows 8 6.2
22:50:08.178 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Java HotSpot(TM) Client VM, 1.7.0_21, x86
22:50:08.240 [AWT-EventQueue-0] INFO  net.vhati.modmanager.FTLModManager - Using FTL dats path from config: C:\Program Files (x86)\Steam\steamapps\common\FTL Faster Than Light\resources
22:50:09.069 [Thread-4] DEBUG net.vhati.modmanager.ui.ManagerInitThread - Catalog isn't stale yet.
22:50:09.069 [Thread-4] DEBUG net.vhati.modmanager.ui.ManagerInitThread - App update info isn't stale yet.
22:50:09.162 [Thread-5] INFO  net.vhati.modmanager.core.ModsScanThread - Background hashing finished.
22:50:09.162 [Thread-5] INFO  net.vhati.modmanager.core.ModsScanThread - Background metadata caching finished.
22:50:19.897 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame -
22:50:19.897 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame - Patching...
22:50:19.897 [AWT-EventQueue-0] INFO  net.vhati.modmanager.ui.ManagerFrame -
22:50:19.913 [Thread-6] INFO  net.vhati.modmanager.core.ModPatchThread - Restoring vanilla "data.dat"...
22:50:19.928 [Thread-6] INFO  net.vhati.modmanager.core.ModPatchThread - Restoring vanilla "resource.dat"...
22:50:20.460 [Thread-6] ERROR net.vhati.modmanager.core.ModPatchThread - Patching failed. java.io.EOFException
   at java.io.RandomAccessFile.readFully(Unknown Source)
   at net.vhati.ftldat.FTLDat$FTLPack.readLittleUInt(FTLDat.java:475)
   at net.vhati.ftldat.FTLDat$FTLPack.readIndex(FTLDat.java:572)
   at net.vhati.ftldat.FTLDat$FTLPack.<init>(FTLDat.java:461)
   at net.vhati.ftldat.FTLDat$FTLPack.<init>(FTLDat.java:451)
   at net.vhati.modmanager.core.ModPatchThread.patch(ModPatchThread.java:160)
   at net.vhati.modmanager.core.ModPatchThread.run(ModPatchThread.java:88)

User avatar
kartoFlane
Posts: 1479
Joined: Mon Jan 14, 2013 10:20 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby kartoFlane » Tue Nov 12, 2013 11:02 pm

From the looks of it, SMM seems to think that the file is smaller than it actually is, and finishes reading prematurely.

That would imply that there's something wrong with your .dat files... But you say it only crashes when you try to install mods? And when you revert to vanilla (patch without any mods selected), everything's fine?

Very odd.

That might not help with this issue, but try to use the default approach like when the archives are corrupt:
- go to /backups folder in SMM's directory, delete data.dat.bak and resource.dat.bak
- then in Steam, go to Library > FTL > right-click > Properties > Local Files > Verify Integrity of Game Cache...
- once it finishes redownloading the archives (should it be deemed necessary), run SMM again.

Hopefully that'll fix any errors. If not, you'll have to wait for Vhati.
Superluminal2 - a ship editor for FTL
Vhati
Posts: 792
Joined: Thu Oct 25, 2012 12:01 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby Vhati » Thu Nov 14, 2013 2:28 am

kartoFlane wrote:From the looks of it, SMM seems to think that the file is [ larger ] than it actually is, and finishes reading prematurely.

The java.io.EOFException is from futilely attempting to read past the end-of-file, because the file turned out not to be as large as expected. Other than that, spot on diagnosis and advice.

kartoFlane wrote:If not, you'll have to wait for Vhati.

* Unsubscribes/resubscribes to the thread to coax the forum into properly sending email notifications. *
hagabaka
Posts: 3
Joined: Thu Nov 14, 2013 4:52 am

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby hagabaka » Thu Nov 14, 2013 4:56 am

Hi, I'm trying to use this on Arch Linux. When I run modman.command, doesn't show an user interface and doesn't print anything in console. The log file only contains:

Code: Select all

23:55:28.153 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Slipstream Mod Manager v1.4
23:55:28.155 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - Linux 3.12.0-1-ARCH
23:55:28.156 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - OpenJDK Server VM, 1.7.0_45, i386
23:55:28.202 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - FTL dats path was not located automatically. Prompting user for location.
Vhati
Posts: 792
Joined: Thu Oct 25, 2012 12:01 pm

Re: Slipstream Mod Manager v1.4 (2013-09-20)

Postby Vhati » Thu Nov 14, 2013 4:31 pm

hagabaka wrote:Hi, I'm trying to use this on Arch Linux. When I run modman.command, doesn't show an user interface and doesn't print anything in console. The log file only contains:

Code: Select all

23:55:28.202 [AWT-EventQueue-0] DEBUG net.vhati.modmanager.FTLModManager - FTL dats path was not located automatically. Prompting user for location.

This may be a silly question, but... was the prompt hiding behind the console window?


Otherwise, I'm at a loss as to what could prevent the prompt from appearing altogether.
But you can at least bypass the prompt by writing "modman.cfg" yourself...

Code: Select all

#
# allow_zip         - Sets whether to treat .zip files as .ftl files. Default: false.
# ftl_dats_path     - The path to FTL's resources folder. If invalid, you'll be prompted.
# never_run_ftl     - If true, there will be no offer to run FTL after patching. Default: false.
# update_catalog    - If a number greater than 0, check for new mod descriptions every N days.
# update_app        - If a number greater than 0, check for newer app versions every N days.
# use_default_ui    - If true, no attempt will be made to resemble a native GUI. Default: false.
# remember_geometry - If true, window geometry will be saved on exit and restored on startup.
#
# manager_geometry  - Last saved position/size/etc of the main window.
#
#Fri Nov 13 23:31:30 EST 2013
ftl_dats_path=/edit/this/to/FTLs/resources/dir/containing/data.dat/
update_catalog=7
use_default_ui=false
allow_zip=false
update_app=4
remember_geometry=true
manager_geometry=x,319;y,133;w,514;h,423;divider,127
never_run_ftl=false

Who is online

Users browsing this forum: No registered users and 31 guests