I have a plugin that has a couple of commands and one Tag. If I comment out one of my commands then the Tag appears in the root of the main right click menu for the selected object in the OM. But if I have both my commands and the tag then the Tag now appears under it's own sub menu in the right click menu.

It seems that C4D is just counting the number of things that are registered, and if greater or equal to 3 then it automatically adds the submenu to the right click menu for tags. Regardless of what is actually registered. I would expect for this submenu to only appear when there are multiple Tags registered, but this doesn't seem to be the case.

Is this correct? Is there some way to force tags to be in the main right click menu. Feels silly to just have a menu with just one item under it that has exactly the same name.

That should work fine for my purposes. I just need to pass in the file to get encrypted and have it write the result to the same directory. But then C4D should quit afterwards. Would be amazing if this was possible.

If this was added to S22 ( or S23 ) then would the resulting pypv files also load in R20 and R21?

I am going to bump this also.This function should be able to be called by command line. I would like to do this via my build system. By calling the cinema4d.exe, or c4dpy, with the python plugin path.

No it's not illegal to make a plugin that does something that another plugin does. It would be illegal if you took their plugin and used anything from it in yours (res files, strings, code etc...).

I didn't even know that plugin existed. Years ago I made my own one called Draw Objects. I haven't updated the feature set since I made it, but everything I see in that primitives plugin are all features I have messed around with in many of my tools.

Snapping and drawing onto other objects has even been implemented and is part of the C4D sculpting sdk examples.

One problem is that perhaps the developer hasn't kept up with development since R14. So they are probably not going to update it to S22 anytime soon. If you want the features you will probably just have to develop it yourself.

My advise is to just jump on in and get started. Make a tool that can draw a plane and then go from there. Your own ideas will very quickly expand way beyond what you see in any tool that inspired you in the first place and in the end it will do what you want.

Good luck!

Thanks @zipit @m_adam.

I will take a look at c4dpy and your link also Maxime.

Cheers,
Kent

Is there a flag that can be passed to Cinema 4D via the Commandline to retrieve its preferences folder?

Just looking at options for creating an installer that installs directly to the users prefs/plugins folder on both windows and osx.

Thanks!

There is stricter error checking now. You will need to do the following...

while (file->ReadChar(&ch)) {
        iferr(text.AppendChar(ch)) {
            return; //Handle the error
     }
}

Those steps look correct. But it should be noted that you should be using the correct version of Cinema 4D to compile for R20 (VS 2015) and R21 (VS 2017). It might work using VS 2019, if you change the Standard Language as mentioned. But it may still link to newer dlls which won't be installed on users machines. So using the correct VS version will ensure the dlls required will already be installed by the C4D installer. And the Support team here can't provide you any support if you are using the wrong version of VS.

https://developers.maxon.net/?page_id=1108

Hi @r_gigante ,

Thanks for the code. I have it working now in R20. The issue seems to be that for R20 the interface file needs to be part of a framework. This is not the case for R21. In R21 I could include all the code locally within my plugin and it worked fine, but for R20 it needed to be extracted out to the frameworks folder as shown in your example. I didn't need to create a new module (ie its own xdl64) since I can register the framework from within my main plugin itself. So I have a working solution now.

This is another reason why I would really like to have the ability to include our own framework folder in the projectdefinition.txt file. Mixing it in with the regular SDK ones is really not ideal.

Thanks again for the example code.

Cheers,
Kent