ambient occlusion hidden??
Hi, is it true that the ambient occlusion node has been intentionally hidden from the UI?
In a misguided attempt to stop users from deploying procedural AO in a PBR workflow?
If so, this sort of paternalistic, condescending design intent makes me angry.
I know that I can expose AO using Python.
But I should not need to take extreme measures.
I know exactly what I am doing.
I need AO because reasons.
Trying to force users to do what you think they should do is the antithesis of the free, open source philosophy.
You can't anticipate every possible use of a feature. Thinking that you can dictate how users will creatively employ features is the height of arrogance.
2 Comments
You know what you are doing, and you know the free and open source philosophy.
So I hope you understand that you do have access to Blender, it's source code, its development communications, ... You could go straight to the facts instead of carrying on rumors.
And when devs take a decision you disapprove: that's fine, it happens. But if you want to make changes happen, constructive feedback and collaboration do better than appeal to motive and name-calling within a FOSS community.
false: shader editor -> add -> input -> ambient occlusion [fact checking might be one of the possible anger management approaches].