o noobs'
hex to obj conversion (poor knowledge required)
It should allow u to extract 3D models with simple formats.
Means such games like Mafia2 or SleepingDogs not to be supported.
- preliminary -
Ok, the truth is - there are two things you should understand:
the hexadecimal numeral system (base 16) using the "numbers" 0..9, A..F
So 0x123 is 291 decimal.
(To avoid confusion with other numbering systems the hex numbers
are marked with 0x or an 'h'.)
Secondly you should be able to use a hex editor.
If you don't have these two skills leave now, and come back
as soon as you gained them.
(If you don't have a clue which hex editor to use: TinyHexer or HexEdit
by A.W. Phillips should do the trick.)
--------------------------------------
As I said you don't need to learn "basics" but you'll have to understand
"the structures" to use
hex2obj.
o So here is a
short tutorial on it's use. You don't need to know the technical terms - I just use them habitual.
Simple 3D models consist of
vertices and
faces.
hex2obj needs the following infos to perform it's task:
the
startaddress of the vertices and the one of the
faceindices.
(Some experience is required to find them but it's not too hard.)
Secondly we need the
vertices count and the
faceindices count.
I will explain this with a model example soon but now for the
structures -
the two most common are:
a)
"sequential" v x,y,z
v x,y,z
v x,y,z
v x,y,z
...
vn x,y,z
vn x,y,z
vn x,y,z
vn x,y,z
...
vt x,y
vt x,y
vt x,y
vt x,y
...
(
v: vertex position,
vn: normals,
vt: uv)
With a sequential model you only need to provide the above mentioned counts.
b)
"blocked"v x,y,z
vn x,y,z
vt x,y
v x,y,z
vn x,y,z
vt x,y
...
With a blocked model you need to chose the VertexBlock size, for example 32.
(And 'yes': the order might be v, vt, vn for example)
If you don't understand anything you'll have to do a trial 'n error.
Or you calculate the VB size: each coordinate (x, y or z) consists of 4 bytes.
So the above two blocks have a blocksize of 32 (8x4) each.
It might be a little bit more difficult if there are DWORDs contained in the blocks.
But anyway the most common blocksizes are 32, 40, 52. Sometimes 24, 44, 48 whatever.
o the v,vn,vt
patterns to search forwell, to identify what is v, vn or vt is the tricky part. This is for little
endian (for big endian the patterns are in reverse order of course).
v: xx xx xx nn with nn= 42..44 (these are rough values only, can also be 3F, 40)
vn: value of each component 0.0 .. 1.0 (1.0 = 00 00 80 3F)
square sum of components is 1.0 (autocalculated by hex2obj)
vt: value of each component 0.0 .. 1.0
It's important to know that half floats use two bytes only.
o Now lets start analysing our first model (We don't care for normals because they can be autogenerated in most 3D tools.)
We leave the "LitE" button as it is (little endian data).
The face indices are very easy to find since parts of the indices block look like a scrambled alphabet.
If we scroll through hw_bu_000.bm in a hex editor we'll find this:
To find the correct ending of the list is a very important step.
Here it's rather easy (0x
4845) because it's bound by a string size (09 000000)
and the corresponding string.
Rest of the tutorial to be found in the zip. Because you need to start
hex2obj.exeto get full use of the tutorial.
---------- These
outdated versions should be used
as a fallback only! ------------
v. 0.22
hex2obj_0.22.zipv 0.23b, exe only
Introduces "multi mesh" creation and the table button.
http://www.uploadmb.com/dw.php?id=1428534043-----------------------------------------------------------------
version 0.24chex2obj_0.24c.zip- uv preview
- allows face indices > 65535 (for non-tristripped meshes)
mapping of the tutorial example:
0x56 ..0x15C1 vertices
0x15C2..0x2B2D normals
0x2B2E length DWord and string "Texture"
0x2B39..0x3980 uvs, length: 0xE48
The v0.21
H2O format changed slightly. So you
can't use it with elder versions of the hex2obj.
hex2obj (v0.21) can read elder H2O files and will convert them to v0.21 when saving them.
(Be aware that there are various possible combinations of little/big endian, seq/VB, WORD/DW, noStrips/Strips and half floats/or not.
With any new version dozens of functions to be updated so there might be another bug.)
known bugs: v0.1: TriStrips starting on even addresses only
v0.2: wrong HF-uvs displayed in list box; ok with 0.2x
v0.2x: max. address= 0xFFFFFF
v0.22: for rare cases when there is a '
.' in a folder name:
........ model names without extension require a
.mdl to be added
before loading the model
v0.22c: TriStrips, superfluous degenerated faces
v0.23d: MMesh feature accidently disabled
v0.23d-f intermediate versions with
bug, don't use!
v0.24a uvs preview (float/VB)
reported bugs:
v0.21: wrong clipping for HF uvs
........ kao issue
v0.24:
libgcc_s_dw2-1.dll missing on W7,W8 (due to CodeBlocks/MinGW update)
todo listHTH,
shak-otay
Login
Register
FAQ
Search
)
Please re-upload your tools!
