Blackmagic Forum

Here's the follow up to a comment on a feature request.
https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=211439

Shrinivas Ramani wrote:Hi Ben

DaVinci Resolve should not differ from Fusion Studio in node handling. Can you add a comp example and point out the difference in behavior?

Thanks
Shrinivas

Complete Example Project
https://drive.google.com/open?id=1XAplI ... drive_copy

Enclosed is the complete project. There's a Fusion Comp and a Resolve Project File that shows the Wireless Nodes functioning and not functioning in the Resolve timeline.
All the assets are the first 24 frames of the full sequence. It's enough to show the problem.

I first encountered it a couple of days ago.
I'm pretty sure it was 11/10/2024 from ResolveDebug_5.txt?

Initially I had thrown together the flow in Fusion Studio. Everything behaved correctly and this is a pretty standard comp for using 3DS Max_Vray generated EXRs. Once I knew that things were where I wanted them, I copy and pasted over the flow into a Fusion Composition on a Timeline in Resolve.



It worked inside the Fusion Page as expected but on the Timeline it was not there. I did the usual things:
Check that the track was enabled.
Check that the Fu Comp was enabled.
Check the Opacity of the Comp on the timeline.
Delete Caches.
Turn off Caches.
Duplicate the Fusion Comp to see if there was something weird going on.
When both the original and duplicated Fusion comps were showing transparent I restarted Resolve, then the machine.

Then I went into the new FU comp and trouble shot:
Checked that the MediaOut was connected and enabled.
Checked that the Index was set to 0.
Deleted and made a new MediaOut.
Simplified the connection to the MediaOut down to one Loader.

The picture showed!

Then started to add back in flows starting with the background plate. When I reached my first WirelessPlus node it became transparent on the main timeline again.


The node I was using is a modified Wireless node that has relinking capabilities. I though it was pretty basic but when I removed that node and replaced it with a traditional wireless node instanced to various locations, the flow worked and became visible on the timeline.



Inside the Timeline comps are both types of Wireless Nodes to compare.


Second Issue - Caching
Inside these comps are an excellent example of Caches not functioning and having to resort to a Saver/Loader cache system. The Velocity Blur before Merge1 will not respect the Cache on Merge1. It will continually regenerate no matter what. Please consider making a cache node to get around these issues. It's been an issue since Fu9 and has never been addressed.

Third Issue - VDB Loading
Also there is something wonky with the initial load of VDBs into a flow. It will throw an error that the file isn't found on intial look in one of the viewers.

Fourth Issue - Cached Cryptomattes throw an erro when tring to save.
I'll make a completely different post about this one but if you cache a Cryptomatte, and use a Saver to export an EXR sequence, it throws the error:
OpenEXR: Cannot assign a value of type "double" to image attribute "screenWindowWidth" of type "float".

This did not happen in 18.6.x, but does in 19.0.3. I hadn't needed to export mattes for a bit so I don't know how far back it goes. I'll also let the guys at Steakunderwater know about this one.

Thanks for making it this far!

Thanks for the detailed report.

The cache issue should be fixed in 19.1.1.