XeNTaX

So I have been successfully extracting multiple models from pinshape and their .bingeom files. However, I have one file I cant seem to properly extract. It is the first file on this page: https://pinshape.com/items/55281-3d-pri ... ns-upgrade which gives the following hex file: https://cdn.threehub.com/resources/9ae4 ... e1.bingeom
However, running this through hex2obj using the method that has worked thus far gives the following result

The vertex count is clearly too high, but I cannot seem to determine why that is. Any help on this would be appreciated.

Hi kgal104,

the face indices are bytes for the file you posted which hex2obj doesn't support. (maximum face index=182 -> vertexcount )

You may try out the tools from Bigchillghost or Lazov which should have that option.

Here*s the obj file with "manually" created face indices:
.

I'm having the exact same issue. I tried applying what little I knew about hex2obj to 3d model researcher and advanced mesh reaper to try to learn how tey operate and maybe then progress to this newer version of the bigeom files, but I'm not there yet. Can anyone point in the right direction? How to use any of these utilities to extract the 3d model? Either version of the bigeom files would be greatly appreciated.

bingeom from the opening post in AMR:
. (You'll need ViewScene.exe and dlls to be put in AMR.exe folder to display the mesh using the "Proceed" button.)

Thank you so much, it seems that I finally wrapped my head around this ( or at least I like to think so). I applied your new information and I correctly opened the above file, next I went to other targets namely the ones that I used to open with hex2obj. With these I had to do the following:

Example file
https://cdn.threehub.com/resources/1b13 ... fd.bingeom

subtract 4 from the address, divide it by 2, convert to decimal and set the data type = uint16

The interesting thing is that I found another variation. It seems that depending on the filesize there are difference on how they are saved:

Example file
https://cdn.threehub.com/resources/2a49 ... ae.bingeom

subtract 4 from the address, divide it by 4, convert to decimal and set the data type = int32

Some more info: if you look at the end of the file, there is some text info that tells you how the data is stored. So in the attachment in the first post, you have this:

{"type":"PolyMesh","faces":{"o":0,"l":1092,"b":1},"faceCount":{"o":1092,"l":4},"positions":{"o":1096,"l":2184},"colorMaps":{},"uvMaps":{},"blendShapes":{}}

It tells you that the faces start at 0, 1092 entries, size is 1 byte per entry, etc. - "o" is the start offset and "l" is the length in bytes, "b" is the size of each entry.

The very end of the file gives you the size of this text data, so you can go back that amount of bytes to get the start of it.

Doh! Prime example of being so fixed in the details that one misses the solution right in front of you. Well at least now I'm a little more familiar with these things, live and learn.
It shouldn't be too hard to code a script for noesis and automate this all process.

Here's an initial basic Noesis script that should read the vertices and faces correctly from the text info supplied in the file.

You'll need to rename the files as *.bingeom for the script to work.

Works perfectly
Probably the first time that I opened a noesis script and could actually understand what it was doing just by reading it all.