Still happening in 5.2.
Hi @rrousselot , this is going to sound a little crazy, but when this happens does pressing and releasing the left control key on your keyboard fix the problem?
Something similar to this happened to me with 5.1 when I was working on a webinar, and doing exactly that… Pressing and releasing the left control key fixed it each time. It might not be the same problem though.
I have not tried that but will when it happens again. I usually just find a node that is not exhibiting the behavior and move it slightly and it somehow resets the poorly acting node.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.