Sat Dec 09, 2017 2:52 pm
Thanks guys. Let me clarify a few things and add some extra information.
My system:
Intel Xeon E5-1650 (6-core) 3.2 GHz
64 GB RAM
Nvidia Quadro 2000 1GB
Windows 10 Pro 1709
I've spent half a day trying all possible solutions from every forum (incl. WeSuckLess) and nothing worked. This is everything I did:
- I've pasted the code provided by Bryan in order to disable OpenCL from within Fusion: applying this to the console as .lua file. The only thing that has changed was the fact that Fusion stopped crashing instantly, instead it was hanging for a while and I was getting Windows prompt that the program needs to be closed.
- I couldn't disable OpenCL in CC node's Common Controls because I couldn't see any option like this there, as indicated by another user as well.
- I've changed OpenCL settings in preferences file many times, I also deleted/hid prefs as advised elsewhere; no results.
I then followed an advice from another user in different thread (there needs to be better flow of information about critical issues like this between threads on this forum...) and re-installed graphics drivers. Since I have Nvidia Quadro 2000, I couldn't follow his advice and install "Quadro New Feature" driver 388.16 refering to "Fall Creators Update" cause it's not supported by my graphics card. I then decided to "downgrade" from my current 377.61 ODE driver to the newest "Quadro New Feature" driver for Nvidia 2000, which was version 372.95 (without any mention about "Fall Creator Update" since it was released 2016.9.27, but that was still the newest QNF driver for my card). Nothing.
I went as far as installing Intel's app to check all drivers related to processor and I have also installed the newest OpenCL drivers manually. Nothing.
After the whole evening and night of trying to find a fix, I went back to Fusion 8 instead.
Today, I decided to try make it work one more time and I pasted different piece of code into console, provided by user Andrea De Paolis. Guess what... IT WORKED! I mean, so far it's working: I can use the "problematic" nodes and even access OpenCL in Fusion's preferences...
I don't know why this particular solution worked and the others didn't, but I hope this is going to help someone.
Btw, the only advice I decided not to follow was to downgrade/re-install my Windows to any of the previous versions. First of all, I honestly don't have time for this, secondly, it's a headache to go back to any of previous Win versions and I cannot spend another half a day to dig into this one, thirdly, all the other apps (like Adobe stuff, DaVinci, Blender, Houdini etc.) works perfectly fine on this version. I know there are issues related to "Fall's Creator Update" and I believe this update is responsible for the death of my (quite old) laptop quite recently, but on my desktop everything works so far...
Anyway, this is a serious bug and if BM wants users to switch from Nuke or AE, then they really need to take care of critical problems like this a bit faster... I've noticed reports of this error in previous months. I hope this will be fixed because I'm a big fan of Fusion, I want to support it and spread the word about the software to my fellow VFX/film peers...
Thank you for everyone who contributed to this thread!
Btw, the code that helped me (author: Andrea De Paolis) that needs to be saved as .lua file (by going into Script > Edit > New Script, opening notepad/similar, pasting, saving) and dragged into console:
for _,id in ipairs({"ColorCorrector", "GamutConvert"}) do
local n = 0
for _,t in pairs(comp:GetToolList(false, id)) do
t.UseOpenCL[0] = 0
n = n + 1
end
print("Disabled OpenCL on "..n.." x "..id)
end
comp:SetPrefs("Comp.Tweaks.OpenCL.Enable", 0)
fu:SetPrefs("Comp.Tweaks.OpenCL.Enable", 0)
fu:SetPrefs("Global.Tweaks.OpenCL.Device", "cpu")
fu:SavePrefs()