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

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

@r_gigante Thank you very much for your help, Riccardo! The suggested method of calculating the ngon index works fine with the Modeling::SplitPolygon() function, but functions like Modeling::GetEdgeNgons() sometimes return unexpected indices, which seem to be based on a different logic. I have updated the demo plugin and also included an image (NgonIndexProblem.png) in the zip file, which explains the problem: https://files.frankwilleke.de/index.php/s/EpGg1TkdzIemWJl In this case Modeling::GetEdgeNgons() and Modeling::GetPointNgons() returns indices which seem to be a confusing mix of ngon and polygon indices (or indices with and without offsets). Do you have any more ideas? Thanks in advance, Tim

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, The Test tag plugin is missing in the linked c4d file but I see the behavior with another tag plugin (Py-LookAtCamera SDK example). I was wrong in my previous post. This behavior of the Attribute Manager is applied to tags that can be added only once to an object. This can't be done for tags that can be added multiple times. Unfortunately the Python tag is registered with TAG_MULTIPLE flag so it can be added multiple times to an object but the parameter tab isn't attached to its parent object.

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

@mike No need to apologize, we are all new here. No worries. Especially during the starting phase of this new forum, we try to point even at small issues, hoping it will lead to a cleaner forum in future.

Hi, just a small request from our side: Please do not cross post to different forums (this topic on CGSociety). Chances are, you'll make people work for you redundantly. Cheers, Andreas

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

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

Hi, difficult to tell. Is this already happening, just by adding the CUDA include paths to the project or do you actually need to include from the framework as well? Maybe there's something with the order of includes? Or something needs to be undefined again, after including CUDA somewhere? Just guess work, here at the SDK Team we have no experience with the CUDA framework at all. Cheers, Andreas

thank you sebastian, this is a really helpful overview!

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

Thanks dskeith, that code worked perfectly. Thanks for that!

yup.. well.. i dont expect that to change very soon... so i guess we have to live with it still thanks for your patient support

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

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

Now Work Thanks Andreas

There is no way to get a filtered list of objects visible in the timeline. Sorry.

@a_block HI Andreas, Thanks a lot for your reply. I am implementing the first approach as suggested by you as it seems the most feasible approach to my solution. I'll get back to you if I found any issue. Thanks again