@PluginStudent Thank you.

Thanks Both of you @zipit @m_adam , Quote: "keep in mind coping data is expensive" I had the feeling that the very nice example I am building on has some limitations (speed) as you mentioned. I guess I have to re organice this section (selecting points) and clean up. My aproach as a beginner is more or less like this. try get it to work anyhow try to understand it by cleaning try to make a compact function so it doesn't break my code everytime i touch it ... I have an old C++ code as an cheat sheet to get a general idea how a perfomant code could look like (selecting & working just inside one big point object list, as far as I understand it) , but at this stage I can't combine them jet hence the different selecting aproach. Anyway I try to get somethingmore robust ... Thank you for your time. mogh

@m_magalhaes Hi Manuel, Thank you for giving me some time to check this out. So after a bit of testing and changing the code to work with Cinema I cannot replicate the issue. As you mention it seems to be related to Pyblish. I did find interesting that when running the code in Cinema without Pyblish you can't see the active frame running through the timeline, while you do see it when running through Pyblish. Perhaps that's the correlation with the crash. I will close this as solve, for the fact that it does not crash in the Cinema context. Thanks again! Andre

hi, I will mark that thread as resolved tomorrow if you don't have anything to add Cheers, Manuel

Hi @blastframe unfortunately for the moment is not possible to implement its own logger in python. However, you could use any existing loggers. Here an example that writes into the Application (Default) Logger. import maxon txt = "My Wonderfull Text" defaultLogger = maxon.Loggers.Default() defaultLogger.Write(maxon.TARGETAUDIENCE.ALL, txt, maxon.MAXON_SOURCE_LOCATION(1), maxon.WRITEMETA.DEFAULT) Note that the print simply reroutes to the Python logger. But it can be useful to directly use the logger to write if you pass the write meta maxon.WRITEMETA.UI_SYNC_DRAW this way you can force a redraw of the console (slower) after each print, this can be used to avoid the limitation mentioned in the second part of this post. Cheers, Maxime

@PluginStudent Thanks for the idea of how to solve this! I was doing what you described before posting my example, but probably making it too complicated. The documentation for the Link gadget describes the pointer LINKBOX_ACCEPT_MESSAGE_ACCEPT as 'A pointer to a boolean value. Set this value to true to accept the object.' so that sounded like what I needed. I've rewritten the approach you described and have it seemingly working.

hi, I will mark this thread as solved tomorrow. Cheers, Manuel

hi, tomorrow, I will consider that thread as solved without further news. Cheers, Manuel

Great, thank you.

hi, must be monday, sorry, the 21.207 IS the current last public version (and after another test, the bug is definitely there). It's already out the next update we can't tell what and when. Cheers, Manuel

@m_adam Thank you for the clarification and the code example, Maxime!

@zipit Hi, Thank you so much.

Yes, Thanks.

hello, I will consider this thread as solved without new information from you Cheers, Manuel

@r_gigante Perfect! Worked like a charm. Thank you.

Hi @karol_w! This is exactly what I am looking for, because Octane keeps crashing on me. Unfortunately, I am not very good with coding. Is there any chance you would share your plug-in? Or point me towards where to find resources to build that myself? Thank you very much!

@m_adam You are a genius - I am in awe! Thank you everyone for the help!

Thanks, it's good to know that there are internal functionalities actually using these flags!

@m_adam & @PluginStudent Thank you both! This was exactly what I needed. This forum is so so helpful.