Official 3D art thread - Warband
- Thread starter WeeSeng
- Start date
Users who are viewing this thread
The handle is longer in comparison to the stick and the spikes are way bigger in the reference.
Specialist
Master Knight
A wee bit of my work.
I am having some issues with a mesh distorting in game, which is first i've ever seen of it -
It's triangulated, so i'm not sure wtf is causing it. It shows up fine elsewhere including BRF:
Disregard the texture as it's still wip and being added to/ refined, so i'm not looking for feedback there.
Can't figure out wtf is up with the mesh.
It's triangulated, so i'm not sure wtf is causing it. It shows up fine elsewhere including BRF:
Disregard the texture as it's still wip and being added to/ refined, so i'm not looking for feedback there.
Can't figure out wtf is up with the mesh.
Hmm that's odd one considering I used male_head as model reference
And i'm fairly certain I was considerate to make no collisions, though maybe on the inside of the cheekguards. Reading the thread I see there are some workarounds with the multimesh, which I may end up doing.
I guess the actual "head box" is much more significant than what male_head presents, since looking at the back of the helmet it is distorted there. Is there anywhere that the true borders of such a 'head box' is represented.. in Native files perhaps?
And i'm fairly certain I was considerate to make no collisions, though maybe on the inside of the cheekguards. Reading the thread I see there are some workarounds with the multimesh, which I may end up doing.
I guess the actual "head box" is much more significant than what male_head presents, since looking at the back of the helmet it is distorted there. Is there anywhere that the true borders of such a 'head box' is represented.. in Native files perhaps?
Hm, don't know about head box in native files?
About problem:
1)
When you make multimeshes for helmets, the first mesh will be distorted the second wont. So just make one triangle and put it inside of helmet. The helmet itself will be the second mesh, and thus not be distorted.
Multimeshing goes like this in openbrf:
helmet ------triangle for distorting
helmet.1 ------helmet
2)
The other solution is to "rig" the helmet, right click on it, choose mount on one bone-->human-->head-->at origin. Of course don't forget to leave one nonriged helmet as an inventory item.
Coding for rigged helmets goes like this:
barbut is rigged mesh
barbut_inv is non rigged mesh for inventory window.
About problem:
1)
When you make multimeshes for helmets, the first mesh will be distorted the second wont. So just make one triangle and put it inside of helmet. The helmet itself will be the second mesh, and thus not be distorted.
Multimeshing goes like this in openbrf:
helmet ------triangle for distorting
helmet.1 ------helmet
2)
The other solution is to "rig" the helmet, right click on it, choose mount on one bone-->human-->head-->at origin. Of course don't forget to leave one nonriged helmet as an inventory item.
Coding for rigged helmets goes like this:
Code:
["barbut_helmet", "Barbut", [("barbut",0),("barbut_inv",ixmesh_inventory)], itp_type_head_armor|itp_attach_armature|itp_merchandise, 0, 469, weight(2.75)|abundance(100)|head_armor(45)|body_armor(0)|leg_armor(0)|difficulty(8), imodbits_plate ],barbut is rigged mesh
barbut_inv is non rigged mesh for inventory window.
I reckon i'll take a look at multimeshing to resolve the issue.
I would suspect that the first mesh won't be distorted so long as it doesn't collide with the 'head box', regardless if further meshes do?
I've never been big on multimeshing though, since I can't quite seem to figure out how/if lods work with them.
Well, regardless thanks you two for the help.
I would suspect that the first mesh won't be distorted so long as it doesn't collide with the 'head box', regardless if further meshes do?
I've never been big on multimeshing though, since I can't quite seem to figure out how/if lods work with them.
Well, regardless thanks you two for the help.
LoDs work fine with multi-meshes, they just need to be named along the lines of 'model.lod1' and 'model.lod1.2' ect.ealabor said:
And here we go, I retextured it from it's first texture, I don't know if it is true to show it again but I wanted to show it because I spent a lot of time on it:
Rigadoon said:First time using a spec map, not really good at using it. Any suggestions are appreciated.
And uh, can anyone tell me what classification this sword would be in?
Looks like some form of short broad sword. I like it
Only real suggestion is a texture one - reduce the levels of blue in the texture. Other than that, it's nice.
thats a gorgeous normal map Elaborealabor said:I am having some issues with a mesh distorting in game, which is first i've ever seen of it -
It's triangulated, so i'm not sure wtf is causing it. It shows up fine elsewhere including BRF:
Disregard the texture as it's still wip and being added to/ refined, so i'm not looking for feedback there.
Can't figure out wtf is up with the mesh.
If you are sure you didn't rigged the helmet, it is probably because of the "fit to face" command at it's tupple at module_items.ealabor said:I am having some issues with a mesh distorting in game, which is first i've ever seen of it -
It's triangulated, so i'm not sure wtf is causing it. It shows up fine elsewhere including BRF:
Disregard the texture as it's still wip and being added to/ refined, so i'm not looking for feedback there.
Can't figure out wtf is up with the mesh.
Darken the blade so it doesn't shine like a lightsaber. Second, don't make the spec map that intense.Rigadoon said:First time using a spec map, not really good at using it. Any suggestions are appreciated.
And uh, can anyone tell me what classification this sword would be in?
