'Always run Fusion on CPU' disappeared

I am not sure how, but after updating to Resolve 15.1, I can't seem to find the option to 'Always run Fusion on CPU'. This is causing me issues as Fusion still doesn't run well on GPU. I get crashes whenever I try connecting a Background node or a ChannelBooleans to the MediaOut. The only way to fix this was to use the CPU option, but now it is gone.

Here is a screenshot of the Preferences.

Screenshot from 2018-09-19 19-32-34.png (27.36 KiB) Viewed 7073 times

Noticed this as well, and I also checked through all of the Fusion preferences accessible from the menu bar. Couldn’t find it or the tradition Fusion OpenCL options. It also seemed that the Fusion preferences weren’t being respected either, I would save them saying I want nodes to arrange to connected, but any comps generated would that feature disabled by default. Not sure what was going wrong there.

Cheers,
Mike

Noticed this as well, and I also checked through all of the Fusion preferences accessible from the menu bar. Couldn’t find it or the tradition Fusion OpenCL options. It also seemed that the Fusion preferences weren’t being respected either, I would save them saying I want nodes to arrange to connected, but any comps generated would that feature disabled by default. Not sure what was going wrong there.

Cheers,
Mike

I have noticed the Fusion settings issue as well. The settings are only respected if you go to the Fusion page in the traditional way (having media on the timeline and switching to Fusion). However, if you create a new composition using the generators or in the media pool, it ignores the Fusion settings.

During the beta cycle, I had 'Always run Fusion on CPU' checked due to crashes. I didn't use Fusion since playing with it during beta.

Now as I dabble with it today on 15.2, I see that Fusion is entirely CPU-bound and my GPU isn't being used. I suspect it's because it's still honoring this option which I set months ago and which I no longer have the ability to toggle.

Looking on my laptop which runs 15.0, I see the setting in the config.dat file which holds the preferences is Local.Fusion.CPUMode, which is set to 1 when "Always run Fusion on CPU" is enabled and 0 otherwise. This setting was absent from my 15.2 installation.

As an experiment, I tried adding Local.Fusion.CPUMode = 0 to config.dat but this didn't affect the behaviour. When I update global settings, the property is removed when the file is updated. So not only has the setting vanished, so has the functionality.

Is it possible GPU rendering for Fusion has been completely removed from Resolve after 15.0?

Edit: more likely my own understanding is flawed and I just need to RTFM. I see the Renderer3D object has a Renderer Type and I can choose OpenGL, at which time I see some activity on the GPU. (That said, the OpenGL renderer has some issues, which is perhaps why it defaults to Software renderer.)

Edit: more likely my own understanding is flawed and I just need to RTFM. I see the Renderer3D object has a Renderer Type and I can choose OpenGL, at which time I see some activity on the GPU. (That said, the OpenGL renderer has some issues, which is perhaps why it defaults to Software renderer.)

OpenGL and general purpose compute on GPU are different beasts, OpenGL is way easier go support and get working so I wouldn't make any connection between OpenGL and OpenCL/CUDA/Metal.

So, to sum it up... the setting has vanished and no one knows why... correct?

I am having major issues with black frames in my cached fusion comps and it's causing some major issues to say the least. Not a real confidence builder when the client has to point out black frames in the renders.

- Paul

Hi all,

I joined this forum just for this single issue. Has anybody solved this yet? Or is there another way now to set Fusion to run on "CPU only"?

Now, that I recently updated to 15.3, Fusion is causing all kinds of crashes (and I can't find a way to make it NOT use the GPU)... mostly, when I use any kind of Gaussian (like in the "Blur" value in the Luma Keyer) or when using a "Background" node.

Any help would be much appreciated.
Thanks in advance.

Hi all,

just wondering if there has been an answer to why this feature has gone?
When trying to add a simple effect like a blur to a clip in fusion, when I drop the effect on the line it sits a s a blank square for ages, doing nothing, the only way I can get it to work is add something like a defocus, then remove the defocus and re add the blur. I just cant work out why?
Does someone have optimal preferences for windows based computer running 2x GTX1080 cards for resolve and fusion?

Bumping this up too. Was stoked to find disabling the GPU solved all my issues, but such a pain disabling it on nearly every node.

I'm using Resolve 16. And I had an issue where I tracked an item in my footage using the 'Planner Tracker'. It successfully tracked. and I even created a 'Tracker Transform' node. But when I add the node into my workflow, Davinci would stop responding and slowing stop responding.

So looking at research, disabling the GPU in Fusion would be the best option since alot of people were getting this as a solution.... but 'Davinci resolve 16' has removed that option under settings.

So I found in the Node Inspector of the 'Tracker Transform' node, in the 'Settings' tab. There is an option to 'Disable GPU'.

THIS WORKED!!!!

Most of the nodes have this option. Check that... I can understand why Blackmagic did this because now, all my other Nodes still use my GPU(Which runs smoother under GPU), but then only that one Node causing problems run on the CPU. !!!!

Screenshot 2020-02-21 at 15.39.06.png (425.19 KiB) Viewed 4385 times

This is a terrible solution. I spent the last 36h trying to export a 10 minute video with some fusion stuff, constantly crashing Resolve without any note what the issue is. If I went into the Fusion tab of the individual clips I didn't see any error message in the CLI window.

Basically picking this thing appart, the result of 4 weeks of work, I found that it was a simple planar tracker 2 second long animation by pure trial and error.

The switch would have allowed me to just not care about longer render times and force this thing through, now expecting me to go through individual nodes!! to toggle a switch, have you guys ever seen the average Fusion comp? Mine have like 200 nodes each.