[BUG] 2.43 Windows - Missing Node line cut

Tue Feb 08, 2011 5:47 pm

Before I begin reporting on this, I did a search to see if this came up any were which it did not. So I wanted to make sure that it was reported as a bug since I think its more then just a missing feature and more a necessity for a node editor.

You can not cut a line once it been made with out destroying the node to which that line connects.

Tue Feb 08, 2011 6:48 pm

I find this behavior very annoying, since ever, but apparently it's not easy to implement a solution that would persist data in a more user-friendly fashion.

In some cases this behavior makes you reload the whole scene - like when you map roughness on glossy shader, then change your mind and disconnect your map, but you can't use a floattexture to replace it because it wont let you input values lower than 0.001

Tue Feb 08, 2011 7:14 pm

I dont think it would be that bad if the IDE have to reload the whole material ball. Now for another complex scene mesh that maybe a different story but even then it would be so much faster to be able to work in the node editor the way you should be able to as most people experiment on the material ball anyways.

matej wrote:I find this behavior very annoying, since ever, but apparently it's not easy to implement a solution that would persist data in a more user-friendly fashion.

In some cases this behavior makes you reload the whole scene - like when you map roughness on glossy shader, then change your mind and disconnect your map, but you can't use a floattexture to replace it because it wont let you input values lower than 0.001