@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

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.