Hello, as Riccardo has pointed out, AdditionalIncludeDirectories has nothing to do with DLLs. It is used to define search paths for header files. See Additional include directories. It was never valid. Also, looking at the error, the plugin was installed into the C:/Program Files folder. In R21, there is no reason to install plugins there; one can install plugins at any location and just tell Cinema 4D the plugin path. best wishes, Sebastian

Hi Maxime, thanks a lot! Both are valid solutions for me. Very helpful. Cheers

@r_gigante said in Cinema 4D Client R21 Service Creation: Hi @thestraycat, we're still investigating the issue since using nssm is not officially supported on Windows 10. Hi r_gigante, thanks for looking into it, i know it's not simple. I had a look on the NSSM website and it does seem to be supported on windows 10 as per the website: But i totally understand that nssm + c4d isn't. As a temporary workaround, considering that the scope of having it installed as a service it to just have it started at the boot, you might consider to add the TeamRender Client executable among the programs being run at the startup: this can be done be creating an alias to the program - in your case the TR client - inside C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp or, if depending on a local credential, in C:\Users[local user]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. Yeah, as a work around i likely will, but this dosn't real deal with auto starting the application during failure and isn't as resilient as running it as a service, we also run into issues with security banners and have monitoring systems tied into looking specifically for this service etc. Finally, although it doesn't change the overall results - I warmly invite the drop nssm and have a look to sc.exe which is a similar utility provided directly by Microsoft and delivers the same functionalities delivered by the first. Thanks for the suggestion, However sc.exe isn't as flexible as nssm (which is where nssm derived it's name and use case from NSSM -> (Non-Sucking-Service-Manager) and adds a comprehensive set of features to service creation. Being able to use sc.exe would be my preference over running a scheduled task at startup. Do have any information or tips or a working service creation command to get R21 working under sc.exe? Thanks for all your help on this.

@m_adam You are a legend! I've learned a lot about UI in Cinema 4D from this post, thank you very much.

Thank you @m_magalhaes! I needed to open the plugins.sln solution instead of the project file. I feel like I've learned something, but I'm not sure what

@m_adam said in GeUserArea lag in R21 versus R20: Thanks a lot for reporting this kind of issues, it's really relevant for us :) My wife is "jokingly" telling me to send in an invoice for all the effort I am spending in "beta-testing" this official public release. Not so sure if she really means it as a joke, or just being sarcastic ...

Hello, We've talked about this issue in our morning meeting. Contrary to what I've said, it's Core related and not API related. (limitation of cinema4D itself in fact) You have to open a ticket in our support. Tell them you are coming from our forum and it's not related to the API and it's a Core Problem. Sorry for wasting a bit of your time but we need to keep organized. Cheers, Manuel

@kbar @m_adam Thanks for the help lads, the markers were already added thanks to Kent suggestion in his previous reply. Now the only things left are a little "GlTF-fighting", and some more polishing, packaging and testing before updating the plugin with a - hopefully - nice animation support ! I'll let you know when that's done (probably not before 2020 though ). Cheers, Loïc

Hello Sorry for the delay, Christmas time didn't helped. I've opened a bug entry for that issue. I'll be back when i'll have more information. I've added the "Bug report" tag to this thread Cheers, Manuel

Still not I will update you as soon as I have some news. Cheers, Maxime.

Hello Maxime, thanks for that detailed answer. Much appreciated. I see, drawing slows down things massively. (3minutes vs. a few seconds) Bad luck for me then. :) But it still helped me though, I'm now going for another approach. (The GUI part was just for convenience, so everything is fine) Thank you and cheers, Robert

Hello, you find information how to run a plugin from within Visual Studio in the documentation: Development for Microsoft Windows - Running Plugins. best wishes, Sebastian

Thanks, Maxime. No urgency from my side. Just stumbled across it, when actually trying to do something completely different. My best wishes to the entire team.

Hi @dskeithbuck thanks for reaching us. In fact, it's written in the C++ BaseDocument - Selection Manual but I agree maybe a note in the function will be welcome. IN any case, I will add a note for the python doc. Thanks again. Cheers, Maxime.

hello, I forgot to ask, where are you running those commands ? on a script, a dialogbox, a nodedata ? Thanks for your time trying to isolate the problem. Don't hesitate to send us an heavy scene, we can see why the command isn't working. Cheers, Manuel

Hi c4dmac, thanks for following up here. With regard to the issue you've reported you can get fixed by reestablishing the executable bit on the kernel_app file found in the zip archive. To sum it up, upon downloading the project tool archive you have to: remove quarantine xattr -d "com.apple.quarantine" ./cinema4d_r21_project_tool_20190903.zip extract the archive (either via terminal or via finder) unzip -d ./cinema4d_r21_project_tool_20190903 ./cinema4d_r21_project_tool_20190903.zip re-establish the kernel_app executable bit chmod 555 ./cinema4d_r21_project_tool_20190903/kernel_app.app/Contents/MacOS/kernel_app Best, Riccardo

Hello, Really sorry about this issue. Would it be possible to send us a scene and some screenshot maybe to reproduce the behaviour ? That would be really appreciate. I will send that to our devs. You can use our mailbox sdk_support@maxon.net Thanks and cheers, Manuel

hello, I'll mark this thread as solved tomorrow if you have nothing to add. Cheers, Manuel

Hi Daniel, for the time being I see three options: run Cinema with its own menu bar; drag out the menù containing your CommandData in order to make the cogwheel appear use keyboard modifiers: Alt + LMB -> lunches CommandData::Execute() LMB -> lunches CommandData::ExecuteOptionID() Best, Riccardo