TOOL: TS3 Recompressor
Ibce:
Hello.
It's been a while since I played the sims, I've got a problem decrapping store content...
I throw the s3pack into the s3rc.exe and get the message that it couldn't open the s3pack as writable.
Is this a known issue? I couldn't google up anything useful with that message.
witch:
All I can say is that mine still works fine. Try another .sims3pack or re-download the recompressor.
J. M. Pescado:
Couldn't open as writable means that something was preventing the program from writing the output data, probably file permissions or failure to close something that had the file open.
spauldo:
Bug report:
I've got a 1.3GB TravelDB.package file from a non-awesome save. I'm running s3rc from the command line with no arguments.
It segfaults with no other message after a minute or so. It does the same with -r, as well as -s. It works with -fD.
When run from cmd instead of bash, I get "An unhandled win32 exception occurred in s3rd.exe [4920]" and a prompt to debug in Visual Studio. Attempting to debug fails, with "not enough storage is available." I'm assuming it's running out of memory, but I don't do Windows so I don't know what that looks like on here. I'd try to compile it with 64 bit support, but again, I don't do Windows and my last attempt at trying to do something like that ended in a broken executable, a headache, and a few hours of my life I'll never get back.
The file does not change (tested with cmp from cygwin).
I opened file file with s3pe and it's apparently mostly images, with some UNKN and SIME tags in there as well.
Not a huge deal, as I'm going to be starting a new Sims 3 tree for playing with AM, but figured I'd pass it along.
s3pe opens the file just fine. Any way to shrink/compress the file using that or some other tool?
J. M. Pescado:
Running out of memory seems like a likely problem, given that your thing is 1.3 GB, and would inflate even more uncompressed. How the fuck did you get it to be that enormous?
And yes, the file won't change because it never gets to the part where it writes out a temp file to overwrite the old one with. At this point the most drastic thing I could suggest is simply burninating the entire file with fire. Because honestly, I'm not sure what it really does, anyway. Just be sure you back things up before trying this to see if anything explodes.
Navigation
[0] Message Index
[#] Next page
[*] Previous page