I am getting this warning : // Warning: File texture “BMC_Excavator_V_Ray:file126” used as normal map has a color correction enabled. This may lead to unexpected results.
The normal maps are not displaying properly either…getting some mixed weird results.
I am new to V-ray and cannot find a solution to this.
I have searched the forums. Only Max issues are found.
Have you got any color corrections on that map?
If yes, it is normal to have that message and it is also normal to have incorrect results.
Can you attach stripped down version of the scene?
Your normal should be RAW and not sRGB.
Cheers.
No color corrections on the map.
What map type should it be? I usually use tangent space.
Yes just like Alvaro just mentioned.
Rgr that- I got it.
Little bit of a learning curve getting this set up right…but I love it.
You can make Maya to read normals as RAW only in the preferences.
There is color management settings but I haven?t used them before…looks like I?m going to need to now.
Gloss, IOR and Roughness they also need to be read as RAW. Good luck mate !
I?m having lighting issues…light colors are getting washed out…
You can define “rules” with the Maya Color management system, which can be pretty handy when bringing in textures for glossiness, normal maps etc. If those textures have a pattern in their filename, for example if all of you normal maps usually contain NRM in the filename (like sometexture_NRM.exr), you can set something like this as a rule: *NRM* and define that the default for such files should be Raw. I’m away from Maya at the moment so I can’t post screenshots, but it’s fairly straitforward.
As for the lighting issues - it’s going to be a bit hard to tell without a scene, but if you’re using textures for your lights - you can again check the color space settings in the file node and see if there’s a texture that is corrected as Raw, when it should be sRGB or it might be something else.
Hi all
Just checking, is it just the normal maps which require changing to RAW color space?
And is there a script or something similar for changing all normal maps to RAW?
Cheers
Read yolovs post. But yes they do need to be raw.
Any texture could need to be Raw or corrected, depending on where it comes from and what’s baked into it.
Usually, maps used for normal mapping, glossiness and similar should not be corrected (i.e. should be Raw).
Other maps such as diffuse might need correcting (again - depends on who made them in what application, in what format and with what coorections baked into them if any).
A script could be made, yes, but given that there are more than one possible workflows in setting up the shading networks, this means making a script that handles (a lot) more than one cases, making this a bit difficult.
I think it’s a lot easier to use Maya’s rules for color management. We did a short tutorial on this a while ago: Chaos Docs
Hi,
I’m using aces 1.2 and I color manage any textures using “values” as "Utility - Linear - sRGB ". Is there any way at all to stop that warning keeping on popping no matter what I do? Many times, I’m doing things like grooming and it keeps on coming over and over again and I find it quite annoying. Thank you.
Cheers,
Jacques.
If a texture for normal mapping or similar (incl. reflection glossiness, etc) that is normally encoded as linear sRGB - you’ll need to set its color space to ‘raw’.
V-Ray simply warns that you may get unexpected results, and you can keep rendering, but it’s best to make sure all the textures are corrected for the right color spaces.
Thank you Alex. That’s what I read in the doc but using ACES 1.2, anything that has a value needs to be “Linear sRBG” not “Raw”… And it works fine… It’s just that that warning which keep on showing up randomly in the bottom script editor bar is quite annoying. If there’s no way I can get rid of it, it’s ok, I’ll try to live with it.
Cheers,
Jacques
There should be a Raw (capital R) built-in color space and then a raw (lower-case r) OCIO color space. Try using one of these depending on your setup.
Thank you Alex but I tried that and you can clearly see the difference where the “RAW” doesn’t correct it right… So that’s not really an option.
Just out of curiosity… Why do you give that message for that specify “color space” and for the others… Say “aces2065-1” and “sRGB” for instance?
Cheers,
Jacques.
Hey @TKIO
Try searching for one that doesn’t say “utility” in the beginning. There should be an option in the list that says simply “raw” (lowercase r) in the list and that’s the one you need when using an OCIO configuration (I assume you are using OCIO, since all the Utility spaces show up in the list).
As for the warning - it’s to warn the user that there’s a texture used for normal mapping, that has unexpected color space corrections applied and the result may be incorrect. The whole purpose of the message is to bring your attention to the color space setting of such textures so you don’t get an undesired result. The message will not in any way prevent you from rendering.
Let me know if that helps.