Fri Dec 07, 2018 11:30 am
To my knowledge it´s a bug that is already known and will hopefully be fixed in one of the next updates. Someone here gave a nice little workaround. On the editpage you can place a transparent graphic ontop of the fusion comp, like a PNG with no visible elements in it. This forces Resolve to cache that area and with it also the fusioncomp. I've tested it and it works. Of course this is annoying but should help you at least for the time being.