@mp5gosu deleted an owned topic is now enabled for all users and no error is anymore notified when attempting to delete a first post. Best Riccardo

Great, thank you for the great explanation, especially of the loop! I will give it a try. -Pim

Hello, please see here: https://developers.maxon.net/docs/cpp/2023_2/page_maxonapi_programming_advice.html and especially here: https://developers.maxon.net/docs/cpp/2023_2/page_maxonapi_dev_windows.html (Windows includes)

Hi, actually this is not a bug, but a design decision. Here at MAXON we have a pretty large code base and especially disabled code branches tend to age a lot faster. So we try to force developers to also maintain such code pieces or to at least think about, if they are still valuable and otherwise remove and thus cleanup the code base. Cheers, Andreas

Hi, glad you were able to solve your problem. We'll take this as a hint and see if we can improve our documentation in this regard. Cheers, Andreas

Hello Daniel, thanks for reporting this. There are currently a few issues regarding the Plugins menu pending. These are being investigated. Cheers, Andreas

Hello, you find information and examples on jobs and threads in these manuals: Jobs Manual Threads Manual best wishes, Sebastian

I already guessed so. Thanks, I think we can close this post. -Pim

Thanks for the responses guys... I think I've found a virtual solution/work-around for the time-being. Cheers.

"actually, you can still multiply in one line. You just have to multiply a matrix with a vector:..." D'oh! I'm surprised that I didn't try that - tho it doesn't seem as intuitive ("vector = some other vector, being modified by some operations" vs. "vector = a matrix, imposing/operating on some vector", etc.)... do you know why the Vector lost so many direct operators (* other Vector (Dot()), * Matrix, % other Vector (Cross()) - there may be others)? Apparently, you can still '!v' to normalize it (yay), even tho there's a v.Normalize() call... and I can understand why the "Identity Matrix" operator might have changed from '!' to '~'... some of the other changes just seem a bit arbitrary. I've already made all the changes at this point, but thanks for the tip/reply - I'll keep that in mind for future reference. Cheers.

Thank you, Sebastian. Your reply clearly shows what I should learn. I need a little time to understand, but I am working on it and I made a little progress. Cheers Makoto

Hi rsodre, thanks for writing us. The Cinema 4D SDK has it's own structure which actually needs that both the plugins and the frameworks folder share the same parent folder and this is what the SDK toolset (sourceprocessor and projecttool) expects to work with. Any change to this structure may lead to unexpected behaviors and is highly discouraged. Using the workaround you pointed out in the projectdefinition.txt is not expected to work as you've already checked. On the contrary using symbolic links seems to work, but again this is not officially supported. For the sake of completeness the ln command I used is ln -s <path to frameworks> <path to plugins>/../. and I succeeded to compile all the shipped plugins under macOS 10.13.6 with Xcode 9.4.1 Cheers, Riccardo

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

Hi Riccardo! Thank you very very much for your detailed explanation. That helped me a lot and YEAHHHH....got it working Thanx in advance for your time! Best regards Andi

Hi, in Cinema 4D R20 the return value of NewObj() has changed. It now returns a ResultPtr<>. This simply means you need to properly handle the error case. In our C++ SDK documentation this is covered on the API Transition page and in more detail in the Error Handling manual. In the microsdk example there's a snippet showing one way to handle the error. One last request, please consider tagging your posts (as I did now here), so we can keep this forum tidy and easy to search. Cheers, Andreas

Now Work Thanks Andreas

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

And sorry @kbar, @C4DS, @aturtur I should have found it earlier, but after looking at how to implement it, I figured out it's already possible since R21 with the flag DR_COLORFIELD_NO_SCREENPICKER import c4d class MyDialog (c4d.gui.GeDialog): def CreateLayout(self): self.AddColorField(1000, c4d.BFH_LEFT | c4d.BFV_TOP, colorflags=c4d.DR_COLORFIELD_NO_SCREENPICKER) return True if __name__=='__main__': global dialog dialog = MyDialog() dialog.Open(c4d.DLG_TYPE_ASYNC, xpos=-2, ypos=-2) Cheers, Maxime.

@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.

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