Hi Riccardo!

The successfully building solution still gives me these errors:

They stem from the R21 sdk frameworks, so I assumed they are not stuff that I have to fix necessarily. I interpreted the icon on the left as a "syntax error", but maybe it means something else.

Hey Frank!

That totally fixed the errors I got. (At least like you said the second part).
I can now successfully build the solution.
Thank you!

I still kinda would like to know if the other warnings that pop up are a serious issue or if they can be ignored... The build doesn't fail anymore, so it sees not to be too bad.

Hi there!

I am trying to recompile an older Plugin to R21 and am having trouble getting it to build correctly.
My C++ and VisualStudio knowledge is very limited so I might just be making some basic mistakes.
I got the R21 sdk and replaced the demo plugins with the old R20 one.
I am using VS2019, but I switched the Platform Toolkit for the plugin and the frameworks to 2017. (Using VS2019 works fine to compile the R20 plugin with the 2015 toolkit)
When building I get a bunch of syntax errors for the frameworks like:

Error (active)	E0757	member "maxon::ClassInterface::REF" is not a type name

And I get this error for several places where a global array is modified like myBaseArray.Append(plugin_id);:

C4834 discarding return value of function with 'nodiscard' attribute

I have searched around for a while but I don't know how to fix this. Do I have to modify the code, or is this an issue stemming from an incorrect setup of the VisualStudio project?

After a LOT of testing around I finally found the culprit.
The header file was encoded UTF-8 with BOM. I finally figured it out after noticing that two versions of the header file that worked or didn't work had a 3 byte difference in file size. No idea how that snuck in there, but now it finally works.
Also now it makes sense that the error was pointing to line 1.

Hi everyone!

I am currently in the process of moving a plugin into a new environment and starting a very reduced version of it up gives me an error on startup:

Error reading resource
file
'[PLUGINDIR]\res\c4d_symbols.h'
Line 1

I am still on R20, in case this is relevant.

I am a little stumped as to what this error is trying to tell me, since the first line of the file are just comments and even if I only put a dummy element in there the error appears (even though the plugin then breaks).
I am confused as to why the plugin seems to run fine after I click ok, since the file contains the pluginIDs necessary to register the plugins. How do I get rid of that error message?

I don't know if this is related at all, but I also always get this in the maxon console:

ZeroConf error: Couldn't get bonjour version [sys_bonjour.cpp(1726)]
Warning: Team Render is deactivated in -parallel mode
[...]
ZeroConf error: Couldn't get bonjour version [sys_bonjour.cpp(1726)]
ZeroConf error: nullptr
CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]
CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]
Optout defined by Installer / Updater.

It's probably not related, but in case it is I thought I'd mention it.

Thanks Maxime!

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

Hi!

Is there a way to output all renderpaths? Perhaps via the token system?

I tried setting up the token system to get to the render paths, but it seems to me, like it is basically the same as building your own string replacement. You still have to manually input all the relevant stuff in to the dictionary, am I wrong?
If only something like $take is used that might be handy, but if you are e.g. trying to output all paths that have tokens like $take, $pass and $frame and you have to cycle through them manually changing the values in the dictionary then that's not really more practical than just searching for the token string and replacing it.

Am I missing some great functionality of the token system that would allow me to just print all the render output paths?

Thanks!

Thanks! I'll try that.

Hi Maxime!
Thanks for your answer.
Is there a way to directly get that variable in Cinema, or is it basically just modifying the string into something that isn't recognized by Cinema? For me it looks like I now have to seperate the string by finding the '=' or something like that. Is that what I have to do?

Hi!

I want to do pretty much what was proposed in this thread. That is passing a script via sys.argv.
It seems that Cinema is trying to load the file after I'm done with my stuff and since it doesn't recognize the filetype I get an error "Unrecognized file format!".
I tried consuming the path with sys.argv.remove(path), but that didn't really seem to do anything.
How can I prevent Cinema from attempting to open the path?

Thanks!