Great!
Cheers!

Thank you for your advice. The build was successful !!

hi @ferdinand
thank you very much for your response!

the python_init.py does the job perfectly 🙂

great support, thanks a lot!

best,
marc.

@johntravolski
I figured it out, I needed to add

node.Message(c4d.MSG_UPDATE)

after the for double loop where I set the polygons.

After a few mails with Ferdinand I switched to a Tag plugin solution. This does the job perfectly.
So the solution was not to use an Object data solution but a TagData.

Thanx!

Hi @Quencyjones first of all welcome to the plugin cafe community,

Nevertheless, this forum is about Cinema 4D Development to build plugin or script in Cinema 4D. This is not a Cinema 4D user forum where you can find solutions to technical questions about how to use Cinema 4D, but only about its API.

So I think it's better for you to ask on more Cinema 4D user-centric forum such as cgtalk, core4d.

Cheers,
Maxime.

Thanks for guiding

Regards,
Folexin

Hi @ferdinand.

Thanks for all of the help. That all makes sense to me. Hopefully in the future there will be a better work around, but for now I've got a workaround that is clunky but working.

Thanks again,
Dan

Works like a charm, thank you!

Greetings,
Frank

@m_magalhaes

Thank you! Works perfectly.

Dan

hi,

technically, it is possible, but you will have to figure it out yourself and be prepare to do a lot lot work.
the answer is pretty no.

Cheers,
Manuel

Hi @rsodre, a quick update from Pixar that hopefully shall address your issue

From: Ivan Kolev [email protected]
Subject: Re: [PixarAnimationStudios/USD] Deadlock loading usd (#1341)
Date: 22 March 2021 at 11:53:37 CET

We resolved this by switching our plugin to refer to the copy of libtbb.dylib included with C4D's USD module, using install_name_tool -change

As our plugin runs on 3 platforms and on 3 hosts (3dsMax/Maya/C4D), our approach to TBB usage is to rely on its full backward compatibility: we compile/link against the oldest version that does the job for us (4.4) and expect that the hosts provide newer versions.
In case of C4D we didn't do that because C4D doesn't include TBB in its main application, though some of its external modules do include their own copy of TBB. Similar to the other modules, we included our (old 4.4) copy of TBB.

But this was no problem until now, the copies of TBB carried by C4D's modules haven't interfered in any harmful way. And the new USD module in R23 didn't change that.

The source of the problem here is probably the fact that our plugin links to our own static copy of USD, which causes USD to be loaded twice, along with two different copies of TBB (and maybe the version mismatch is not important).
So, linking against C4D's copy of TBB resolved the TBB deadlock problem, but we have now a new duplicate symbol problem, which I opened a new issue about: #1479

Cheers, R

It works perfectly, thanks again!

Cheers,
Frank

Thanks Manuel, yes that's how I ended up doing it in the end.

I thought it would've been simpler to extract a variable from the main function, since it had already calculated. All I would need is to save the variable somewhere where the button function can read it, so this is where I tried the global variables but it didn't work.

@m_adam alrighty got it working. 😃
Thanks again. You can close this thread if you like.

Cheers,
Sebastian

Thank you Ferdinand

Hi @Virtualritz,

without further questions or updates we will consider this topic as solved by Thursday and flag it accordingly.

Cheers,
Ferdinand

@Cairyn @ferdinand

Thanks for the response. The python generator works as expected.

I did try to retrieve the cache earlier for mograph but with a python tag rather than a python generator, but it has some priority delays. Your solution is much more stable.

Now, I don't have to jump to houdini for such simple scenes.

Have a great day ahead!

Hey guys, thanks for the explanations.

My only concern is that I can't really do anything besides closing Cinema4D to cancel the operation. Just for reference my plugin is a fluid volume that needs to be visualized in the viewport. This is not an expected workload, stumbled on it by chance, but so can one of the users.

Anyway we can close this thread if it's not a bug.

Regards,
Georgi.

Thank you @bentraje and @ferdinand !

You make the deal of the EffectorList function much clearer ! It works well now