@r_gigante Thanks for the reference. For anyone trying to achieve the same, here is a sample file. https://www.dropbox.com/sh/z1lzyphp8qnt9kw/AAB2P5gNo16IHafgc6xPEsy4a?dl=0 Thanks again for @zipit for the help.

@zipit work fine thanks a lot

@m_adam Thanks! Works as expected

Thanks @PluginStudent

Got it. Thanks, again, zipit for you answer.

@r_gigante Thanks for your reply! You were absolutely right about checking input type. When i did a simple type check everything started to work as it should!

Cool! Thanks.

Hi, thanks, that answers all my questions. Cheers, zipit

I'm sorry for the huge delay asked for this question, but it appears, that this dialog layout is hardcoded in the default Cinema 4D layout, so when you open it this dialog, it loads this layout by default since it's saved in the default Cinema 4D layout. Unfortunately, there is no way to do the same thing with code but you can split your GUI in 2 parts and let the user build its own layout with all the Command and your Dialog bellow. Cheers, Maxime.

@Cairyn Thanks, all work fine for this module

@Cairyn Thanks again! That's what I was afraid of, but thanks for the information!

Thanks @moGRR for reaching out us. With regard to your question, as pointed out by @zipit, it's not possible to have a Python Generator to generate object which can be recognized as real spline by generators/deformers expecting a spline as input due to the Python Generator flags used in its registration. Beside the option mentioned by @zipit I also invite to have a look at this post where it's presented a generator outputting spline and accepting splines as input. Best, R

@m_magalhaes No other dependencies. Plugin type is deformer. Yes, i should probably ask it on Redshift forum. Thanks for reply!

Nevermind. Trying to explain will probably lead us too far. I was only wondering if messaging was possible between a CommandData and its GeDialog.

Work fine Thanks a lot Manuel

Hi @tdapper, unfortunately, I confirm this is still not possible. Cheers, Maxime.

I figured out the problem. I needed to assign the UD in Main.

Extra info! While I had set this topic as solved, without an actual WORKING solution being provided, I simply wanted to point out for future reference that R16 - R19 has a slight different behaviour. As with R20 and R21 the first time the dialog is opened it gets positioned centered on the current mouse position. On all subsequent opening it gets positioned with its upper left corner at 0,0. Something got "fixed" between R19 and R20, but not "fixed enough".

Ah! Okay. Thanks.

Hi @fwilleke80, unfortunately, I confirm the shader effect is almost always dirty. I don't have any real workaround maybe you can retrieve all noises and compute their dirtiness, but this is indeed a very hard topic to handle all cases because you will also need to handle the actual parameter of the shader effector itself. Cheers, Maxime.