1st of all: learn how to detect floats. If you can't you're lost. As simple as that. floats consists of 4 bytes (half floats of two). You need to gain experience by checking some dozens of simple examples in the forum where hex2obj was used. And you need to learn some basics. Understand how to get 1...

using hex2obj (view links in my sig):

Quick check usx using hex2obj, one submesh only: (unsure about uvs)

Using hex2obj (view link in my sig) you need to load the xbg, enter the parameters from the picture in my previous post then File/SaveAs mesh and you're done. You can also copy the following lines into a text file, rename it to whatever.H2O and load it with File/Open H2O : 0x406D4 22899 Vb1 40 12 0x...

import obj to blender; in UV/Image Editor
a ctrl my <ENTER>
(select all, invert uvs vertically)

sy <ENTER>
(scale y)

zerenium wrote: ↑Fri Mar 01, 2019 4:43 pmScaling the Y is a good work around, thanks!

It's no "workaround", it's THE solution.

What do you mean with " the helmets require UV indices"?
why not scale ty?

Problem is that vertex stride is 32 for the first submesh; script is very hard to debug for me. [(1, 1062, 1062, 3186, 32, 666, 3018), (-1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, ...

Can't serve with any scripts, sorry, but I've got the table data (for use with hex2obj ). Seems there's 4 lod levels, the formula for lod1 meshes is (n-1)x4 +1, so for 3rd mesh object lod1 is #9 (1, 5, 9, 13, ..). FI addresses in parenthesis (1cf1e or 1e4c6), first one is for FVFsize of 32, second o...

Mesh format looks simple; getting the submeshes might become a tedious task, though:

okay ill try that, i still havent quite get the way you got the fvf size, It's no rocket science: you look at the data for patterns and in most cases they're easy to find: FVF = 36 bytes.png (another pattern here is 00010000) since the tutorial version its not sequential here it's not sequential, t...

but any object in trucks file im not being allowed, the obj tester just opens and closes There's a rather simple solution for this: open test.obj for that model in notepad , scroll down to first "ugly line", place cursor, then Edit/Go to..., a line number is being displayed, subtract 1, u...

this is a part of the truck; I don't see where the problem should be with just floats? (Getting all the subeshes would be a little bit tedious but I'm too busy to include it into the Make_obj project.) trucks_7oqkolj.png H2O file for lower mesh in above picture (FVFsize= 36): 0x27C7B1 127467 Vb1 36 ...

rodrigo2397 wrote: ↑Wed Feb 20, 2019 9:33 am( yes i have read all of the tutorial also )

hello, that's nice, but the link to the sample you've provided has expired.

I've made a small patch: for m in range(lodCount): x=g.tell() g.seek(x+16) mesh=Mesh() but as you can see there's the next hurdle in PMCU chunk. Don't have the time to fix this so you might wait for the author. console output: Avatar[PC]\navi_willow_tree.xbg -----------------------------------------...

how should anyone know without one of those problematic samples?