Hi,

unfortunately we can't help developing algorithms. So, what has been said here and in the Quaternion Rotation thread, is probably all we can contribute from MAXON's side.

Maybe somebody from our community is willing to step into this and help out?

Cheers,
Andreas

Hi,

please, do not delete discussions threads. The contained information might be valuable for future readers.

Cheers,
Andreas

Hi @pyr,

In Python, there is a GIL which do not allow Python by design to execute something in parallel.

In Cinema 4D all our functions (so everything which is in the c4d python module) is "GIL safe" in order to avoid any issue with Python memory.
So in Cinema 4D thread are designed for doing GUI, or background stuff.
Moreover, keep in mind creating a Thread have a cost in term of time (to create, execute, delete them).

Finally, I would like to point you to multiprocessing vs multi-threading.

Note that since it's more an algorithm problem than an issue related to our API, we can only provide you hints.

btw, I also turned your topic as a question. See Q&A New Functionality.
Cheers,
Maxime.

Hi @Rage

I guess export_OBJ example on our Github repository is what you are looking for.
Note for the moment values of the BaseContainer are not available in the Python Documentation.
But you could find them in the C++ documentation about fobjexport2.h.

If you have any question please let me know.
Cheers,
Maxime.

Amazing! Thank you again Andreas!

@mikeudin Thanks for making us aware. We'll change the link with the next docs update.

Hi,

this sounds more like a TR issue and not so much an SDK problem.
If so, then I suggest to rather use the How Can We Help? form on MAXON's homepage.

Cheers,
Andreas

Thank you very much for your support !

Working as expected now ... didn't think of playing with the PLUGINTYPE_xxx
Thanks for details.

Hi Roger,

yes, you are right, this seems a bit strange on first sight. But the entire concept of VideoPostData providing C++ functions to extend the render pipeline does not hold for a GPU renderer nor the viewport display (which in the end is used for the preview renderers). This doesn't make it any better, but may at least explain the current inconsistency on our side. I'm confident at least for ProRender this is being looked into, but I can't say anything nor make any promises about future developments.

Cheers,
Andreas

@m_adam Thank you for your team's reply.
I will share my exploration in this post in the future.☺

Hi,

I'm afraid @Cairyn already contributed everything we could.
We need to leave this to the community. Sorry.

I have moved this to the General Programming & Plugins Discussions category, as I don't regard it as a very C4D specific question. Please, correct me, if I'm wrong.

Cheers,
Andreas

Sorry, in contrary to what I had written here before, we will not add RestartApplication() to the documentation. These calls have certain intricacies, so their use will be at own risk. This is now based on an answer from our development.
Cheers,
Andreas

I forgot to turn this thread into a question. Done now, and as I regard the last post as a "solved" message, I also marked it as solved. Please, don't hesitate to turn back to unresolved, if I was wrong.

Hi @C4DS, thanks a lot for your message.
Documentation tag have been added.

Drag and Drop Manual, changed to:

GeDialog Drag and Drop GeUserArea Drag and Drop GUI Message Drag and Drop

Links will work correctly in the next update of the doc.

However you are right, the code sample in the old manual was wrong. It should have been

if (CheckDropArea(DLG_GROUP, msg, true, true)) {}

Note, you could also create your own function as demonstrated in the AsyncTest Example.

Cheers,
Maxime.

Thanks, @C4DS for pointing out this issue.

It will be fixed in the next version.
Cheers,
Maxime.

Nice, congrats ☺

I have to admit, I forgot to turn this thread into a question. I did so now and I also marked it as solved, as your last post seems to imply.

Cheers,
Andreas

Hi Andreas,

Thank you very much! ☺
It works like a treat and I appreciate your thorough explanation!

Happy Friday!

Andre

That's great, Andreas. Thanks! I'll kludge on until then.