normals randomly flipping with xoliul

garriola83

Hi, I'm Gene and I have a problem.

I am using 3DS Max 2013 with the Xoliulshader2009.fx without the interface. I have this 3D model and I have baked the normals on them already. The problem is that when I open the file it would randomly be flipped, or correct. Now, when I flip the green channel it looks even worse. So I don't think its the bake but rather the shader itself? Maybe it's not playing nice with 2013.
One time I did delete the old file from the folder, renamed it and it worked. So something screwy is going on...HALP!

Any thing towards a solution would be greatly appreciated!

garriola83

I would also go to my older files and the normals are fine but some reason, my newer files would have that seam and the normals are jacked up.

Ace-Angel

Did you disable the LUT/Gamma thingy and go to DX9 instead of the Nitrous Viewport?

Also, clone your mesh and delete the old one, does the problem persist?

Did you make any changes on the mesh after baking the map?

garriola83

Gamma/lut is off
Nitrous is off im using Directx9 viewport
actually sometimes when i clone it, it makes it error out like that.
When I start attaching things to the mesh, like last minute attachments, SOMETIMES, it flips out. But sometimes, it doesn't...weird

garriola83

Theres no issue in 2012 tho, so I've reverted back to 2012

Kurt Russell Fan Club

I remember a thread recently where someone had something looking like this error and iirc the fix was to do with welded uvs...? Not very useful

Ace-Angel

Well, if Max 2012 isn't doing the issue and 2013 is, it's understandably so with all the patches, fixes and packs, Max 2013 could have a bug or two that will need a couple of months of fixing, so I would suggest, if necessary, to work in Max 2013 and save it out as Max 2012 file, end viewport from there.

Kwramm

In older Max versions the mesh would sometimes become buggy after working with it and show odd normal behavior. Exporting to obj; Loading in some other app and saving it there; Importing the saved obj again into Max would fix that.
You could try that as last resort.