Fusion version: 16.2.3 (and before)

OS and version: Windows 10 64 bit

Additional relevant system info: 3900x, 64GB RAM, RTX2070 8GB

Description of the bug:

The Custom Tool seems to be performing very badly in certain circumstances when compared to Fusion 9 Studio. I noticed at least a 5-fold degradation with the comp below (30fps on Fusion 9, between 5 and 6fps on Fusion 16.2.3, but had noticed worse on previous 16 versions). This is with the same setup (HQ versus non-HQ, GPU...

This is sort of an unusual bug report, because I hope that I can bring more people to actually report bugs and issues to Blackmagicdesign and need your help in this particular case. There is a comp file in the next post that should show you the issue when rendering.

Fusion version:
16 to 16.2

OS and version:

Windows 10 latest updates

Additional relevant system info:
RTX 2060 super

Description of the bug:

Fusion fills up the RAM and VRAM with previous frames until it's full and...

Fusion version:

16.1.1 build 5.

OS and version:

Windows 10 - version 1809.

Additional relevant system info:

x2 RTX 2080ti - Nvidia Drivers 441.28 (same issue with 430.86).

Description of the bug:

If the Vector Motion Blur node have Use GPU enabled a line appears at the bottom of the frame. This happen with render AOVs or synthetic vectors as Bryan Ray described in the BMD Forum.

If Use GPU is disabled the line disappear but the calculation takes more time obviously....

Fusion version:
16.2
OS and version:
MacOS Mojave
Description of the bug:
Scirpts such as Archive Composition don't work.

I had to go back to F16.1
:( :(

Fusion version: 9.0.2, 16.2

OS and version: Windows 10 Pro

Additional relevant system info:

Description of the bug: An expression on the Angle of View input of a Camera3D does not evaluate during rendering. It works as expected in an interactive mode, but as soon as a Render begins, the input is locked to its most recent value.

Workaround: Bake the input using the Bake Animation script from the Eyeon Legacy script package.

Severity (Trivial, Minor, Major, Critical) Minor...

Fusion version: 16.1, 16.2

OS and version: Windows 10 Pro

Additional relevant system info:
- Clevo laptop
- Intel Core i7-7820HK
- 64 GB RAM
- NVIDIA GTX 1070
- Windows 10 Pro 1909
- NVIDIA driver 442.19 (I also tested older NVIDIA drivers, always resulting in crashes under the same circumstances)

Description of the bug:
Fusion 16.2 crashes when using Lenscare OFX plugin when GPU is selected in:
Preferences --> Global and Default Settings --> GPU --> Device: Auto / GPU

With the...

Fusion version:

16.2.1 build 6 (happen in older versions too).

OS and version:

Windows 10 version 1809

Additional relevant system info:

CPU: Intel 7.700-K / GPU: x2 NVIDIA RTX 2080-Ti / 64GB RAM.

Description of the bug:

In the new Fusion 16.2.1 (and older versions too) the OCIO Color Space viewer LUT have some issues displaying ACES CCT OCIO transformation. If you set ACES CCT as source space and Output - sRGB as output space, some blue and red bands appears on middle greys, but...

Fusion version:
Fusion 16 (and 9.02)

OS and version:
Windows 10

Additional relevant system info:
i5 3rd generation, 16GB RAM and Geforce GTX 1060 6GB

Description of the bug:
It appears that (procedural) animation of published points on a polyline is ignored on final renders.

I created a polyline to make a procedural 'spotlightcone'.
To do this I made a triangular shaped polyline mask, published one inner point, one outer point and modified those with vector results that are...

Fusion version:

16.2

OS and version:

Windows 10

Additional relevant system info:

Two monitors

Description of the bug:

The Create floating views option in Preferences -> Layout incorrectly saves Floating Frames as Floating Views.

Severity (Trivial, Minor, Major, Critical)

Minor

Steps to reproduce:

Create a Floating Frame and customize it to your liking.

Go to Prefs -> Layout. Hit Grab Program Layout and make sure Creating floating views is checked.

Restart Fusion....