@m_adam Hi, and thanks for your feedback and suggestions. The Take System sounds like requiring too much user interaction after the import, and I think we won't therefore consider it/ The motion system and "global" Python Tag seem like coherent alternatives to loading every animation one after the other. Now, the last step is to choose one of those systems... I think we'll first implement the back to back loading of animations as suggested by @kbar, as this seems like the most lightweight and straightforward solution for a quick iteration. Cheers, Loïc.

@m_magalhaes I'll write it in your way Thank you very much. Cheers!

Great, I will do that. :-)

Hi Rui, thanks for reaching out us. With regard to your issue, I confirm that whilst VS is more "tolerant" with regard to code-style check, Xcode is less. The code style check, which is embedded in our source processor, expects tabs rather than spaces for code indentation and it could happen that either Tabs has not be set in Xcode preferences, as preferred indentation method, or that you've copied and pasted some portion of code that was indented with spaces. Please check your indentations for using tabs rather than switching off completely the style check. Best, R

Hello, just FYI: you find information on how to access individual characters from a string in the manual: String Manual Also, one of our examples includes checking the ASCII value of a given character: streamconversion_impl.cpp If your question has been answered, please mark your thread as a question and set it to "solved". best wishes, Sebastian

@s_bach Thanks, I ignored the parameter check and it works now！

The HashMap/HashSet iterator does not provide a it-- (as used in the Iterable::Reverse) but only it++ as you can see in https://developers.maxon.net/docs/Cinema4DCPPSDK/html/classmaxon_1_1_hash_map_1_1_iterator_template.html#ab6054287e6f409207af3fa16e49046ad Cheers, Maxime.

Thank you very much, RIccardo. I will look into it tonight when I get home.

Hi @r_gigante Thanks for the confirmation. Hopefully, it will be possible in the near future. Have a great day ahead!

Hi Rui, thanks for reaching out us. With regard to your question there are a few things to note: /Applications is a folder which requires elevated permission to write in: I recommend to move the SDK in a different location where standard user permission are required; with R21, whether you're using Xcode 10.1 or further revision, it's supposed that you enable the Legacy Build System in the Project Settings: be sure to set it via File -> Project Settings in Xcode. Finally it's recommended, when such building issues are faced, to provide a description of your development environment. Cheers, R

@s_bach Okay I will give it a try , and I will do a open source example project for anyone, who would love to do this with python only for Cinema 4D. lol I been making different types c4d python plugins for 3 years now, from 2015 for my studio I work for and I love making c4d plugins. But this will be my first time using GeUserArea Class to the fullest lol.

hello, To keep you inform, I'm asking the devs and this is taking more time than expected. Sorry for the delay. Cheers, Manuel

Thanks for the update Frank. Looking at your "resolutions" I think that the actions you took were responsible, in the first case, to clean the existing derived data for the R20 project, whilst in the second, to refresh the DerivedData subfolder where the newly re-created R21 project was supposed to store intermediate files. Please keep us updated and for the mean time I'm going to set this thread as solved. Cheers

@m_magalhaes Hello, thank you very much for your inspiration. You've been very helpful. There is no need to overwrite TranslateDescID(), only two macros HandleDescGetVector and HandleDescSetVector can realize my idea. Thanks again! Cheers, Sean

Hi @C4DS thanks for reaching us. I can indeed confirm the issue. I've reached the development team about, I will let you know about any workaround. Cheers, Maxime.

hello, From the execute command you can retrieve the RayCamera using the VolumeData stored inside the VideoPostStruct const RayCamera* cam = vps->vd->GetRayCamera(); You can get the off parameter of the RayCamera that is the offset of the camera (so double it to have the resolution) Using the zoom factor should help you to retrieve the aperture and determine the ray direction. This RayCamera will change depending on where the render is done, (viewport or picture viewer) in the Execute Function : const RayCamera* cam = vps->vd->GetRayCamera(); if (cam == nullptr) return RENDERRESULT::OUTOFMEMORY; ppx_ = cam->off.x; ppy_ = cam->off.y; zoomRatio_ = 1.0 / cam->zoom; in the CalculateRay function maxon::Float newx = x - ppx_; maxon::Float newy = y - ppy_; maxon::Vector focalPoint; // Sets the value of the focal point in local space, the plan is put at the image size * ration in Z axis focalPoint = Vector(newx, -newy, xres_ / zoomRatio_); // go to goal space focalPoint = camMg_ * focalPoint; // remove the camera position so we have a direction focalPoint -= camMg_.off; // set the ray position dst.p = camMg_.off; // set the ray direction dst.v = focalPoint; dst.v.Normalize(); Hope this help a bit. Cheers, Manuel

Ok, made it work now. Thank you so much.

I think we are talking past each other. You can of course build any project any way you like. An then make sure that your plugins link to the build result using the link options defined in projectdefinition.txt. But I think you want to include an already existing (non-plugin) project in the solution created by the Project Tool, right? And I think that is not possible. I guess you could add the project manually to the solution created by the Project Tool.

Thanks Maxime! In the mean time I will cycle through takes, AOVs and Frames manually to get the paths.