A Paint node breaks the ability to cache an entire comp

Any one else see this? As soon as you put a point node or a mask paint node, the comp will no longer properly cache. The green ball will no longer fill up so the frames will play at the correct framerate.

This has been a problem for a really long time but I would love to upgrade a version at some point and see this issue fixed. I avoid paint nodes like the plague for this exact reason but in a compositing app it's not great to not be able to rely on using paint.

Obviously I know you can split out a render and all the workarounds, but I'm not talking about any of that. I'm just talking about a simple paint node not breaking the ability of an entire comp to cache properly.

Yes. Been an issue for years, have no idea how to reproduce it other than "use Paint for a while".

I have the issue as well. On every machine that I ever used fusion on.

But it’s so difficult to make it reproduce in a simple comp for the support.
I’ve tried but failed to properly communicate it several times…

One workaround (besides saving to disk) is to view it, then sometimes it caches to RAM, and then view another node downstream. But if fusion decides to clear the RAM cache on the paint node then you’re back to choppy performance until you do it again.


This issue and the new multi merge requesting all branches even if the blend is set to 0 are really big performance hits. The Paint node is obviously a bug while the MultiMerge seems to be an oversight though

Paint node suddenly stops working correctly. It's a longstanding problem, but I don't know how it started. I try not to use paint node.

Resolve and Fusion Studio 19.0.1

Still an issue....

Maybe its time to retire paint and build a new paint2.0 from scratch with new more advanced tools?
Paint is outdated imho.

Maybe its time to retire paint

That doesn't really address the problem, though. There's a QA issue in Resolve and Fusion that affects everything, not just one particular tool.

I wonder if problem is related to domain of definition and optimization. Last week I was making a macro with a sliding panel for the edit page. And when transform node moves the panel off screen DOD was still being used, making 4K video run like, literally 10K video, because domain was so large. I was getting crashes and GPU run out of memory messages, constantly.

After I went node per node and optimized the DOD to only render what it needs, the whole thing now runs so smooth one could run it on an old calculator.

Paint node can have DOD issues that can be optimized, depending on how you use it. Especially if used with a lot of strokes and in serial node fashion instead of parallel node tree. I wonder if the whole thing is simply a matter of optimization, specifically of DOD.

Doubt it, as Paint resets the DoD to the Image Size.

Doubt it, as Paint resets the DoD to the Image Size.

Regardless of the stroke. Most of it could be wasted if painting on transparent separate layer. And if you transform the layer you could end up with all sorts of non needed rendering. Its worth doing the trouble shoot to optimize the comp.