Unable to extract MP2, fatal error during FrontEnd.pak about metaforce HOT 16 CLOSED

Thank you for the report, We'll see what's going on and see about fixing it. Also that AL bug is rather strange, and should be unrelated to what we're using blender for.

from metaforce.

So I am getting the same error, however I was able to somewhat pipe the output into a log file. Upon doing so the crash no longer happens but the log file produced seems corrupt somehow. The first 500 lines or so seem normal but after that there is really odd behavior. Notepad++ doesn't seem to display correctly but opening it in normal Notepad apparently allows me to see the full contents.

The last normal lines of output are:
"Continue? (Y/n)
Using DataSpec MP1:
Update Partition"

After that there are about 10 blank lines and then the remainder of the file is filled up with dash characters.

Hopefully you can do something with this information.

Blender version 2.76b, running Windows 8.1

EDIT: I would like to add that I received the same error for both my Trilogy image as well as my MP1 image.

from metaforce.

Hmmmmmm, that's the same error I was able to reproduce once, but haven't had any luck with since.

Can you run it in verbose mode? -vv or -vvv should work.

from metaforce.

Ok so if I don't try to write to a file I'm able to see a bit more than was in my log. Here's a pastebin: http://pastebin.com/zfHBpzJ2

Also, as a heads up, I'm using the release exe that you guys have provided (looks like 25 days ago was last release) and am not compiling the current source.

from metaforce.

AH HA!, Unicode!!!!

from metaforce.

Hmm, I'm curious, can you move it into a path that does not have spaces and try again?

from metaforce.

Same issue. Still says there is a unicode error.

from metaforce.

Yeah, we kind of figured it wasn't a spacing issue, but it didn't hurt to try.

from metaforce.

Alright, we traced the issue down, we should have a working fix here in a bit.
But for now an explanation is in order:
Currently we're not escaping or transforming path separators, so when "C:\Users*" is being passed to python it's seeing \Users as a unicode escape, causing this issue:
http://stackoverflow.com/questions/18084554/why-do-i-get-a-syntaxerror-for-a-unicode-escape-in-my-file-path

A simple fix by all means, but still an irritating one.

from metaforce.

Found it myself.. extracted to D:\Umos and the issue occurred early on.

Updated the release to p6e:
https://github.com/AxioDL/PathShagged/releases

Let us know if that works for you!

from metaforce.

Currently testing. Its made it past where it was crashing before and working great so far!

from metaforce.

Nice, let us know if you get get a full extract, depending on your computer it can take anywhere from 2 to 4 hours, sometimes longer.

from metaforce.

Full Extraction seems to be coming along nicely. Several of the paks have been extracted at this point!

I do have a question though. Is collision data extracted as well? I haven't seen any hints of it yet.

from metaforce.

Yes, collision data is stored in layer 2 for Maps, we currently don't export DCLN, but we will soon.

from metaforce.

Everything extracted nicely!

from metaforce.

Nice!

from metaforce.