Flame UI shortcomings

If every parameter of every node could be set pythonically…

noop node embedded as an elbow with obvious metadata
also HUDs like Lightwave and Softimage from 30 years ago, or am I showing the color of my beard?

sliders please

And casually show splats in flame :wink:

Extra points @bryanb :wink:

@andy_dill ’s gizmo hack does this by making the controls available in a matchbox. I think in theory it should be possible to automate this in a python script but in practice there might be too many variables to make the code do it.

Just integrate the UI that Autodesk developed for Toxik back in the day!

Here’s the v1.0 demo with a little more of a peak at splats…

Flipping the repo today.

Fu splat connects the splat to an action camera and pipes it in as a bg

First of all pics or it didn’t happen. Second, currently my OFX works with or without a camera file. You can import your action camera via a camera selection hook on an action node directly into the editor and still have the use of orthogonal viewports for setting up the volumes, alignment, scene scale etc. When you exit the editor, the OFX gets populated with all the values from the editor and only exposes global scene controls for rendering. So FU FU Splats :rofl:

:heart:

I think all this should filed under Schematic Feng-Shui

Flipped the repo public. GitHub - cnoellert/forge-wireless: Wireless Get/Set nodes for Autodesk Flame Batch — connect nodes by name, ComfyUI style · GitHub

Enjoy.

You can kind of do it, but it’s either clunky, or a pain. Clunky in the sense that you can hide all the nodes you have no need of controlling and set which node UI comes up via default.

A pain in the sense that you can code a null matchbox that is just the variables you want, include that in your group, write all the expressions to link things and set the group to only display the UI of the matchbox. I made one, well, at least eleven years ago now. At the time I had hope that a Flame Gizmo-like tool would spur the sort of sharing that we saw when Matchboxes started catching on. People could share custom keyers, effects, etc…

FWIW, this is how I’ve been working for years. It enables experimentation without getting tripped up in organizing wires. Once I made the jump, there was no going back.

I’ve used similar workflows in Houdini, Unreal and Comfy.

Simple version

Advanced (MUX nodes carry all outputs from action):

Yes, and better still a momentary overlay with layer info, like

Media2 : Front : ‘trees layer fill copy’

on for 2 sec every F4/Shift F4 hit. That will also tell you if you’re looking at the matte, in case you missed that(!)