[Archive] Mesh normals are bad ingame
[Archive] Mesh normals are bad ingame
Original source
M2mod automatically makes the normals retarded everytime I change the format to M2i. I have to go through a roundabout way of fixing this each time and it's fairly annoying to have to incorporate that into my usual process.
![[Image: ioiSuSR.png]](http://i.imgur.com/ioiSuSR.png)
rektbyfaith
05-26-2017, 11:00 PM #1Archived author: XodusArt2 • Posted: 2017-05-26T23:00:04+00:00
Original source
M2mod automatically makes the normals retarded everytime I change the format to M2i. I have to go through a roundabout way of fixing this each time and it's fairly annoying to have to incorporate that into my usual process.
Original source
I'm curious on how you manually fix normals. In my mind it always have to do with the game not understanding character modelling and that that was something we can't do shit about
Do you have bullshit deathknight eyes on some edited models too ? Like big black square around texture on the glow blp and even if you edit renderflags or the blp it doesn't do anything. Sometimes it can be litteraly transparent face
rektbyfaith
05-27-2017, 10:25 AM #2Archived author: Roccus • Posted: 2017-05-27T10:25:46+00:00
Original source
I'm curious on how you manually fix normals. In my mind it always have to do with the game not understanding character modelling and that that was something we can't do shit about
Do you have bullshit deathknight eyes on some edited models too ? Like big black square around texture on the glow blp and even if you edit renderflags or the blp it doesn't do anything. Sometimes it can be litteraly transparent face
Original source
Normals are part of model. 3d stuff, absolutely nothing to do with game engine (apart from fact that it uses them, but so it does with UV maps, topology, vertex paint and so on).
rektbyfaith
05-27-2017, 12:03 PM #3Archived author: Amaroth • Posted: 2017-05-27T12:03:47+00:00
Original source
Normals are part of model. 3d stuff, absolutely nothing to do with game engine (apart from fact that it uses them, but so it does with UV maps, topology, vertex paint and so on).
Original source
Yep that's what i realised. Still annoying thing 'cause custom cloak work, game cloaks aren't. I tried to delete the flip normals layer of the standard long cloak model, it didn't work. Then i duplicated the normals et flip them To do my own flip layer still didn't work. I'm interested in the subject
rektbyfaith
05-27-2017, 12:13 PM #4Archived author: Roccus • Posted: 2017-05-27T12:13:46+00:00
Original source
Yep that's what i realised. Still annoying thing 'cause custom cloak work, game cloaks aren't. I tried to delete the flip normals layer of the standard long cloak model, it didn't work. Then i duplicated the normals et flip them To do my own flip layer still didn't work. I'm interested in the subject
Original source
I had the same issue with the new modredux but it is no problem to fix it, just go in blender on the cloak, select one verti hit strg and +, and as you can see it has in blender two sides.The old modredux handle this but the new one not.So just delet one side and after converting it to m2 goo to skin file 0 and 1(and yes in both!) search the cloak and make the renderflag to "Rf_two sidet" and Rm_Opaque" most its the flag 0.
It is more work but at the end you have fewer polygons.
rektbyfaith
05-27-2017, 02:05 PM #5Archived author: Finsternis • Posted: 2017-05-27T14:05:18+00:00
Original source
I had the same issue with the new modredux but it is no problem to fix it, just go in blender on the cloak, select one verti hit strg and +, and as you can see it has in blender two sides.The old modredux handle this but the new one not.So just delet one side and after converting it to m2 goo to skin file 0 and 1(and yes in both!) search the cloak and make the renderflag to "Rf_two sidet" and Rm_Opaque" most its the flag 0.
It is more work but at the end you have fewer polygons.
Original source
Nice To know i changes renderflags in m2 before but not in skin00 and skin01 but still have you for an est way To find what textureunit le linked To what mesh ? WMV model control does lot help
rektbyfaith
05-27-2017, 02:38 PM #6Archived author: Roccus • Posted: 2017-05-27T14:38:03+00:00
Original source
Nice To know i changes renderflags in m2 before but not in skin00 and skin01 but still have you for an est way To find what textureunit le linked To what mesh ? WMV model control does lot help
Original source
ya look in the wmv model control search the id.
This id is the same like in skin00. Then look in the skin00 the struct Sub submesh and look for the unit32 id (on cloacks it was 1502 +)
Go to the skin01 file and search the 1502+ id(it is higher then the id in skin00) in the struct Sub submesh it is not just one it can be more there you need all.
Then struct TEXU TextureUnits with the same number as the struct SUB Submeshes and edit there the flag and finish^^.
This was alot try and error a year ago to fix the transparence on cloaks
.But with this it should work
rektbyfaith
05-27-2017, 02:45 PM #7Archived author: Finsternis • Posted: 2017-05-27T14:45:37+00:00
Original source
ya look in the wmv model control search the id.
This id is the same like in skin00. Then look in the skin00 the struct Sub submesh and look for the unit32 id (on cloacks it was 1502 +)
Go to the skin01 file and search the 1502+ id(it is higher then the id in skin00) in the struct Sub submesh it is not just one it can be more there you need all.
Then struct TEXU TextureUnits with the same number as the struct SUB Submeshes and edit there the flag and finish^^.
This was alot try and error a year ago to fix the transparence on cloaks .
But with this it should work
Original source
Great info thx mate you erased a great problem of my project
rektbyfaith
05-27-2017, 02:47 PM #8Archived author: Roccus • Posted: 2017-05-27T14:47:18+00:00
Original source
Great info thx mate you erased a great problem of my project
Original source
well i fix it a diff way.
select entire mesh, recalc norms
then select one face, and face step select the rest.. ctrl + I to invert selection, then hide, then select all visible and remove doubles
unselect all, then unhide, ctrl I, rinse repeat.
then just enable "double sided" in blender
rektbyfaith
05-30-2017, 02:19 PM #9Archived author: XodusArt2 • Posted: 2017-05-30T14:19:03+00:00
Original source
well i fix it a diff way.
select entire mesh, recalc norms
then select one face, and face step select the rest.. ctrl + I to invert selection, then hide, then select all visible and remove doubles
unselect all, then unhide, ctrl I, rinse repeat.
then just enable "double sided" in blender
Original source
Maybe the problem are not the normals, but a renderflag set to "two sided". It causes the two overlapping faces to show up in the same view, causing some artifacts.
Just change the renderflag from "two sided" to "none" with 010 editor.
If the renderflags are already set to "none" then it is a normal problem indeed.
rektbyfaith
05-30-2017, 06:14 PM #10Archived author: Inico • Posted: 2017-05-30T18:14:40+00:00
Original source
Maybe the problem are not the normals, but a renderflag set to "two sided". It causes the two overlapping faces to show up in the same view, causing some artifacts.
Just change the renderflag from "two sided" to "none" with 010 editor.
If the renderflags are already set to "none" then it is a normal problem indeed.
1 Guest(s)
1 Guest(s)