This is so frustrating…Why is if that when I load a custom Normal map it works some of the time…
Example.
In image"Capture2" I created the map and it work as it should. Normal map are far better looking than bump but, in the situation the effect is to strong and I can reduce it in engine. (can you add a slide for this?)
So, I reduce the contrast to lower the strength but when i swamp the map out it goes from being color data to a bump map… Can you can see in image"Capture" bump is just flat with zero details and I know I can increase the slider but honestly it makes it look even more worst when it renders - Just a big ball of grain and noise.
So I guess I’m doing something wrong but what is it?
Reducing contrast of a normal map is not the correct way of reducing the strength as it invalidates the stored normal vectors (the color channels each represent a component of a 3 dimensional vector). After reducing contrast the vectors will no longer be normalized, which prevents Enscape from detecting it as a normalmap, but will also lead to incorrect shading (eventhough that might be subtle). You’ll have to regenerate the normalmap with different settings in that case or you use a tool that ensures the correct length of the normal vectors after post processing.
We do have the normalmap strength slider on our agenda - we’ll then do the correct post-processing on our end.
What causes a Normal Map to display as a RBG map (normal) and then out of no where change to a Black and White (bump) map?
Nothing in my Normal file has changed. There is a big difference display wise with Normal and Bump so how does this get corrected? Also why isn’t there a texture slot for just normal maps?
Attached is the Normal map generated directly form Substance - Please let me know why Enscape has decided that its no longer a normal map??
sorry to hear that. Albeit Preview versions may still be unstable, we’re of course very interested in what caused those issues. Did you report them via the Feedback button yet? Thanks in advance for any reports, that’ll help us iron out those issues faster for the upcoming 2.7 Release.
LOL So..? any thought to the original question on the current stable 2.6.1 version of Enscape? What is or does Enscape actually looking for to make a bitmap “Normal” or “Bump”. Would love some clarification on this - is it a bug or something else?
Were you able to get a different result? The map is generated directly from Substance - appreciated the insight.
Thanks - Glad to hear that will get the option for how materials are created. Good step forward for Enscape. Unfortunately, I can afford to take risks with beta versions as it not worth the risk when dealing with deadlines. Once 2.7 is stable I’ll explore the update. Sounds like its going to be a solid update.
Enscape assumes normal maps contain predominantly correctly normalized vectors per pixel - we do a limited set of samples to verify that, this apparently fails in some cases (either when normal maps are tweaked manually or supposedly some generators output such results):
As Matthias correctly mentioned, we’re aware of the problem, that’s why we’ve added an explicit dropdown for the 2.7 release to counter that issue:
If that’s no option for you, you could export a heightmap from Substance instead and use this. The resulting normalmap Enscape generates internally will most likely appear quite similar.
i assume i found a reason why normal maps get sometimes interpreted as bump map.
I had also an exported image from Substance Player. Substance exported this PNG in 64Bit. When i load that Normal map in it automatically turnt in a bump map. If the imported Image(in my case PNG) was 32Bit or less it was correctly interpreted as Normal Map.
maybe that could be something to do with.
Is this behavior already known or some kind of Bug Maybe ?
