Fusion 16 Studio Public Beta Bug List

Just making a thread where we can put bug reports for the F16 beta. Each post will be it's own individual bug report. I'm also mirroring my reports to the WSL Bug Tracker[0] and a Trello board[1] I set up so I can see what changes from beta to beta. Just making some extra places so BMD can't miss it

A note on the Trello board: Any Trello user can comment/react to the cards, and if you want to contribute new cards you can join with this link[2]. But please make sure you report your bug first on these forums or on WSL first. The Trello board is really just a summary and overall view of the beta's bug crunching progress.

Cheers,
Mike

[0] https://www.steakunderwater.com/wesuckl ... m.php?f=19
[1] https://trello.com/b/yuFPY5ts/fusion-16 ... ublic-beta
[2] https://trello.com/invite/b/yuFPY5ts/b7 ... ublic-beta

Fusion 16.0b1

Console Appearing Behind Main Window

Launching the Console view will result in the Console floating window appearing behind the main window. The only way to retrieve it is to move the main UI out of the way. However, it doesn’t float above the UI as a modal, so clicking off of it will result in the Console being sent back behind the UI.

Occurs on: RHEL 7.6

Cheers,
Mike

Fusion 16.0b1

Cache is cleared when time range values are changed

Anytime the playback global in/out ranges are changed, the entire timeline's cache is erased. This forces a playback of the entire timeline to re-cache the input. This occurs even when the time range is reduced to only frames that have already been cached. If the comp in/out (not global) are adjusted, some frames are invalidated, and on a repeat loop they never get re-cached so certain frames will never play at real-time playback.

Occurs on: RHEL 7.6, Windows 10

Cheers,
Mike

Fusion 16.0b1

LUT Enable/Disable separate from Viewer On/Off

Inside the LUT options there is an enable/disable switch. This switch has no affect on actually enabling or disabling the LUT in the viewer. However, if a LUT is disabled from the menu, then shut Off and On from the viewer controls the entire viewer will be come transparent and spit out the following error to the console:

Code: Select all

View LUT failed - disabling LUTs.
View LUT failed - disabling LUTs.

Occurs on: RHEL 7.6, Windows 10

Cheers,
Mike

Fusion 16.0b1

Background node outputs an RT Kernel warning

Adding a background node and changing any parameters of that node outputs the following warning to the console. If sliding the color parameters around, it spams the console with this warning.

Code: Select all

RT kernel Background failed to build:


Occurs on: RHEL 7.6, Windows 10

Cheers,
Mike

Fusion 16.0b1

LUT Edit options aren't synced to the currently selected LUT at startup

To edit a LUT, the viewer has to be viewing a node and the viewer LUT has to be on. However, when clicking LUT > Edit, the options menu that pops up is for the `FusionViewLUT` option and not for the LUT currently highlighted by default. For me, I have the `OCIO` env var set to ACES 1.0.3, so `OCIO Colorspace ViewLUT` is shown to be selected by default but isn't the default option to be edited. I need to manually press `OCIO Colorspace ViewLUT` and then hit edit for the edit menu to take affect.

Occurs on: RHEL 7.6, Windows 10

Cheers,
Mike

Fusion 16.0b1

Python 3.6 detected, but not usable

Python 3.6 was detected during the installation phase, however it is not usable from the Console as it is not detected within the app. The system uses PyEnv to manage Python versions, and the BlackmagicFusion.py script was installed to ~/.pyenv/versions/3.6.8/lib/python3.6/site-packages.

A reinstall with python36 from EPEL does not solve this.

Occurs on: RHEL 7.6

Cheers,
Mike

Fusion 16.0b1

FFmpeg not being identified on Linux

FFmpeg (3.4.6) coming from the RPM Fusion repositories is not being recognized by Fusion.

Occurs on: RHEL 7.6

Cheers,
Mike

Dear Mike

I think BMD has been pretty clear about 1 BR per topic. it helps them sort and find things. When you try to pile stuff in like this it just makes for a total utter mess including anyone who might report having seen the same problem, or. not .

S

Dear Mike

I think BMD has been pretty clear about 1 BR per topic.

Where and when? Not trying to be facetious here, I'm asking legitimately. Because (at least in these forums) BMD doesn't exist unless Resolve is mentioned, and they don't seem to have a problem with the globbed threads over in the Resolve forums. And in a perfect world, users search before posting. Having these all in one thread means it'll be easy to find and reference, and not get scrambled in the various bug/non-bug threads that may crop up. From my experience, in a non-uniform forum setup it's easier to browse or search one thread (assuming it doesn't get too long) than deal with an entire forum.

I'm intending to post all of these (and more) into the WSL Bug Tracker, which is considered the semi-official Fusion bug tracker anyways, once a bug in the forum is fixed. If BMD could adopt some standard software development practices and have an official Bug Reports sub-forum or portal (like every other vendor), this wouldn't be necessary.

I've tried writing this with the least amount of saltiness possible, but I apologize if it still comes off as gruff.

Cheers,
Mike

personal emails, occasional posts on forums.

when creating a new topic if you start it as BR or BUG its pretty easy to find. That generally gets the devs attention a lot easier, sometimes with online or offline response to supply what they might need to repro and fix the problem, especially crashers.

I agree there needs to be a formal site for bug reporting, but the industry standard that everyone uses is expensive AFAIK . that said there are open source options too. anything right now would be better than nothing.

S

[Peter Chamberlain]

Thanks for bug reports.

Thanks for acknowledging these reports have been seen, Peter. It means a lot and goes a long way for customer satisfaction.

Cheers,
Mike

Delta Keyer gives different results compared to F9: Erode/Dilate in Matte tab output enormous values around keyed object (r=5076, g=5076, b=5076, a=15360).

photo_2019-04-22_12-15-39.jpg (69.6 KiB) Viewed 7594 times

Panning and Zooming in Node field

This was like a first 30 seconds of usage bug. When scrolling mouse wheel it zooms in and out fine but as soon as you click the wheel to pan it will zoom out right away. Same thing goes for panning when you hold CTRL key (or if you have set scroll wheel to pan) as soon as you hold the wheel down it will pan to the left by itself

Thinking it would be good to have both this thread and the user interface thread
i.e.
viewtopic.php?f=22&t=88866
pinned at the top.

Cheers

I don’t know that I would quite cold as a bug, but I can’t seem to find a good existing thread to mention this. The drop-down menus in pretty much every page of the public beta for a version six team are incredibly finicky and sensitive, and I often find myself having to re-navigate through a drop-down menu several times before I can get the cursor to select the option I am looking for correctly.


Sent from my iPhone using Tapatalk

Fusion 16.0b3

Fusion won't launch if there is no dedicated GPU

It seems that with the latest Fusion 16 Beta 3 you can't launch Fusion if you don't have a dedicated GPU.
I think this might be an introduced bug when fixing up GPU issues.
Beta 2 launches fine.

Added a Beta 4 list for those using the board. @Pete, can you verify if your report has been fixed in B4?

Cheers,
Mike

Yep. onboard GPU is working again.
Actually what happened is that I needed to upgrade my display drivers in Beta3. Some changes must have happened since beta 2 ( which was working with older drivers). Anyways. All good.

OCIO colorSpace node problem

In a OCIO colorSpace node I load the OCIOconfig in the OCIO Config path.

The Source space and color space drop downs are empty.

If I copy the node into resolve fusion 16 the drop downs populate.

This node also works on the linux version of Fusion studio 16.

Hmmmmmm....

I have a big one and this is driving me crazy. I put a moving mask on one video file and another video file is on the background layer using merge node. It played fine in Fusion preview window, when I switch to Resolve timeline, it starts glitching. The mask dissapears and moves randomly every time I play back. It also rendered all the glitches that were in the timeline preview. Switching back to Fusion tab, it plays fine. I really do not know what to do.