Blackmagic Forum

Basically whenever I go to the Fusion page and add a CC node or a transform, Resolve becomes unresponsive, and I have to restart it.

Also, if I try animating something, or changing some of the parameters in any node, most of the time the viewers don't update, and I have to restart Resolve to see the result of the changes I made.

In fact, a lot of the time the viewers don't even update when I change the node that is viewed in them. When I switch to the Fusion page, the MediaOut node is viewed properly, but if I try viewing any other nodes, the viewer doesn't update.

This is tested on a Windows 10 laptop. To be fair, it is not my production machine, but I don't want to install Resolve 15 on my production machine yet. The laptop is a Surface Book with an i7-6600 CPU, 16GB of RAM, and an NVIDIA GeForce GM108 with 1GB VRAM.

The logs are here:

https://we.tl/3P1bUjY1vF

1 GB of VRAM is not enough. Please check the configuration guide.

Uli Plank wrote:1 GB of VRAM is not enough. Please check the configuration guide.

Hi Uli. I know that. I have already checked the configuration guide. But would it really stop me from even adding nodes in the Fusion page.. I am not talking about anything complex. Even dragging the Transform node to the Flow makes Resolve unresponsive.

Actually, no need to answer, Uli. I decided to test Resolve 15 on my production machine, using Windows 7 (which is not my main OS).

I, initially, didn't want to do that because I know Windows 7 is not supported, but I when for it as just a test for the hardware, and it actually works really well.

Almost all the performance issues I had were fixed by simply having a better hardware configuration. Can't wait for the final release to be able to use on an officially supported OS

The GPU looks like it might be 11GB, I’e ok.

Peter Chamberlain wrote:The GPU looks like it might be 11GB, I’e ok.

Hi Peter. On the Windows 7 machine, the GPU is 11GB, and it works fine. The laptop has only 1GB. This is the one that wasn't working properly despite having Windows 10.

Ah, thanks.. i didnt see that.