Jump to content

Analysing a model with Model Researcher, output is a bit weird

Go to solution Solved by Durik256,

Recommended Posts

Hi all!

I am currently analysing a 3D model format, with the following data structure:



Which translates to the following model of (part of) a Porsche 911 GT2RS:



All vertices seem to be allright and the end of the block lines up with what I've seen in 010 Editor.
However, when I try to map the faces, thigs becomes a bit.... cheesestringy... 
Who has any idea what I'm doing wrong here? Thanks in advance!





Edited by Jille
Link to comment
Share on other sites

1 hour ago, Jille said:


I think your model is divided into submesh, and each submesh has its own piece of vertices. you need to specify the offset of faces and vertices for each submesh

Link to comment
Share on other sites

Ahh, yes, you are totally right, that's exactly the case!
Submesh 0, without any cheesestrings 😄 


And there are 6 more that build on this.
Now I have to convert this data to something useful with Python 😄 


Link to comment
Share on other sites

Posted (edited)

Because it's not a game! It's car infotainment 🙂.


I'll share the meshfile. It's made in some proprietary tool, called Esel Studio, and the full (big!) conainer file has an .iaa extension. I figured out most of the file format, which was a fun exercise 😄 I am writing a converter in Python, to export all relevant data to a format I can work with 🙂 


Edited by Jille
Link to comment
Share on other sites

  • Solution
3 hours ago, Jille said:

I'll share the meshfile

i made plugin for Noesis fmt_iaa.py

strange, but some meshes are simply huge compared to others


I changed the extension to *.iaa_mesh to avoid format conflicts in Noesis. (I have a lot of plugins for .bin) xd

I also added a flag to disable dividing the mesh into submeshes

Без имени-3.png

  • Like 1
Link to comment
Share on other sites

Posted (edited)

Wow, you are fast! 🤯

I was still tinkering in python 😅 thanks! I'll do some testing with the various models.

I dont understand why they made the wheels huge compared to the body 😂

In the overarching container files, there are also materials, cameras, render settings and textures and a dictionary with all the names for the parts and files. Maybe it's useful for people who want to import official factory 3d models into a game 😏 ps: thanks for pointing me to Noesis! 



Edit: Works like a charm!! Tested with some files from other brands as well, that have a slightly better scaling 😉 

Edited by Jille
Link to comment
Share on other sites

@Durik256, I had a look at your code, and if it's ok with you, I'll try to extend it with objectnames, textures and materials 🙂 

The .iaa container has a bunch of blocks inside, compressed with some proprietary RLE compression format. I'll make a script to uncompress each block on the fly, and feed the resulting bitstreams to Noesis. That way the complete mesh, including textures, materials and correct names for everything can be imported. 

In the past, I've done similar stuff with other infotainment systems, but that was limited to replacing 2D graphics. Some of the proof of concept pictures (I like to replace with something different than a car, as a proof of concept, otherwise people might not see what's new). 



Link to comment
Share on other sites

17 minutes ago, Durik256 said:


do you understand compression algorithms?

ps. о, я вижу кириллицу)

Yes, I find it a lot of fun 😄

Not Russian by the way, this picture was from a Russian friend who put the image in his radio 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...