I have a strange problem, my normal map gets cut. Why?

I get the same problem if I bake in xNormal or Projection in 3Ds max. So is there a problem with the cage? The cage is covering the high with no problem. I dont get the same error on the upper side. Only the sides and the back.

What may cause this?

Thanks!

Anyone? It does not appear to be any better if I redo the cage.

That must be your cage yes.
You haven't posted any pic of it so it's hard to tell by the way.

Originally Posted by funshark

That must be your cage yes.
You haven't posted any pic of it so it's hard to tell by the way.

It worked fine if I didnt use the cage in xnormal.

This is what it looks like when edit mesh is applied:

.

Yep, that might be the second cause.
Can you post a screen of your high poly in the side view ( ortho )?

It looks more like the top row of vertices is bent skewing the projection. So, yeagh, fix your cage. Try looking at your smoothing groups as well.

Cut a loop in around the top of your mesh, on the line where the inset is skewed(disapearing).

This happens because the normals of your projection mesh are averaged around the top, but it looks like you have an extra loop at the bottom to support those cut-outs. Thats why you don't see the same skewing on the bottom.

More info here: http://www.polycount.com/forum/showthread.php?t=81154

Adjusting your cage is a messy solution, and unlikely to give you enough control to match the detail on the bottom.

Messing with smoothing groups(and not using a cage) is even messier, and will cause gaps in the projection around hard edges.

Messing with smoothing groups while using cage will have no effect.

Additionally, you may want a supporting loop on either end of the mesh, as the bevels on the sides skew out further towards the ends.



timwiese: The top has the same bevel detail as the sides/bottom, as clear from the screenshot of his highpoly.

EarthQuake, thanks that worked!

Is it ok to optimize like this?

(images taken before threadstart)