MCG re-think

[theAndreas]

I would love it if mcg was working in a different way.

If you want to make a modifier you would just add an empty mcg-modifier on the stack. Click a button to open to editing UI and have live feedback.

If you want to make a mcg-controller you would add an empty mcg-controller and start editing from there.

If you want to build your own primitive you click and drag out a mcg-primitive in the viewport. click a button on the modify panel to open the ui.

You get the picture.

Maybe there could be some input and output nodes that relate to the end use as well. Modifier, controller, spline, primitive etc could all have different start nodes in there.

The biggest thing is the live feedback though! That would be amazing. The workflow right now is not great.

/Andreas

[theAndreas]

Another benefit to this approach would be that you could have just a single clean MCG-modifier, named simply "MCG", in the modifier list. Instead of flooding the list with ill named modifiers you could load the finished ones as presets inside the newly added modifier. 

After that you could rename it on the stack to a name that matches to whatever it does. 

[michael_spaw]

+1 Great Idea.

-Michael

[alitanucer]

totally loving this idea. I just proposed similar approach like making it like Grasshopper. 

It will cool if this is a certain mode in the editor window that you get live feedback on the viewport.

[aslantamjidi]

+1

[MartinBeh]

Sounds a bit like the recently introduced Data Channel modifier?

[theAndreas]

No, I do not want this layer-based and building the mcg should not be done in the modifypanel.

There should only be a button on the modifypanel that opens a separate window for editing your mcg. The mcg editor is still node-based. Other Ui-elements that you want for your mcg-features will of course be displayed on the modify panel, once you add them that is.

/Andreas