"Set User Default Birth State" right click

Wishlist and RFEs
1

With active, and efficient dynamic network building, one has to be aggressive about modifying default operators to fit their current need on a regular basis. An alternative to setting up each base point for an op every time you birth one is to remember where common pre configured nodes are in your specific network and copy / paste them, or by flooding your own personal pallet with favorite versions.

Ive found that these approaches become very tedious and can falter efficient flow-state network building “zones”. I propose that in future releases one could perhaps set up their own easy to recall way of changing an ops birth state… I propose 2 potential depths of such a feature are possible:

1 - Right click and “Set user default op birth state”
This would mean that at any point one could right click an op and all the par and settings would be loaded in the the user based default birth state storage for that type of operator.

2 - The latter feature could be expanded upon by making the state its own potential “user default” storage where one would have their own specific access as an alternate to the Derivative default birth state… so for example after setting your “user default state” as mentioned above, when the op selection menu is open, if you hold “alt” as you click or press enter after typing an op name… it with birth that op with your user distinguished default birth states, and if alt is not held as it is birthed it is the Derivative default.

I do not believe this hotkey combo is in use at this time while birthing ops, so this opportunity is ripe.

Thank you for listening!

2

I +1 this more so for the ability to set a “blank” birth state to all operators. Almost like a “pro” mode. There are lots of operators that start with default parameters set to non-0 values, or comps that start with objects already inside them. Two good examples are

  • a geometry comp being created without a torus inside, the default really should be to have an In SOP with it’s display/render flags turned on so you can create the geo comp and connect something to it and keep working. Right now the only workaround is a trick that most users don’t know where you can right click on the output of the SOP, switch to COMPs in the op create, then create a geometry comp and it’ll be created with an in sop instead of a torus inside.
  • bullet solver comp is the same thing but even more so because not only does it have things inside, it’s default birth state is almost an “example” of a functioning simulation with gravity already defined and 2 actors inside.

My recommendation would be to have everything zeroed out and empty in most cases. Then the user should continuously be directed to op snippets to see examples and such.