Your edits are completely valid. The mesh is broken for another reason. I can't see the actual blend code, but chances are there is a mesh.getmesh(1) or mesh.getmeshraw(1) in there. It tries to import the second submesh from the binary. Problem is, this functionality was reversed by me on the smashe...

I was having a play with some stuff from your Dropbox. None of the scripts there include any call to sys that I could find. sys module is referenced inside blend file. If you open the blend scene and navigate into Text window, you will see a script that actually imports the meshes. It relies on my ...

beast_parts.jpg Finally found where block headers are stored and how offsets are organized. These are all the pieces from this mesh file (head is stored separately). Strangely enough I still don't see any value describing the amount of LODs in mesh which is odd. But I guess I should just fig a bit ...

Part separation is nominal. It isn't an island per limb. It goes in groups. On my screenshot you can see legs' and shoulders' armor pads. That all is the first 'island' in that model. Uslands most likely separated by material id, not by triangle connectivity. And yes, they have up to 5-6 lods, that'...

Afaik lzo was used as main compressor in siege in first years. Then they switched to zstd. It's still worth a try though. Right now Im having troubles with that mesh I posted earlier. Siege's triangle indices come in 0x180 long blocks. If block ends with valid triangle (3 unique indices) then you ca...

oryx_mom.jpg Well, something went wrong xD At least now I do have links per each npc. Strangely enough they have different magic from operator's assets (this one has 0x971a842e while assets have 0x22ecbe63). I hope inner structures will be the same. I'm planning to polish out mesh parser on older m...

God samples of new metas. Doesn't seem to be zstandard as for general .forge chunk packing. Maybe enyone by chance can identify the compressor? file index meta datapc64_merged_set02_bnk_meshshape.forge 2231 FF 60 FA 6B 30 80 D1 5F 68 A7 7A DC 9D C1 24 53 37 19 11 66 9C 2C C3 42 C4 80 92 2C 8A 70 45 ...

I haven't used the ninja ripper so I don't know what type of data you have. I'm pretty sure if it's actual model data than it can be interpreted and parsed. The other question is whether there is any sense in trying to convert it when there is some decent progress on unpacking tool.

Fury_ondemand seems to be the vital one that is missing. I stashed the old parser for now to keep the code. I don't want to introduce versioning inside existing repo right now because I want to focus on actual data parsers. I might introduce version recognition later. Or simply unpack the data and s...

Well as long as they don't decide to encrypt it like in for honor. And someone provides game resources. Because I don't think I'm going to buy it )

NNNNNOOOOOOOO!!!! I just found out from their update notes that they are going to restructure game data. Why?! WHY?!?!?! Edit: checked the TTS game version. They have indeed changed file format. But it's not that severe. They seem to pack meta and file data into one block now, so file headers have c...

Here is the link, have a try. https://www.dropbox.com/sh/sii6e34kymrkgzl/AACb1BYKQODv47NDBY3Qv2TUa Small node about your archives. I couldn't find any pointers from beast mesh to it's asset file. What this means is there are 2 options: 1. Mobs aren't stored as an operator asset 2. You missed some ....

Yes. Those are just textures like everything else. Problem is identifying them.

Right now it's based around manual parsing for 2 reasons: 1) it gives more flexibility. I can collect specific files and work on their raw data 2) it simply isn't finished to be as straightforward as possible =) . My main goal is to build complete models parser, complete skeletons parser (thanks to ...

I'm trying to document everything I do there. But you will still most likely need to write a script to grab the actual thing you want. Right npw the process looks like this: import r6s with r6s.forge.parse('path\\to\\forge.file') as f: for i, e, n, c in f.files(): # loop through all files in forge a...