-
Just a cat helping with the development of Blender.
Thank you Blender developers for doing everything you do.
- Joined on
2018-10-10 -
-
The CoatIOR in closure color CoatBSDF = dielectric_bsdf(CoatNormal, vector(0.0), color(1.0), color(0.0), coat_r2, coat_r2, CoatIOR, "ggx"); also needs to be set to max(CoatIOR, 1.0) to avoid issues when CoatIOR is below 1.0.
There's still a mismatch between Cycles SVM, Cycles OSL, and EEVEE.
When the coat IOR is below or at 1.0, all three behave differently.
- Cycles SVM behaves like IOR is 1.0 and there are no…
What is your IOR? If it isn't 1.0, then reflections will appear. This is caused by a recent change to the Principled BSDF made by @LukasStockner .
This may seem like a weird change, but from my…
Remove the full stop from the end of "Typically should be zero or one for physically-based materials.". The Blender UI already adds a full stop to the end.
I also noticed a weird behavior with certain coat colours and device configurations.
If the coat tint has a blue channel set to 0, and you're rendering with the CPU, then the coat will appear…
I would like to pin @JulianEisel again to look into this issue or the pull request that has been made to fix this issue.
This results in Blender crashing on the Metal backend for Blender/EEVEE. You can find the error message below.
Running a quick test, I can identify a few issues.
- Blender crashes when using EEVEE with this pull request on the Metal backend for Blender (Tested with a M1 Pro). I haven't done much…
Replacing if (coat_tint != one_float3()) with if (!isequal(coat_tint, one_float3())) fixes compilation issues with the Metal backend.
This is probably unintentional so that's why I'm reporting it.
Changing the Coat Tint colour while the coat parameter is set to 0 still has an impact on the material.
![Clear coat…
and also still have to address the HDR monitor availability idea from Brecht, but hopefully that should be the last of it for the initial implementation.
Just confirming, this patch is for…
I just wanted to add a comment.
As pointed out earlier, the rendering error occurring on the GPU but not the CPU was due to floating point precision differences between the dot() function on…