[Help] Hex2obj

[ekmek]

I replicated what you did fine.

But when messing with other chunk files I was trying to figure our how you got:

"5CCE0: start of face indices (FI) list"


It's not clear in the tutorial to me. How did you get that number?

As I go through this I plan on helping out on your tutorial for noobs. written by a noob for noobs!

[shakotay2]

But when messing with other chunk files I was trying to figure our how you got:

"5CCE0: start of face indices (FI) list"

Assumed first face to consist of 0, 1, 2 (-> 1, 2, 3 in one based wavefront format)
so search for 000001000200 (little endian of 0000 0001 0002).

Doesn't work always because the first face might consist of other vertices, may 3,4,5 or something else.

[ekmek]

But when messing with other chunk files I was trying to figure our how you got:

"5CCE0: start of face indices (FI) list"

Assumed first face to consist of 0, 1, 2 (-> 1, 2, 3 in one based wavefront format)
so search for 000001000200 (little endian of 0000 0001 0002).

Doesn't work always because the first face might consist of other vertices, may 3,4,5 or something else.

ah, ok. I guess this where the hex editor comes in.


Do you recommend one?

[shakotay2]

My most preferred one is WinHex. But any other should do which has a decent search feature.

For me a byte grouping of 8 plus 8 is totally important (which HxD v 1.7.70 for example lacks of).

WinHex.JPG

[thunderkai]

I can not get any mesh to display on the attached file
some screenshots: http://imgur.com/a/kdUBC

[shakotay2]

face indices start address is correct; but it's 5 submeshes, search for 000001000200 to find the different startaddresses
next find: 0xFF04 (delta 0x2FF4 related to 0xCF10-> delta/2= 6138 face indices; vertex count= 1180)

Why set start of vertices to 0x1387? That's not senseful.

calculation CF10 + 35934x2= 0x1E7CC shows where to search for vertices.

knyitm001.JPG