I think the reasoning behind it is too complicated for comments to describe. The PR description is already rather complicated despite only containing hand waving explanations, so I'd rather leave…
And also assuming it would simplify the code significantly. But it seems that was only for the fbm mode and the Noise Texture is now getting an additional enum and 2 input sockets for…
@JacquesLucke You sure that I should rename all new variables? (It's quite a lot)
Yeah, I know but a lot of other versioning code also uses Camel case. Should I change all variable names to snake case?
Thought about that, but kept it like this to make the logic consistent with versioning_replace_musgrave_texture_node. But will change if you want that.
You mean I should rename sockRoughness to roughness_socket? Why just this specific socket? It makes the naming inconsistent with the rest of the code.
@mont29 What I propose isn't supposed to be final solution to the Fake User problems but rather a temporary fix until a new data management system replaces the current one.
You rarely hear…
@Nika-Kutsniashvili Having an individually toggle for data-types makes sense. In that case I'd make an individual option for all the different data-types mentioned in my PR except for Freestyle…
A few design questions remain:
- Should it be enabled by default?
- It's categorized under the Node editor category because that's what most users think of when speaking about Fake User.…