Hi Manuel, what you say rings a bell. I was sure it was because the vector hadn't allocated anything yet. Global possibly wasn't the best way admittedly, it just started like that for convenience. But it ended up being a bit complex, there's a lot of things accessing it, so I didn't want to change it (for now). @m_magalhaes said in Setting up global plugin structs: create a pointer and in pluginstart and pluginend take care of assign memory and free it hadn't thought of that. Seems to work - I'll go with that! Thanks WP.

Ok, success. Copying the plugin folder from pc to mac was the issue!

@kbar said in Decoupling source from SDK project: Since Maxon also updates the ProjectTool when a new version of C4D comes out and it may have new flags or optimazations and changes to the project structure for XCode and Visual Studio. From what I can tell it's pretty stable, also I don't mind what someone else thinks my compiler optimisation flags should be. Maintaining your own CMake version going forward for R20, R21, S22, RXX etc... would be a massive pain and just slow you down. Not as painful as you think it might be, also not as slow. Whatever floats your boat. :)

Brah... Third time spent fighting with stupid typos! : @PluginStudent @zipit @r_gigante many thanks! I didn't assume you are using the same system inside the program and had no thought to take a look there! Seems adding the "," helped it. And, as I see, you must enumerate all the elements in your .h file, but though you can leave id blank. Thank you! %\

Just to point out, I already answered & posted a full sample scene in this thread: https://www.c4dcafe.com/ipb/forums/topic/109504-python-vertex-map/ plus a detailed explanation on how vertex map calculation works in a free post on my Patreon: https://www.patreon.com/posts/script-club-1-07-34384586 (Just so we don't get work duplicated.)

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

@m_adam said in How to create splitted dialog window: But in any case, here it's how it works. Thank you very much, Maxime! Great example!

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.

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

Thank you so much, all The Cinema 4D on the other computer was not updated to R19.068, I updated the c4d app and I made new test, it seem to work normally. To be sure, I will retest it again on a third computer. I have an error when I try to debugging plugins, I will create new topic concerning this error. Thanks again, and have a great day.

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, We need to ask if you are compiling the SDK, your own project, etc. Different question, you should open a different thread :) It will help other people to find the thread. Cheers, Manuel

Hi Root Star, thanks for reaching out us. With regard to the IDE version, we highly suggest sticking the compatibility table reported in our documentation. Visual Studio 2019 is not supported by R20 and it's likely not to be officially supported also on R21. With regard to .hxx files, these are generated by our source processor when the building process is initiated and it's highly discouraged to change or get rid of them during the building process. The issues you're facing are highly related to the fact that the solution/project file(s) built by the projecttool (when kernel_app_64bit.exe g_updateProject=<your path to Cinema SDK> is executed) are not 100% compatible with VS2019 resulting in building tool-chain flaws. Best, Riccardo

hello, if you can give us feedback that would be awesome. Cheers Manuel

@r_gigante said in Specify additional directories for DLL dependencies: If I end up with some workaround I'll come back here but for the time being I consider it solved. OK, thanks for the info! /Filip

Thanks Sebastian, I will try that! /Filip

Thanks Sebastian! Looking forward for a fix. ;) Meanwhile I'll take care of your recommendation. Best, Robert

HI Andreas, no worries, this question was not exclusively targeted at Maxon, the opposite is the case. I was hoping for some information by other users here, like @kbar or even @m_adam (back in the days Maxime was not associated with Maxon. ;)) Meanwhile, I'm going to build a toolchain and see what works for me. I'll report back here if I have something to show. That may help someone else.

Here's an older blog post about VS property sheets. Still for VS2010, but the principle is still the same. Sharing project properties in Visual C++