Already found the reason, sorry to bother you, all good Cheers, Frank

Given my own blind spots on flags and GetAllTexturesNew() I was actually quite glad, you hadn't had the time to look into it. Unfortunately I was obviously too late to stop you from investing time nevertheless... Sorry. Which then will turn a bit into a data structure/similarity problem when you want to group your textures into nice packages. Yeah, this, plus my concerns below. Regarding running over the project's frame range: Especially character animators seem to have a habit of storing information outside the project's frame range. That's where I'm afraid to loose information. Or I would need to establish additional means to figure out such frames. I doubt document's GetMin/MaxTime() help here. So it would be iterating over all tracks in a document I guess. And you are right, you shouldn't spend additional time on this. Given the result of my other current thread, everything in this thread really is the least of my problems. Somehow I have a "Händchen" (I guess, one would save, I have a knack for) for maneuvering myself in these situations...

Hi, It looks like the problem got solved by Sized function. Thanks a lot @m_magalhaes and @m_adam !!

hi, have a look at this thread please. Cheers, Manuel

Oh yes, it works. Therefore, the topic is solved Cheers, Frank

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.

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

Ok, thanks for the clarification.

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

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

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

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 @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 @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

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

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

I have a same issue. The problem solved by assigning argument without name: self.AddSeparatorH(5, flags=c4d.BFH_FIT);

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.

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