I guess im not getting Automatte the Node then!
To me the user bin option seems very reasonable and easy. I wouldnât vote for putting resources into duplicating functionality for something that is already good and easy to drag from a bin.
3 Likes
Pulling a node called âAutomatteâ from the user bin isnât really that much harder or onerous than pulling Image from the Flame bin, right?
I get that it would be more convenient to have that functionality built-in. But I compare the about 45 seconds it would take a user to either make a preset or put it in the bin, to what this request would mean on the developer end.
The number of ADSK meetings, where this would be taking up time and energy to just decide upon, then the research into it, then the cycles of development, then the internal testing, then the user beta testing, then releasing it, then bugs found by users, then bug-fixing, then releasing that â and the cycle continues.
For functionality that already exists.
While I think most of us could agree that we would much more value development into new and missing functionalityâŚ
2 Likes
This is not a duplicate function at all. But rather to expand functionality. Expand machine learning driven intelligent mask selection to other nodes that require Mask channel input.
Yes, sounds nice. But the development of that feature would deprive development of many more crucial features and innovation that we all would like. There is an easy and reasonable workaround to your concern.
How about we let the devs spend their time on something new?
1 Like
When development resources are very limited, I strongly agree to prioritize solving the problems that most people expect.
excited to see all of these new exciting features you all mention!
1 Like