XeNTaX

https://gyazo.com/b2d00ede9899eb8315452ab777e0d3db
is a build im working on

brianmoyano wrote:Hi, i don't know if this is the best place to ask, but since we have the files for the game, can we get the images of the cars with transparent backgrounds?

Like this one

only if they're stored as an image format and not rendered real time whilst in game, out of interest why do you need it? Surely this cannot be only source where such images can be found

Added _library folder, thanks to GTAIV Modder for pointing this out to me and added an icon to the program..
Download here:https://github.com/Frazzlee/MakeH2O-Plugin
Next update will hopefully use MakeH2O to open the files and create the obj directly so minimising work needed to convert to obj : )
p.s. Will also take a look at dash scaling issue when I have time...


Edit 20:56pm : Added new source so I don't have to do it later

Frazzlee wrote:

brianmoyano wrote:Hi, i don't know if this is the best place to ask, but since we have the files for the game, can we get the images of the cars with transparent backgrounds?

Like this one

only if they're stored as an image format and not rendered real time whilst in game, out of interest why do you need it? Surely this cannot be only source where such images can be found

I think some images like the one that i uploaded should be local stored because it's a stock car, i don't need the tuned ones.
And the reason is because i wanted to make a design and use this resources, and it's pretty hard to find a set of consistent cars, with the same scale and angle.

They are in the stripped folder from what i can see.

fixed a bug with Aston Martin Vulcan (ast_vulcan_16), body_a.modelbin, reported by SonyKalien; thx!

Be aware of such lines in the obj files:
# body_a.modelbin, # uv-sizes 24 24 32 32 28 32 32 32 32 36 36
which should help to decide which uv offsets to choose.

There's 11 uv blocks. The first one has the uv channels 2, 3, 4 at offsets 4, 8, 12,
the 6th one should have 2 3 4 5 (at offsets 4, 8, 12, 16),
the 8th and 10th should have all 5 sets (unchecked, so this has to be proven!)

minime891 wrote:They are in the stripped folder from what i can see.

Wow, i think i'm in love with you. I already have the Devbuild (Opusdev) in my computer, can i find it there? What's the location?
If not, can you share it with me?

shakotay2 wrote:fixed a bug with Aston Martin Vulcan (ast_vulcan_16), body_a.modelbin, reported by SonyKalien; thx!

Be aware of such lines in the obj files:
# body_a.modelbin, # uv-sizes 24 24 32 32 28 32 32 32 32 36 36
which should help to decide which uv offsets to choose.

There's 11 uv blocks. The first one has the uv channels 2, 3, 4 at offsets 4, 8, 12,
the 6th one should have 2 3 4 5 (at offsets 4, 8, 12, 16),
the 8th and 10th should have all 5 sets (unchecked, so this has to be proven!)

could you make it so that your program can open the files as a default settings, so as to say dragging the modelbins.txt into the exe would work?

I was thinking about command line parameters, or using the exe in a batch, but found it less important.

Separate obj files to be created for Exterior, Interior and _library (CAD_ATSV_16) when parsing a
scene-modelbins.txt for example would make more sense to me.

The more important things on the todo list are complete uv maps, the movable parts, the suspensions, the dashboards.

Just in case it's of any use to someone - I did a comparison of UV mapping as produced by MakeH20.

This is the SLOD parts from Lambo Cenentario. In game it has a carbon fibre material. This is produced by a tiled normal map across the body. The map is mirror-imaged down the center of the body (via flipped UVs not normals?), so the car parts are also split down the centre, except for lower LOD's. Also, after a quick hex thru the meshbins to get material and map names, it appears that lower LODs may use slightly different materials. In this case I suspect that the lower LODs have a separate material for left and right instead of mirrored UVs using the same material. I could be wrong about this, this is just an observation

shakotay2 wrote:I was thinking about command line parameters, or using the exe in a batch, but found it less important.

Separate obj files to be created for Exterior, Interior and _library (CAD_ATSV_16) when parsing a
scene-modelbins.txt for example would make more sense to me.

The more important things on the todo list are complete uv maps, the movable parts, the suspensions, the dashboards.

yeah the command line params need to be changed, what language is it written in?

@SoniKalien: what happened to the images in your post?

Frazzlee wrote:yeah the command line params need to be changed, what language is it written in?

it's C (exe as a GUI app)

dragging the modelbins.txt into the exe would work?

"dragging onto" works for console applications only, afair.

It's possible to use WM_DROPFILES, i.e. you could drag 'n drop the modelbins.txt into the extractor's window but since it has a one-shot-only structure that doesn't make too much sense.

A professional solution would be doing a recursive search for modelbin files and having them displayed as a list where to choose from with multiple selections.

But since my time is limited I decided to use dir /s /b *.modelbin > modelbins.txt which I found to be a very efficient way of collecting.

shakotay2 wrote:@SoniKalien: what happened to the images in your post?

Fixed sorry

Things are going pretty well with the last JM, JM4 and 5 are O.K., i can do things like that:

or

Each model can take for me 30 mn to 2 hours to have something correct using Blender.

At the end models are pretty good looking :



but there are some cars that simply don't want to be converted, as for example the AMC Rebel "the machine", which make every H20 version crashing, and lead to an incomplete obj.

Does anybody here havec some insight wether its coming from the original modelbin and its extraction or from the conversion by H2O and so can be done at the end.

Thanks in advance!!

shakotay2 wrote:@SoniKalien: what happened to the images in your post?

Frazzlee wrote:yeah the command line params need to be changed, what language is it written in?

it's C (exe as a GUI app)

dragging the modelbins.txt into the exe would work?

"dragging onto" works for console applications only, afair.

It's possible to use WM_DROPFILES, i.e. you could drag 'n drop the modelbins.txt into the extractor's window but since it has a one-shot-only structure that doesn't make too much sense.

A professional solution would be doing a recursive search for modelbin files and having them displayed as a list where to choose from with multiple selections.

But since my time is limited I decided to use dir /s /b *.modelbin > modelbins.txt which I found to be a very efficient way of collecting.

ahh c, and idk if you've seen my plugin (collects modelbin files from all dir and writes to respective modelbins.txt), but I wanted to do it where it uses exe to directly produce the obj's too
p.s. could you take name of folder in which modelbins.txt is in and have that as the obj name pls, i'm happy to help