@blastframe said in Inserting an Image Shader into a Dynamic Slot: This is the C++ code of the shader: Hello, just to make things clear: the above snippet is NOT the "C++ code of the shader". It is the resource parameter description, that defines the parameter types and layout. See Description Resource. best wishes, Sebastian

@r_gigante Yes! It's really helpful.

Hi, check RENDERFLAGS (Link). You will have listen in NodeData.Message() for them. I never did use this, but checking for RENDERFLAGS_PREVIEWRENDER sounds promising. Cheers zipit

@zipit and @m_magalhaes Thanks for the confirmation. Will close this thread for now. Will just ask separate question on GeUserAreas.

hi, yes closed is a better word in that case, I still need to add something in the documentation. Cheers, Manuel

hello, We need to ask if you are compiling the SDK, your own project, etc. Different question, you should open a different thread It will help other people to find the thread. Cheers, Manuel

@m_magalhaes Thanks. Next time I will follow the instruction. Thanks

Hello Sebastian, thanks for this quick response! I dind't know about this. But this solved my issue! Best Regards, Florian

Hello, Thanks for sharing your answer @zipit and @Cairyn Cheers, Manuel

Hello Manuel, thank you very much! This was exactly what I needed! It is not exactly for my own render engine. I just wanted to implement an open source one as a side-project and to familiarize myself with that topic by just doing it. Best Regards Florian

@zipit said in LAYOUTGROUP Description Resource: STATICTEXT { JOINENDSCALE; } I'm searching this solution for long time, thank you so much!!!

@C4DS Thank you. Works as expected!

This issue is now fixed in R21. Cheers, Maxime.

Issues with GetAllHighlevelData() and VariableTag.SetAllHighlevelData() is now fixed in R21. Cheers, Maxime.

This issue is now fixed in R21. So you don't need to manually SetDirty / Send the message. Cheers, Maxime.

This issue is now fixed in R21. Cheers, Maxime.

This issue is now fixed in R21. Cheers, Maxime.

This issue is now fixed in R21. Cheers, Maxime.

@m_adam Hi Maxime, Thanks for this workaround, indeed puts the polygon on the right place. Best, roger

@m_adam said in Distributing Python Plugins that have Dependencies: As an Idea but didn't try and will not have the time to do it today (so if you try, do it at your own risks), but you could try to install things using directly the python executable from the resource folder I'm moving onto different parts of development, but I'll likely want to investigate this later and will post an update if I do. Thanks!