It's byte face indices at 0x6DB in atl_hip.erf , a feature which hex2obj misses. (Maybe try out Bigchillghost's AMR?) . atl_hip-erf.png (first submesh only, used 82 vertices only instead of 137, see H2O file) Looks like there's 6 sub meshes in sum, face indices blocks preceeded by the string @aatl0 ...

well, pointing you to 0x13A4C which I thought being the start of the bodies uv data was wrong, my bad. the head is in 709B and the body should start in any part past that UVB of the head. There is another texture block but that correspond to the lod model, You have the solution, more or less, it's t...

View link in my sig or here But it's a quick workaround only. A capable hex editor (with "data inspector") would do better, I guess. (Can't tell which, because for me it's easier to just write some C code for tasks like this one.) The link to the download doesn't seem like it ever existed!...

(You need to unpack all three zips (part 1 and two see previous posts) into one directory of your choice to get hex2obj working.)

well, since uploadmb is down I'll create a new (temporary) hosting here until I've found another reliable hoster. Just unpack the three zips (part 2 and three see following posts) into one directory of your choice. -------------------------------------------------------------------------------------...

Can somebody make an in-depth tutorial about QuickBMS? Every tutorial I've found so far is either broken or doesn't have enough info. Well, I didn't even know that there are tutorials on it. Most info I have is from quickbms.txt which comes with quickbms. There's 100 s of bms scripts. Once I've a p...

Oh, thanks for your answer, I will certainly study what you provided and try to redo everything with rapi. But I decided for the time being in my own way) mariokart64n's tutorial uses the more manual means of constructing a mesh, which probably does seem more familiar to someone coming from Max. So...

Hi. good night, or good morning, i don't know if i'm too dumb or what :( , but i only got to display two models (the one you posted on the previous post and the other one mirrored) when i try to get more meshes all of them are messed up or they are empty like the one on the screenshot. Hi, good mor...

ok, are you familiar with floating point IEEE754 format? You'll need to understand at least where a coordinate component starts. I load 1993_alfa_romeo_155_v6_ti.points into hex2obj to give you the idea (any hex editor capable of showing floats should do, too). Here we go: . a-points-file.png You ne...

yeah, ok, but they're in place!? So we'd need some hint in the .points file for the misplaced steering wheel to get it's position offset, correct?

Maybe I didn't get what you meant with this:

ReVolt wrote: ↑Fri Mar 05, 2021 6:57 pm I'm converting Real Racing 3 cars, and I need a new way of figuring out where the wheels are positioned.

So it's for the wheels? Problem is, there's LOD_A_STEERING_WHEEL_mm_cab in the model file and POINT_WHEEL_BL, POINT_WHEEL_BR, POINT_WHEEL_FR, POINT_WHEEL_FL in the points file. But none of them is in both. :eek: (At least not from the ASCII names. Maybe they're referenced via hash, too, dunno.) (wel...

well, I just dived into the agsys_2048.rcsmodel and didn't find it too hard:
. (Maybe there's parts/blocks that are harder to understand - didn't have the time to check.)

You wouldn't expect someone digging into a .points file without having the belonging model file, do you?

models are already loaded but only with triangular faces, square faces give an error... You could use rapi.rpgCommitTriangles(idxBuff, noesis.RPGEODATA_UINT, numIdx, noesis.RPGEO_QUAD, 1) But as you can see it's the "latest Noesis style" (rapi interface) while you seem to use the old one....