Maybe post some D4 model samples here? Can't do nothing without seeing some samples.

Maybe someone could reupload samples. Links above are expired.

People use PMX Editor for this. They don't use Noesis or Blender, unless your aim is to make things more difficult.

This is a DirectX file stored in the DirectX format. The reason it doesn't load is because they either changed or added new template names. DirectX templates allow you customize the format to anything you want. These files are in binary format, so perhaps if you were to convert them to text format, ...

Payload texture: Looks like pure texture data, most likely in some compressed format. Meta data: 0x18 (DWORD), possibly texture format. 0x28 (DWORDs), width, height of texture. Not always powers of 2, but always a multiple of 4. Rest of meta data probably meaningless until someone figures out what t...

IstiGI wrote: ↑Sun Dec 04, 2022 9:35 am Not all of them this large. I thought it would be more convenient to add the largest ones as an example

Not really, the smallest files are best. The less data to look at, the better. And not just one file, we need several, for comparisons.

Diablo 4 is new to me. Can we see some model data?

Are all texture files this large? 28MB? It seems unusually large for a single texture.

These files are still compressed with LZ4. You can tell by the 'ZZZ4' id in the header. If they come from DIDT, you need to do one more step and decompress them.

I managed to get these model files of Diablo from the Wowhead website's model viewer. Do you have a link? That site is always confusing to me. btw, those ".model" files are actually 4 files in one. Model + Mesh + Material + SkinSkeleton. Each subfile begins with a "MESSIAH" id. ...

It's not for newbies. If you don't know a thing about assembly language, then you're not going to understand how to use it. And if you have to ask about it, then it's probably above your skill level.

If you want something free, google for OllyDbg.

Executable = .exe. It's machine language. They use a decompiler like IDA Pro to dump it.

When a file format is difficult to figure out, the most determined people usually resort to decompiling the game executable. I would guess that's what they did to make their MDG3 tool. Maybe find someone who likes decompiling games.

They may have bones, but the link I posted was for MDG3 models, not MDG5 models. There is no tool for MDG5 models.

It looks like the same format used here: https://forum.xentax.com/viewtopic.php?t=15853 But instead of MDL3/MDG3 headers, they use MDL5/MDG5 headers, so the data is organized differently. Like before, both files are needed, as the .mdg file stores the geometry, and the .mdl file describes it. Sorry,...

btw, are STO models animated in any way? Do they have bones/joints or skeletons? Any external animation or skeleton files? Just wondering why source code mentions "bone weights", when I don't see any bones in the file or any kind of hierarchy.