Fu Changed names of matte inputs breaks old macros, groups, comps

Moderator: Chad

User avatar
pingking
Fusionista
Posts: 733
Joined: Thu Aug 14, 2014 9:10 am
Been thanked: 9 times

Changed names of matte inputs breaks old macros, groups, comps

#1

Post by pingking » Sun Sep 03, 2017 5:19 am

Fusion version: Fusion9 build 13

OS and version:
Windows 10

Description of the bug:
In Fusion9 the internal names of some Inputs on tools have changed!

Seems that all Matte inputs are now named

Code: Select all

"Mattetyp.Matte"
, before it was

Code: Select all

"MattetypeMatte"
e.g. now it is:

Code: Select all

MatteControl1.Garbage.Matte
before it was:

Code: Select all

MatteControl1.GarbageMatte
this will lead to problems with old Macros which uses these inputs, it is simple to update them but not nice to break old macros. somehow the conversion of the inputs works if you open an older comp but not if its used in Marcos and will break saved comps from older versions

doesnt work even work with Groups!

Severity (Trivial, Minor, Major, Critical)
Critical (will break older comps)

Steps to reproduce:
you need a Macro which uses a Matte input of an internal tool as exposed Input (e.g. the exponentialGlow macro)
create a comp with this macro in Fusion8, conncet something to the Matte input of the macro, save the comp

if you now open the same comp in Fusion9 the MatteInput of the Macro is lost and no node can be connected to it.

Please, if possible, provide a Fusion setup to help demonstrate the behaviour, either as an attachment or between code tags:
added is an example comp saved in Fusion8
You do not have the required permissions to view the files attached to this post.

User avatar
AndrewHazelden
Fusionator
Posts: 1310
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 2
Location: West Dover, Nova Scotia, Canada
Been thanked: 38 times
Contact:

Re: Changed names of matte inputs breaks old macros, groups, comps

#2

Post by AndrewHazelden » Sun Sep 03, 2017 11:17 am

Hi PingKing.

I wanted to mention that BMD is aware of the issue. They have created a solution to the MatteControl issue that will be shipped out in the next Fusion update. I can't say any more due to NDAs.