Will Blender 4.1 read uint8_t normalize correctly? Because the memory space that used to be for uint8_t normalize in 4.0 is now used for uint8_t type.
If turning a checkbox on or off in the user preference could be considered "mind messing" then the rest of Blender would equal literal rocket science.
If it's possible to have versioning code for 4.0 by next week Wednesday, that would be great so we can add it in time for 4.0.0.
I'm very busy right now but I'll try my best. For the…
If such problems come up during collaboration it should be company policy making decisions to resolve the problem, not personal preference.
So yes.
In that case just turning "Add Auto Fake User" off would solve the issue.
@brecht Looks like the artists on https://devtalk.blender.org/t/merging-the-musgrave-texture-and-noise-texture-nodes/30646 are happy now after resolving some communication mistakes.
There are…
The problem of such kind of a solutions is that they fit personal use only.
Why do you think it wouldn't work for collaboration conditions?
I think there is a distinction between a node meant for height fields, centered around 0 without bounds. And a node for textures that produces normalized values in the 0..1 range. It might be a…
For me it's not just forward compatibility, I'm still not convinced that all these modes belong in a single node from a user point of view. I just don't see a compelling reason for it, and no…
It really seems like forward compatibility is the main problem here. In that case I can add code to convert the Noise Texture back into the Musgrave Texture for the 3.6 and 4.0 versions.