Mind to show to vertices? I won't do all the work - my usual job is to show the first sub mesh of one sample.

(In some rare cases where I'm interested in the models myself I create some Make_obj (or Make_H2O) project. That's the way it goes and I won't change it. )

fast wrote: ↑Fri Jul 30, 2021 9:09 am how to fill vertices with faces?

What you think is face indices (FIs) looks much too regular to me. So auto created face indices seem to do the trick (until someone finds out how to get the FIs, if any).
.

Seems good, do you have any solid tutorial for hex2obj because the original is quite difficult to understand. well, the project is finished, more or less - so I surely won't write another tutorial. :eek: You may read through the "Extracting simple models" thread: https://forum.xentax.com/...

The formula would be directPosIdx[i] = posIndices[ faceIndices[i] ] ... yeah, that's what I used in my last posted picture. Or you just recreate the position and uv buffer to use the face indices directly: directPosCoord[i] = positions[ posIndices[i] ] directUvCoord[i] = uvs[ uvIndices[i] ] That's ...

As a first impression (maybe more tomorrow):
.

milo9559 wrote: ↑Thu Jul 29, 2021 2:14 pmAny body have any easier method how to do that?

If you think of a one-click-solution I guess, "no". As always you'll need to understand the data structure, test it in a tool (AXE, MR, hex2obj), then write a script.

Maybe for uvs are indexed are something like that? Yep, newbie, and the vertices, too. :roll: Well, indexed indices. "Data Reorganizer" of AXE is a good idea but too complex for me (and hex2obj - guess I will create/hold all the data in its memory. But no idea how to keep this simple for ...

Maybe for uvs are indexed are something like that?
Point cloud looks ok:
.

well, doesn't look too bad: . 2h_axe.png Guess you need to use a lesser face index count (15?) for the first sub mesh, then find the start of the next face indices block for the mesh. (For the uvs it's different, max FI is 116 there. ) edit: nope, it's indexed vertices (or to say, there's an additio...

It's supposed to be - someone has to do the remaining work .

Like vertices the uvs seem to make sense:
. (We'd need the texture to maybe tell more.)

Take your time.

Finding the start of vertices in aya_a.kmd is no rocket science, I just scrolled down through the file in a hex editor:
.

lilyampykidYTXeNTaX wrote: ↑Sat Jul 24, 2021 7:34 pm Hey Shakotay2, can I get help with CHAR_FourArms_WC.et_decomp?

Well, I was in the hope you could start some research by yourself. These are my nearest hits:
. (both meshes look similar somehow)

, but what file you open on a debugger (ida or ghidra) of an xbox1 game? well, I guess you'll need the XBox360 SDK? ------------------------------ Would this be useful for refining existing model plugins/converters for CS? Usually we don't have access to the .pdb files of those plugins/converters. ...

Afaik .pdb is the symbol table, you load the exe into a debugger (windbg, IDA, OllyDbg) then usually the symbol table is loaded and you can see data types, set break points, etc.
Here are the symbols of a 3D tools of mine in x32dbg (successor of OllyDbg?) :
.