Thank you!

thank you for looking! Looks as if that message is indeed dead. Without a translation map, it would be fairly useless...

The original use I had for it was in a Morph plugin (goes back to R8) so the various morph shapes could keep track of changes done to the original mesh. It's not properly working there any more; guess I know now why 😉

My current use is a Symmetry plugin I just finished. Right now, it only works by mapping right points and left points, and duplicating positional changes. I am now looking into possibilities to track added or removed points (and maybe polygons) on one side to duplicate that too. The TRANSLATE messages used to do that, including special information like "point A was merged with point B", but naturally all tools need to support that, and apparently the new kernel has moved on to some other method.

I guess I'll investigate whether MSG_POINTS_CHANGED is now carrying the required information...

Hi Manuel,

oh right, that does the trick! Thank you, one bug less! 🙂

Cheers,
Frank

Hi Maxime,

thanks for the answer and verifying what I had thought. Indeed I would need it in Animation mode and especially for the case where user highlighted multiple poses at once.

I had seen that thread, but it did not contain a definitive confirmation from Maxon. Maybe the thread I was thinking of was in a different forum.

Anyway, good to have your confirmation, now. And not possible only means I can stop wasting time looking around and instead need to implement another workflow for the user. Maybe not as slick as with the selection info, but no show stopper either.

Cheers,
Andreas

hi,

it's not possible, but I've answer your other thread so we can figure out there what are the options to achieve your goal.

Cheers,
Manuel

Oh, my bad then. Will update immediately, which I should have probably done before posting to the public forum. I'd say, if you can, please remove this thread, so nobody gets confused.

And don't worry about InitValues().

Cheers

This is 2 separated "optimization", one to prevent running the script when an animation is played.
The first one about the exeCount prevents running the script for each scene evaluation (aka each action, e.g user click on the object manager, select one object than another then another one, its pointless to execute your script each time)

It's a pretty dumb approach, I admit but its one 😛

Cheers,
Maxime.

I have a same issue. The problem solved by assigning argument without name:

self.AddSeparatorH(5, flags=c4d.BFH_FIT);

Hello @blastframe,

I forgot to put the final outcome for this here. So, after some back and forth we decided to not fix this for reasons I unfortunately cannot disclose. But we will update the documentation in an upcoming release to avoid this being as opaque as it currently is. This is probably not what you hoped for, but currently the best course of actions for us.

Thank you for your understanding,
Ferdinand

Hi, Maxime, great!

if I come across any additional issues of a similar nature, I'll update this post.

Hello @indexofrefraction,

without any further questions or replies, we will consider this topic to be solved by Monday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hello @mfersaoui,

without any further questions or replies, we will consider this topic to be solved by Monday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hello @blastframe,

without any further questions or replies, we will consider this topic to be solved by Monday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hello @davidtorno,

without any further questions or replies, we will consider this topic to be solved by Monday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Seems the only solution here is to register an own mode.

Oh, cool! I didn't know it was possible to deactivate those via comments.
Perfect, that should do it, thank you!

Cheers,
Frank

Ok, thanks for the clarification.

Hello @HerrMay,

thank you for your reply. Please note that we prefer users to flag topics as solved, as doing it ourselves always comes with the danger of erroneously flagging a posting as solved. Please refer to our Forum Guidelines - Forum Feature: Ask as Question in case you do not know how to do this.

Cheers,
Ferdinand

Hi @m_adam

Thanks for the response. Although just a personal sentiment, it is a bit disappointing having to wait 3 years for the actual API only to find out that it will be irrelevant in the next few releases.

Anyhow, will close this thread.