Bug: Nodes disappearing off screen.

Maybe I have used too many nodes or something but suddenly I'm not able to see my "last" 4 nodes.. I have tried zooming in and out, switching off and on thumbnail view, turning off the node viewer, restarting resolve, used "Clean up node graph" nothing works.


I'm on DR V15.0.0B.065

Mac Pro (late 2013)
Version 10.13.6
3,7 GHz
AMD FirePro D300

MacOS High Sierra

[Dwaine Maggart]

If you middle click while moving the mouse, it will drag the whole node group around the screen, which should allow you see the other nodes. Not sure why Cleanup isn't doing a better job.

Works now if I turned off dual display.. but nodes are still unreachable when I go back to dual display (middle mouse moving doesn't do the trick either.)

Okey so I found it to work in dual display if I remove the video viewer (toggle display mode) or resize the node panel to be as big as possible and then using Cleanup.

But if the node panel is normal sized (in dual display) the cleanup nor middle mouse move/hand tool will let me see the nodes right to the output..

Same problem here in DVR 15.

I appended a node to a larger node tree and the node was off screen and I could not get it back, nor delete it.

This is a bug that needs attention.

The "Zoom to Window" control helps a lot in these situations.

For a lot of reasons, I think Good Node Management involves using a fixed number of nodes throughout a project (particularly longform like features or episodic TV), each one pre-labeled as to function, and then you can just bypass the unused nodes and activate them only when needed. You can also keep the node tree large enough that everything is easily readable.

The problem with winding up with 25-30-35 nodes is they get to be very unwieldly a lot of the time. I tend to try to keep the node trees at no more than 20-22 nodes or so, but I'll add another half dozen or more as Post-Clip grades when necessary. (I concede there are complex projects like fashion commercials or car spots where you might well need a dozen tracking roto windows, a dozen external mattes, and a half dozen curves and keys to really slam the image.)

Often, I find there is a simpler way to do what you're trying to do with massive number of nodes. In cases where I've been teaching Resolve students, I've seen cases where they have 2 or 3 nodes early in the tree, and then we discover that much later on, there's a couple of nodes that completely undue that effect. In other words, when we delete all of those competing nodes, the picture effectively does not change. Keeping it simple can be very beneficial, not only creating a cleaner picture but also providing a better visual understanding of signal flow. Order of Node Operations is really crucial here.

I had the same issue, but with my first node disappearing to the left side of the window; only snapshotting the node tree, reseting the grade, and re-importing the saved tree did the trick.

However, this (late) reply is more of a general remark addressed to Mark Weilage: your comments are consistently the most useful notes I come across on this forum, for what it's worth. Thanks for all your time here.

I had the same issue, but with my first node disappearing to the left side of the window; only snapshotting the node tree, reseting the grade, and re-importing the saved tree did the trick.

We have a Fixed Node Tree tutorial coming up in the future over on Lowepost, and one thing we'll deal with is "how do you get a large number of nodes back on the screen."

One trick is to arrange them in a shape that matches that of your screen, and I use "Original Size" quite a bit, and then zoom the tree in to get a better look at it and read the labels. If you have the exact same Node Tree for every shot -- even if individual nodes are bypassed or unused -- it can work very reliably, even in a big project.