Flame Feedback requests implemented in Flame 2026.2 Update

Hello Everyone,

Here’s the list of requests submitted at flamefeedback.autodesk.com that have been implemented in Flame 2026.2 Update.

Thanks to everyone taking the time to add requests and vote.

FI-00166 Preferences: Select a default render location for Batch’s Render nodes

FI-00256 Batch: Drag and drop Matchbox / Ligthbox shaders from one node bin tab to another

FI-00398 Python: Possibility to change the Open Clip version

FI-01237 Batch: Enable/Disable Render Node via Context Menu

FI-01894 Create alpha maps inside action using selective keyer

FI-02149 Media Panel: Create Batch Groups and Reel Groups template.

FI-02296 Selective: Combine Semantic keys with other keyers

FI-02431 Selective: Ability to output the matte of a Selective

FI-02506 Default Batch Group Prefs: Schematic reel names and settings

FI-02532 Batch: Ability to set new Write File nodes to Follow Iteration by default

FI-02573 Memory Management: Ability to flush the VRAM from inside the application.

FI-03180 Batch: Have Iterations start at 0 rather than 1

FI-03372 Selective: Update the object isolation models to something similar to Resolve’s Magic Mask

FI-03448 Batch: Add options to the Render Node’s destination list.

FI-03451 Batch: Ability to set default path for the Write File node per project.

FI-03506 Type: Add a Favourites tab to the Select Font widget

FI-03519 Type: Option to disable the style display in the Select Font widget

FI-03538 Batch: Ability to use the Snapshot feature

FI-03541 Snapshot: Add Exported image to the OS clipboard

FI-03528 Media Import: ARRICORE codec support

FI-03559 Type: Expose the Layer Opacity channel in the UI

FI-03570 Python-API: All batch clip node parameters need to be exposed (but please can we can start with timing)

20 Likes

Some great stuff in here. The suggestion box works.

5 Likes

Legend.

1 Like

Love this list! Really appreciate all the effort that goes into it @fredwarren

1 Like

LOVE this @fredwarren

5 Likes

What a warm fuzzy feeling

its a great update, thank you team! just one tiny thing that i cant wrap my head around: why does the standard gmask tracer in the node bin wake up with a front output activated? is there a specific reason?

Yes, this is so you do not have to use the 1 and 2 shortcuts to switch to the Matte output when you navigate between Action and GMask Tracer nodes.

1 Like

Oh hmm. I dont understand that last part. I never had any issues. Switching between a GMask Tracer with only a Matte Output and an Action with Matte Output Selection on the main Render Layer doesnt seem to do anything unexpected for me over here.

1 & 2 are for when the matte is turned on in Output Selections. But on the GMask Tracer its been added to the primary Render Layers, so shuffle thru the Results.

I suppose its no harm done… Can change the node default back to the other way if really miffed about it. In the long run, might enjoy being about to use the GMask Tracer as a passthru for the Front i suppose.

For what it’s worth, I can’t seem to get a new default to stick. Keeps reverting to the new behavior of having a comp & matte output.

Plus one here, I would really like the old behavior back but I can’t get it to work