Hello @beesperester, without any further questions, we will consider this topic as solved by Monday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @johntravolski, without any further questions, we will consider this topic as solved by Monday and flag it accordingly. Thank you for your understanding, Ferdinand

Hi Manuel, sorry, I totally forgot about this one. Priorities have changed, so this isn't an issue anymore at the moment. Thanks! Cheers, Frank

Hello @john_do, the Asset Browser is an important feature for Maxon and we plan to build upon it. Despite that, we are not at liberty to currently disclose when we are going to provide Python bindings for the Asset Brower or if this will happen at all. I understand that this is a unsatisfying answer, but it is unfortunately the best we can currently give. Thank you for your understanding, Ferdinand

Thanks @ferdinand, I think that clarifies my issue. I'll what I can do here.

Hi @m_magalhaes , Sorry for the improper formatting of my question, I wasn't aware of these features. Thank you for the suggestion, the workaround can do the trick with the right safety precautions.

Hi, Please use the tags and the "ask question" features of the forum. Have a look at our guidelines for more information. That's the correct way of checking the Cinema 4D's version. Cheers, Manuel

Hello @pyr, without any further questions or replies, we will consider this topic as solved by Monday and flag it accordingly. Thank you for your understanding, Ferdinand

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