It's ok but i think that the "short all" method must be the one used because you get the normals, how are you converting those 2 bytes in "short all" method? like described in my post before i was thinking that you were using hf kind of conversion but now i see that you were ref...

It's ok but i think that the "short all" method must be the one used because you get the normals, how are you converting those 2 bytes in "short all" method? i was thinking that you were using hf kind of conversion but now i see that you were referring to another type.

it's all wild guessing atm, the data might be compressed, shrinked, whatever. You could switch to HF_all in hex2obj but after pressing the go2 button you'll see that the result is not senseful: asteroid_HF.JPG v 339 94208 0.067566 or v 5436 0.006973 0.06427 for example are assumed to be wrong verti...

that's the reason why I've switched to ShortAll ('short' means 'signed int', 'All' means verts AND uvs, which isn't proven so far). First you say that in our 0x10 or 16 bytes lines instead of v(x,y,z,w?) x 4b there is v(x,y,z),vn(x,y,z),vt(u,v) x 2b right?. THat make sense according to the .WDR for...

i'm using a simple java app ("REALLY SIMPLE") to get 2 bytes integer from "index-data-decompressed.block" great ! :) That's what most beginners lack in: to gain basic coding knowledges. So java is a good start! As for your asteroid; I've a deja vue but I can't really recall from...

this all is a little bit confusing to me (maybe you should give your thoughts more structure? :wink: ) First of all I don't think that it's floats in your asteroid_18800-0x2D60-vertex.block Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 000000 5D 4C 7D C0 2C 53 30 03 11 FF 74 FF CF 80 7F FF 2ndly when I us...

f 0/0 1/1 2/2 wavefront obj face indices are 1-based. Add 1 to each face index. btw: very interesting that you deal with edge compression! :) But you're producing walls of text; sadly I don't have the time to go through it. :cry: Yeah i wrote a lot of text i will try to make it shorter, Thanks for ...

Good news i think i managed to get vertex values (x,y,z,w?) floats extracted from the block that i "BELIEVE" that have vertex positions, as i say on the post is the block located always maybe all .cdr from what i see on (0x15800+CPU SECTION LENGTH) in the case of asteroid cdr it was 0x3000...

Hello people, a lot of work have been done about drawables of RAGE engine on pc and even on x360, for example on x360 there is this xdr2obj https://github.com/tgascoigne/xdr2obj but nothing for the ps3 version because there is a different approach to store index and vertex data. There is a documenta...