Blender 2.8 Design Flaw: The Texture Node Editor

I admire and support the progress that Blender is constantly making, and I understand that things like the GSoC exist to permit to other people to fix things that the devs cannot due to time, but honestly I’m a little bit puzzled that fixing/replacing the Texture Node Editor is not a high priority task: we’re literally dragging this from 2 years now, it feels so weird to me that we have an entire editor in Blender that doesn’t work, or anyway works in a very limited and almost no-user-case scenario. For example, using the Displace modifier only with the textures inside the properties editor (that permit very tiny modifications) it’s something that limits so much the possibilities of proceduralism.
Fixing the editor was part of the proposals for the GSoC '20, but it didn’t make it because as far as I know nobody took the project: do we really need to wait until someone external to the developer will come with the will of fixing it?

5 Likes