Thank for the reply r_gigante I did in fact find the interface without any issues but was having issues using it in any way, I got as far as telling that it needed to use the Class<T> template but was unable to figure out due to either lack of documentation or my own lack of C++ knowledge I'll likely just stick to my own WebSocket library in the meantime until this feature is well documented/supported

@césar-vonc said in C++ new plugin with Project tool fail: The informations a bit dispatched and I don't find the doc very clear, for example, there is no link to download Project Tool on the Project Tool page, and globally not enough examples in the sdk. Second sentence on this page: https://developers.maxon.net/docs/cpp/2023_2/page_maxonapi_projecttool.html Agreed, the link is not very well visible, but it says "The Project Tool can be obtained from developers.maxon.net[URL-REMOVED]" And of course, the docs are very helpful, it just needs a bit of reading. [URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.

Hi Gigante, Thanks a lot for your reply. I'll analyze that and will update you on the results. Thanks again !

thats a pity... i can convert c4d layer shaders to vray layer shaders but cant do it in the other direction, because i cant create layer shaders ... sigh

Hi, it depends... Via the NETRUNONSERVER flag (to be returned from GetRenderInfo()) a VideoPost specifies, that it can be run on the server. Where the VideoPost is actually executed in the end, depends on the scenario. For a distributed single frame rendering, such a VideoPost will be executed on the server. On the other hand, for animation rendering, where every client finishes entire frames, the VideoPost will nevertheless be executed on the clients. Cheers, Andreas

This worked. Thank you.

Hi, thanks but i managed to fix it. It wasnt a Cinema4d related error. Apparently a bad argument to one of python methods was causing it to return the filepath of the script instead.

damn. totally didn't look there. sorry. Alfie

Hello, LoadDialogResource() and LayoutFlushGroup() should work perfectly fine together. Typically LayoutFlushGroup() is called in reaction to some user interaction or in InitValues(): Bool CreateLayout() { if (!GeDialog::CreateLayout()) return false; if (!LoadDialogResource(11000, nullptr, 0)) return false; return true; } Bool InitValues() { LayoutFlushGroup(11003); AddButton(100, BFH_SCALEFIT, 0, 10, "Button"_s); LayoutChanged(11003); return true; } best wishes, Sebastian

Thanks for the solution and explanation Yannick. It's working perfectly now and I can finish converting my scripts.

Cool. Will do.

Hello, please post questions on Cinema 4D plugin development in the "Cinema 4D Development" forum. When doing so, please also use the appropriate tags. MATERIAL_GLOBALILLUM_GENERATE is the correct ID of that parameter. You just have to set the parameter value of the material you want to edit: material->SetParameter(MATERIAL_GLOBALILLUM_GENERATE, false, DESCFLAGS_SET::NONE); please notice that the ID is defined in the millum.h header file. If you have general questions on how to handle materials with the C++ API you will find information in the documentation: Materials and Shaders Overview BaseMaterial Manual Material Manual best wishes, Sebastian

Hello @iluxa7k, I just move this thread to the "Cinema 4D Development" forum. When creating a new thread, please also always add the proper tags. best wishes, Sebastian