Flame UI shortcomings

curious how others deal with this - trying to pipe from a very narrow source into a bunch of nodes that take up much more space than the source and then have to pipe back into a small action icon in batch… at some point the UI is gonna need an overhaul…

lots of elbows and breakouts to give more space downstream

Yeah, I end up just building a much expanded system of outputs from the PSD or EXR with labelled mux nodes and elbows

I would consider loading the psd directly into the action node, then extracting any layers that needed pre-action work done. But point taken.

This Is The Way GIF

This is what I have done in the past and would like to see for exr sequences.

additional manual labor is always an option @BrittCiampa @ALan - but some smart UI updates could prob save us a lot of this effort IMHO

Nuke. There must be a multi-channel request somewhere.

Hiya @TimC !

Jeezus… open that thing up… give it some breathing room!

(warning… snakes incoming)

I would use About to Mux Shit Up and then Tidy Nodes. Both are on the Logik Portal. The first one throws the muxes on, then the second is used to align, distribute, and scale nodes. Scale up in Y to add vertical space btwn nodes. It will work on Action Input mini nodes.

You could go as crazy as you want I suppose. Rename the muxes, maybe put Compass on each section.

We’ve all done it, got through it then winced when the client wants changes and you’ve got to dig into that plate of spaghetti.

Sometimes I’m jealous of the little trees you can copy from a nuke script, paste into an email and into someone else’s batch script.

But often the shapes of the mess make me remember what it was all doing. I get lost in nuke scripts. And electrical diagrams.

so these are all good answers but still not addressing the underlying problem IMO: constantly having to rearrange all the deck chairs to make room for more guests… its just… exhausting after awhile. I also can’t escape the feeling we could all benefit from some UI refresh. Maybe the way to go is the @imag4media method

Hidden inputs in mux get a bad wrap but it’s my go to now. I also wish that we could upgrade the mix to behave like Comfy’s get and set. Simple feature but would be amazing.

Desktop paint is and has always been the answer…

Right?

:rofl:

I gave it a go reworking the UI and came up with this. It’s a bit retro but I hope you like the simplified interface. You won’t have an issue with node connections anymore, that’s for sure

There was a nice little script I remember we had in nuke at the mill - you pressed a hotkey and it could break apart the exr then you could put it back together again in whatever order you wanted - handy for roto that came back in different order.

I’m thinking the same could be true here: I often get frustrated by these multi layer dmps/psds because I can’t see what’s what. Of course you can load it in action but then it becomes slow and there aren’t as many options to precomp stuff as action only works in layers not a tree.

Is there a way to write a python script to open up a dmp then fuse it back together? Maybe inside a group? Fairly certain there could be a way to engineer this.

Is that even useful to you?

Yeah and how painful is it when you are looking for a layer in a big psd that hasnt been labelled well and you madly hit F4 to find it and you skip past it but cant go back without going around the block. We need a way to reverse back through the psd. Shift-F4 maybe ?

YES.

Oh you mean you don’t find it useful when a matte painter has given you thirty layers all named layer 1, layer 1 copy, layer 1 copy copy, layer 1 copy copy copy???

5 Likes

My favorite clip to send to the “is it ready?” crowd.