There Are tons of Bugs on Fusion page, Need optimization

There Are tons of Bugs on fusion page, Need optimization
I know there are many new features, which is feel like rushed on few features, but others some features are too good

But the fusion optimization is very, very bad on 20, they just too rushed to released 20 or rushed to get out of BETA

In fusion with @ image planer 3d, text masking is lagging on my machine, Frequent breakdown on fusion, The nodes are always caching even when I did not put the node tree on viewer

the caching is it's never ending on a same node tree

I installed v19 same node tree but with 4k clips and effect add on, Playing like butter did not have to use Playback resolution to quarter

But in 20 even I do playback resolution to quarter, disabling motion blur and High quality , it's just lagging, breaking down, frequently frame is not processing, viewer is not processing etc.

I will list down all bugs in here.

Please BMD Fix and adjust this optimization, the thing with Fusion

[Shrinivas Ramani]

Hi

Can you add a link to an example project file that plays/caches/shows different performance characteristics in v20 compared to v19?

Even a minimal project with a single Fusion composition will do. In your response, please also include some detail on your set up and observations (e.g. using fps counts or seconds etc) so we can try to reproduce your observations with a similarly spec'd set up.

Thank you
Shrinivas

@Shrinivas Ramani
Thank you for noticing, Sir.

The problem I’m facing is that after the version 20 update, the Fusion integration issue still persists. Features like Color and Fairlight are well integrated and communicate smoothly with the software — but Fusion is still poorly optimized.

I suspect it may be due to Fusion still using older code structure, unlike the other pages which are built on newer frameworks.

Here are some screenshots for reference:
Even when I’m viewing only a single media node, the entire node tree is processing. I’m not sure why that’s happening. For example, when I use just a Fast Noise node connected to the Viewer, I still see the whole node tree being processed, which shouldn't be the case. I'm getting only 6–7 FPS, even though a Fast Noise node is usually extremely light to process.

Screenshot (65).png (24.03 KiB) Viewed 501 times

As you mentioned, I’m attaching the project file for review.
https://drive.google.com/drive/folders/1z_LrCKiDlOiEtrozAtlVQYQMdCjXbbol?usp=sharing

Nothing fancy — I’ve just used a bunch of Merge nodes, Transforms, Images, Text+ with sliders, Image Planes, and a Camera3D.
I’ve been building node trees like this since Resolve 16 and never encountered this kind of issue before.

Please, Sir, consider improving Fusion’s integration so it communicates better with the rest of the software.
Even on a Mac Studio with over 100 GB RAM, it’s still lagging.

That said, DaVinci Resolve is still the only software I enjoy opening, even when I have nothing to work on.
It’s just such a pleasing experience to use a tool like this.

Thank you again!

[Shrinivas Ramani]

From engineering:

Taking a look at the comp, I see 19fps playback on my Mac Studio. I can improve performance by simply changing the renderer node. Try the following:
Renderer3D > Renderer Type > Hardware Renderer

This one change gives me 24fps playback

[daniel.koch]

Even when I’m viewing only a single media node, the entire node tree is processing. I’m not sure why that’s happening.

This sounds like you've turned off Selective Updates, perhaps accidentally. Changing that from Some to All will cause Fusion to process the entire node tree, instead of only what's required for viewing or saving.

In Fusion Studio this can be changed for the current comp with the Some/None/All button below the viewer, to the right of APrx, and also in Prefs/General as "Update All/Selective/No Update". In Resolve's Fusion page, it's only in Fusion Settings/General, and applies to newly-created comps.

Other general advice to help with caching is to try giving Fusion more system memory in Resolve's Preferences/Memory and GPU, and ensure that the Graphics Memory amount in Fusion Settings/Tweaks is not set too low (Auto is recommended).

Hey

Sorry to pop up here but as I also experienced his issue, this is very interesting actually...
Honestly, I'm on Fusion Studio 90% of the time but I recently when to the fusion tab for some jobs, and I also wondered why I saw all the branch processing (leading as you both know to a fps fall).

In Fusion Studio this can be changed for the current comp with the Some/None/All button below the viewer, to the right of APrx, and also in Prefs/General as "Update All/Selective/No Update".

Yep, that's what I do, I'm always on Some and only go to All once out of 25 times, when I check image/image, the effect I just made.

In Resolve's Fusion page, it's only in Fusion Settings/General, and applies to newly-created comps.

This I didn't know, thank you because it will have me go there and check not only this option but also all the rest, as I've done in Studio a long time ago...

Hello @Shrinivas Ramani & @daniel.koch
Thank you so much for your resolution.
It did kind of help me on the previous matter, THANK YOU VERY MUCH ALL.

But right now I am working on a project containing a PSD file, and I am enjoying the new layer selector in FUSION. But the problem is I'm getting 3 to 4 FPS.

So I am using 7 MediaIn, all are individual PSD with different layers selected with DVE node—not just simple X and Y keyframes, very simple—but the playback is 3 to 4 FPS.

Screenshot 2025-06-27 191436.png (180.27 KiB) Viewed 305 times

Screenshot 2025-06-27 191453.png (22.25 KiB) Viewed 305 times

So Is this happening because of Using 7 individual Same PSD file as a MediaIn ?? Or Should I use Old method to import PSD to Expand layer a file.