Topics created by Motion4D

Hello @Motion4D,

without any further questions or replies, we will consider this topic as solved by Wednesday and flag it accordingly.

Thank you for your understanding,
Ferdinand

Hi @Motion4D,

I am not quite sure if there will be anything in the pipeline soon, because the limitations of IDs and markers are more of principal nature due to Cinema's heavily procedural architecture; i.e., not really something that can be "fixed". If you have any particular feature in mind, I would ask you to make a separate post with a dedicated feature request.

We however already did identify the whole "identifying and object"-thing a few weeks ago as something that is probably not explained well enough at the moment and added it to our to-do-list. There are no guarantees on when this will come though 😉

Cheers,
Ferdinand

Hi,

without further feedback, we will consider this thread as solved by Monday and flag it accordingly.

Cheers,
Ferdinand

@m_adam Thanks for clarifying!

Thanks Bach! I knew it was going to be something simple like that.

@C4DS Thank your reply! I had to come back to this because I had problems with switching back to object context and this solved that!

@a_block It was the ID. I did use a random number, apparently one too many. I didn't think it would matter for testing but I guess I was wrong! I figured it would be something dumb like that. It was just weird it pointed me to that line for the error. And yes sorry my code snippet was confusing, I thought it was standard practice to put RegisterObjectPlugin on multiple lines for easier reading.

Thanks again!

Thanks a_block,

Sadly I had to disable the state() function because it breaks (delays forever) Material Preview/Shader rendering.

This State() function should somehow be isolated if possible ... but i guess this is the limitation of "checking the gui state".

kind regards
mogh