Fusion version:
17 & 17.1.1

OS and version:
Win 10

Additional relevant system info:

Description of the bug:
On 3D Tools one could use the 'Pick' button to position one object on the surface of another object.
This is not working in Fu17 at all.

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

Steps to reproduce:
Add and merge two Shape3D.
Open Transform Tab on one of the shapes.
Click and hold any Pick button, try to pick in the viewport.
Nothing happens....

Fusion version:
9, 16, 17 (and most likely earlier as well)

OS and version:
Win10

Additional relevant system info:

Description of the bug:
As the manual says:
Frame layout allows you to define a rectangular frame used to align the text. The
alignment controls are used to justifying the text vertically and horizontally within the
boundaries of the frame.
The boundaries of the frame are not respected at all.

I think this has been broken for a long time.....

Severity (Trivial,...

Fusion version:
16, 17

OS and version:
Win10

Additional relevant system info:

Description of the bug:
With the ColorCurves set to UseGPU Fusion crashes.
Works fine when set to disable.

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

Steps to reproduce:
Add a BG, add a cCv.
View cCv....bang!
If it doesn't crash on viewing,add a point on the LUT curves....bang!

Please, if possible, provide a Fusion setup to help demonstrate the behaviour, either as an attachment or between...

Fusion version:
16, 17

OS and version:
Win10

Additional relevant system info:

Description of the bug:
Add a CoordinateTransform modifier to the Transform Controls of a 3D Tool.
Fusion stalls and comes back after many (many!) seconds with the modifier added.
Go to the modifier tab, add a target object.
Again, Fusion stalls for a few seconds (sometimes hangs).
If you eventually managed to set the CoordinateTransform up, it will not evaluate the position at all.

Severity (Trivial,...

Fusion version:
17

OS and version:
Win10

Additional relevant system info:

Description of the bug:
Working with dblPolylines on Float tools creates Alpha values largen than one in some areas

Severity (Trivial, Minor, Major, Critical)
Minor, but annoying

Steps to reproduce:
Add a BG, set to float, add Polyline to BG, make double, offset the outer polyline, zoom in to the border.
In the attached comp I used a CustomTool to flag all Pixels with an Alpha largen than 1.

Please,...

Fusion version:
17

OS and version:
Win10

Additional relevant system info:

Description of the bug:
The 3Bol does not output Position and Normal values.

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

Steps to reproduce:
Add a Shape3D, a ReplaceMaterial3D, and a ChannelBoolean3D.
In the 3Bol set R/G/B to X/Y/Z-Position.
Output is nul.
ReplaceMaterial_WPP.comp
Please, if possible, provide a Fusion setup to help demonstrate the behaviour, either as an attachment or between...

Fusion version:
17+
(most likely previous versions too but I don't have 9 installed right now)

OS and version:

Windows 10

Description of the bug:

Using a matte object in Fusions 3D system will introduce errors in the data channels on that matte object in the Software renderer.
Using OpenGL will not render any data channels.

Severity (Trivial, Minor, Major, Critical)
Major

Please, if possible, provide a Fusion setup to help demonstrate the behaviour, either as an...

Fusion version:

17.0 build 43

OS and version:

Windows 10 (2004)

Additional relevant system info:

Quadro P4000 or Geforce 1080 Ti (I've tried 461.40 and 461.72)

Description of the bug:

Some nodes do not work or crash Fusion with GPU mode. Or Could not create GPU Session Error in console.
ClolorCurve,VectorMotionBlur,HotSpot,Ray,ErodeDeliate,FileLUT,LutCubeCreator,LumaKeyer,Transform,LetterBox,Resize,Scale

FileLUT, LutCubeCreator, Ray do not work as they should. They will show...

Fusion version: Fusion Studio 9.02 - 17.1. I haven't tested Resolve, but if it's in every Fusion version it probably happens there, too.

OS and version: Windows 10 Pro

Additional relevant system info:

Description of the bug: The modulus operator in a CustomTool's Channels expressions sometimes returns values that should not be possible. In a CT with the expression (x*w)%2 , the result should be stripes with the value 0.0 and 1.0 alternating for each pixel. However, it returns a...