I gave up and just used PCSX2ModelConverter 1.0.

I keep forgetting to add the 4. I haven't tried 2byte floats since struct.unpack won't accept them. I need to take a step back a learn more about mesh formatting, It could be that the vertices are somehow padded and don't directly follow each unlike the terrain, I just wish I had more examples to wo...

It might be possible but at this point I'm more concerned about the floats. Is it possible for different assets to use different float types? I tried a script using doubles and got next to nothing but after months of this it seems that byte long floats akin to the terrain vertices might not be it ei...

Just tried my file comparison script on a savestate with a mech and one without and didn't get anything that even might have been viable. At this point, I have two theories- mech and weapon data is loaded wholesale into the memory and thus can't be splintered off with the method I'm using or I have ...

I managed to take a look at the differences file and found about three groups of floats capped by what might be headers. http://i.imgur.com/NBaLi9q.jpg Wrote some code. import struct import re import bpy coordinates = [0.0, 0.0, 0.0] vertices = [] f = open(r'C:\Users\Greg\Documents\Front Mission sav...

Made the file comparison script using a = open(r'C:\Users\Greg\Documents\Front Mission savestates\FM4 hanger no weapons.bin', 'rb') b = open(r'C:\Users\Greg\Documents\Front Mission savestates\FM4 hanger one weapon.bin', 'rb') c = open(r'C:\Users\Greg\Documents\Front Mission savestates\differences.bi...

I had this idea the other day after thinking about doing another file comparison- I'm going to write a python script that reads from either two drastically different or very similar savestates and writes the differences/shared values to a third file. Theoretically, either approach would narrow thing...

I've been thinking, if using a script to pull out vertices isn't working, why not pull out headers? It's probably too resource intensive but If I could put each byte into an array then loop through it while comparing entries through re.match I can see how many times said byte appears in the code. Fr...

To my understanding, a PS2 savestate is simply a RAM dump, hence the ability to extract game assets from it. I tried switching around parts of the mechs in-game in hopes of finding different XYZ values when comparing two savestates, this did not work as I did not factor in changes to mech and invent...

Assuming my script is throwing off the mech vertices, I suppose working backwards with files or savestates is impossible and I would need to go through them by hand. I just wonder how I'll know when or if I find the mech header, the formatting must be less obvious than the terrain header or he would...

I took a look at the vertex clouds again, I'm starting to wonder if the reason I can't see the mechs is because the their vertex data is "off" and forming a different shape- if the header itself is read in as a float wouldn't that cause the resulting vertex coordinates to be one off, thus ...

Oh, I see. My original script just read in the terrain vertices until it reached what might be the vertex color header.

Performing a wildcard search for the terrain header was actually the first script I made but I don't understand what "+4 log 11*3 floats each (11 vertices)" means or does. Are you trying to exclude the terrain vertices?

The file extractor the PS23D guy made extracted about 3000 game files ranging from 0 to 300MB. While that sounds like a lot, the script generated quite a few duplicates I've been deleting on and off again. In any case, I poked around them in the beginning and found some level mesh data around the 10...

I didn't know that was an option. Would there be a difference between this and testing the files I've extracted from the archive?