Thanks for this neat looking tool! Sadly i got this error: you can ignore it - it's a warning only. So does the tool give me (if everything works correctly) the adresses of every SM? You never can be sure. :D (The answer can only be given for a specific model where you assume some SM to be missing ...

-you have to do alot of guessing when it comes to finding start of vertecies and faces well, you could use this tool to ease getting the params (not perfect, so some guessing remains... (: ): . Make_obj-MEcko'sGU.zip (attention: some lines in the logs are pure nonsense, for example for Trane: # 0 F...

MarieRose1301 wrote: ↑Sun Oct 06, 2019 5:25 pm I've tried using floats, and it does not freeze anymore, no bones pop out either though

You need to add
mdl.setBones(boneList) before mdlList.append(mdl)

For the endianness thingie: I think readBytes(count) simply reads "byte by byte" no matter which endianness was chosen.

yeah, this line in the else: path of your bone loop makes it crash: MTRX = ROT.toMat43() Some ROT values are too big, I think: Detected file type: The iDOLM@STER One For All Model PTR 32 60776 214 1 (0.0, 0.0, 0.0) 2 (0.0, 0.0, 0.0) 3 (0.0, 0.0, 0.0) 4 (0.0, 0.0, 0.0) 5 (0.0, -632378032652288.0, 0.0...

(Posted due to a user's request and because I couldn't find an appropriate batch - though I have a deja vue there's already a solution somewhere on xentax) Usually quickbms is used for extracting a bunch of (compressed) files from archives (*.pak or such). But there's bms scripts which handle one si...

very few people only can judge from a picture

Still freezing? See a suspisious NoeBone () line, where you shortened the params list.
(I know that's possible in C, in python, too? Just in case...)

params
noeBone = NoeBone(len(noeBones), boneName, boneMatrix, boneParentName, -1)

Trane's head:
.

Trane, 2nd SM and bottle belt:
.

shakotay2 wrote: ↑Thu Oct 03, 2019 8:51 amFor him I got a point cloud only for the 2nd SM.

well, the trick is to keep the start of vertices of the first submesh:
. I assume there's still 75 vertices left (688 + 285 +75)

edit: well, I think I've got the scheme now how it's working... (FI count is 144, though)

Next face indices' (FIs) block at 0x61e7 + 361x36 (dec.) = 0x 94ab So there's a "wide range of guessing". :D The assumed start of face indices usually is NOT the start here as you may have noticed. :) You need to look at the hex dump in my post as of Thu Oct 03, 2019 8:51 am to understand ...

EDIT: could it be that tranes second submesh starts directly where the first one ends? You need to try it out. There's face indices counts before the submeshes (SM) start. For spleen 1300 precedes the fst one (so it's not 1305 as in my previous post). For him I got a point cloud only for the 2nd SM...

you can't start at 0x94b9 because of f 1 2 3 f 2 4 3 f 3 4 5 f 4 6 5 f 5 6 19 f 6 20 19 f 19 20 21 f 20 22 21 f 21 22 29 f 22 30 29 f 29 30 31 f 30 32 31 f 31 32 39 f 32 40 39 f 39 40 41 f 40 42 41 f 41 42 43 f 42 44 43 f 43 44 45 f 44 46 45 f 45 46 1301 <<<< f 46 1 1301 <<<< correct start address o...

Edness wrote: ↑Tue Oct 01, 2019 3:15 pmIs my general line of thinking at least right?

I hope so. Start of vertices is 0x0C9E for me. FVFsize is 8 for hex2obj. (You need to "translate" that into padding/padding intern for the MR.)

I think I've got the face indices set right, where? how? Could I at least see what you set for the unlock_maid to get it drawn properly? well, it's not "drawn properly". It has too many superfluous faces. (Or is the V2 model supposed to look like so?) The params are "as always" ...

I've been working on a project related to The Sims 2 for the PS2 for quite some time. Most of the stuff doing work with textures and sound and similar to that is already out of the way, all that's left are the 3D models that just baffle me. Either I am dumb/too tired or awful at reading and couldn'...