Hi Rui, thanks for reaching out us.

With regard to the mentioned issued, it's pretty clear looking at the outputted line in the building log that you were trying to feed some function with a data-type missing the ToString() method which is usually supposed to "convert" the data in a convenient maxon::String representation.
I warmly recommend to have a look at the Conversion section in the maxon::String Manual.

Last but not least this change was already requested to adapt code from R19 to R20 and not from R20 to R21.

Best, R

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

Hi wickedP, thanks for reaching out us.

With regard to your request, the solution is pretty easy: using the GetRotationMatrixX() and GetRotationMatrixY() you get two transformation matrixes that in the end should be multiplied by your camera transformation matrix.

In Python it looks like

    # get the cam
    cam = doc.GetActiveObject()

    #get the ray (it's just another camera with 0.2 aperture)
    ray = cam.GetNext()

    # create the yaw and pitch matrixes
    pitchMatrix = c4d.utils.MatrixRotX(c4d.utils.DegToRad(3.7))
    yawMatrix = c4d.utils.MatrixRotY(c4d.utils.DegToRad(4.5))

    # combine them and set the ray tranformation matrix
    ray.SetMg(pitchMatrix * yawMatrix * cam.GetMg())
    
    c4d.EventAdd()

Hi Rui, thanks for reaching out us.

With regard to the issue you mention, it's caused by the fact that the iferr_return statement requires the tmperr_ies identifier to exist. This is usually managed by adding the iferr_scope; at the beginning of the code fragment where error handling is involved (usually at the very top of the function/method implementation).

Error handling is properly explained in this manual but mostly important have a look at the Error Scope section.

Best, Riccardo

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

Hi bentraje, thanks for reaching out us.

With regard to your request, I confirm that at the moment Python API doesn't support nodes, making not possible to execute any sort of operation on nodes or regarding nodes. Rest assured that this is on our radar and that, based on product development prioritisation, might be added at a certain time in the future.

Best,

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

Thanks Rui for following up.

Since kernel_app.app is just a folder on macOS, can you also check what permission has ./kernel_app.app/Contents/MacOS/kernel_app which is the real executable?

In my case I see

$ ls -l ./kernel_app.app/Contents/MacOS/kernel_app 
-rwxr-xr-x  1 riccardogigante  staff  3998432 Feb  5  2019 ./kernel_app.app/Contents/MacOS/kernel_app

Finally please have a look at this thread.

Hi mfersaoui, thanks for reaching out us.

With regard to your question, whilst it's actually possible to query for the layers belonging to a certain Layer Shader, it's not possible to programmatically add new layers with the current API implementation.

Here you can find an old discussion on the argument.

Best, Riccardo

Hi Frank, thanks for reaching out us.

In order to be of some help I need to know a bit more:

• you refer about a generic crash even involving the cinema4dsdk: can you be more precise on when it crash? At Cinema start-up? At plugin registration? At Cinema shutdown?
• looks like you have provided a portion of the crash log: can you also provide the Cinema crash log as well?
• are you aware of any unexpected update of your tool chain? What are the Xcode versions your're currently using? What is the os version you're using to build your plugins?
• you mentioned about Deleting and freshly cloning the repository (to eliminate all chances of unwanted changes): did you tried to Clean the project, before building again?

Finally, waiting for your feedback, I recommend to delete the Derived Data that Xcode generates in the folder specified in the "File -> Project Settings".

Best, Riccardo