Normal maps looking different from Substance Painter to Marmoset?

Danface

Hey, 

I've had issues before where normals maps in UE4 look 'wrong' with artefacts on edges and whatnot but in Marmoset, they all looked fine - it was just the way it was being shown in UE4. 

Now however, I'm having the problem where my baked normals look fine in Substance but in Marmoset I have dark edges, almost as though the low mesh is too far away from the high or too close. I should also note that I'm still currently trying to perfect the art of baking so it could be a fundamental problem with how I am doing things or it could be something to do with how Substance normals look in Marmoset.

The first image is the normals viewed in Substance and the second image is how the same normals are seen in Marmoset




Any help would be greatly appreciated

EarthQuake

Hit the flip Y checkbox in the normal map settings, also check out this tutorial on baking/normal maps in general it has a lot of good information: https://www.marmoset.co/posts/toolbag-baking-tutorial/

waedoe

Another could be when you create a new mesh, I have had issues depending on the setting in substance painter 2

"compute tangent space per fragment"

https://support.allegorithmic.com/documentation/display/SPDOC/Project+Configuration

The "compute tangent space per fragment" is used to compute and display the normal map. If enabled, the tangent and binormals of the mesh will be computed in the pixel shader. 

• Unity requires this setting to be disabled. 
• Unreal Engine 4 requires this setting to be enabled.
  

Danface

That works

It's sad that something like this makes me as happy as it does but thank you!

Danface

waedoe said:

Another could be when you create a new mesh, I have had issues depending on the setting in substance painter 2

"compute tangent space per fragment"

https://support.allegorithmic.com/documentation/display/SPDOC/Project+Configuration

The "compute tangent space per fragment" is used to compute and display the normal map. If enabled, the tangent and binormals of the mesh will be computed in the pixel shader. 

• Unity requires this setting to be disabled. 
• Unreal Engine 4 requires this setting to be enabled.
  

It's frustrating that nowadays, we all use one program to do 1 thing and another to do something else, but there isn't a clear guide as to what works with what and how this interacts with this so when things go wrong, it can be a minefield trying to find a solution online.