Closed XyozaxeR closed 2 months ago
The color space of normal maps is set to Non-Color already. The issue is probably that you seem to have custom color profiles in Blender, and the "Non-Color" color space is renamed to "Non-Colour Data" so the addon cannot find the proper color space.
I don't think it's worth it to add kind of fixes for these on my side unfortunately. I'm not sure how exactly the custom profiles work in Blender, but I would suggest you use ones that do not rename the default profiles, or if it's possible, add a color space with the name "Non-Color" for compatibility.
Well, I'll try to fix it myself but if you will fix it the custom color space name is "Filmic Blender"
In case someone has the same issue with filmic blender or other color spaces heres the solution
You should edit the config.ocio in {version}/datafiles/colormanagement and duplicate the colorspace that represents non-color data and name it "Non-Color" ( I additionally copied it once more and named "Raw" but I dont think that is exactly necessary )
Import the map/model/material in a version of blender without having the color profiles installed ( because for me for some reason it only changed the color profile of detail textures if I did that on the version of blender with edited color profiles installed )
Copy and paste the whole map collection from version without custom color profiles to version with edited color profiles
By default color space of normal maps is the same as any other texture, but normal maps store data and not color and custom color profiles will break normal maps like on this screenshot
sRGB OETIF (Custom sRGB profile)
To fix this issuse color space must be "Non-Colour Data".
Non-Colour Data
Please make default color space (ONLY FOR NORMAL MAPS) "Non-Colour Data" because changing color space of every normal map is very tideous when there's thousands of materials and overall this is just how normal maps work.