Always using the threadIndex, of course :-) Thanks, I'll try that!

Ah, great, thank for checking! Then I don't need to worry about my bmp code :-) Cheers, Frank

Sending another CoreMessage... interesting... I will try that, too. Thank you!

Hi @JuicyJuggles , I apologize for coming late here but luckly you've been already provided in the meanwhile of some good guidance from @PluginStudent and @zipit . Rest assured that the API documentation is, by far, the best place where to look for answers although I can see that, due to huge number of covered topics, it could take time to get used to browse it effectively. Last but not least, if the issue is addressed, don't forget to mark the right post as correct answer or if it's not possible to identify a specific one, to set the whole topic as Solved Cheers, Riccardo

Hello to all @zipit said in GetFontDescription() on Windows and Mac: FONT_FLAGS Thank you i miss flags in https://plugincafe.maxon.net/post/58961

Thanks a lot! That helps :-) Cheers, Frank

Oh man, it really was the missing message. Never thought it would have such weird consequences to forget that. Thanks guys!

Thank you! That does it exactly!

@r_gigante @kbar Thanks for the infomation. I assumed that was the case and it makes sense, I'm just reluctant to stop supporting older versions of Cinema but it might be time. Riccardo, I think I was using the incorrect version of osX or XCode, not sure which, but using your codesign worked when I moved onto a later version of both and it is correctly signing my R20 compiles. Thanks both of you for all of the help and clarifying of notarization. Dan

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

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.

OK, thank you!

Ok, thanks @r_gigante... I'll keeping going with the workaround.

Hey zipit, thanks for the answer! Exactly what I needed! Best Regards, Florian

Hello Sebastian, thanks for this quick response! I dind't know about this. But this solved my issue! Best Regards, Florian

Thank you again, @m_adam! I ended up using the C++ method, and it worked like a charm. Also, I appreciate the link to the *args and **kwargs at pythontips.com. It was very helpful to understand those concepts. I do have (many) more questions, but I'll start new posts since they're not related to this topic. My Best, Eric

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.

Hi Roger, thanks for following up. Although I've run a few tests here trying to mix-up STL data-types and Cinema API ones, I wasn't able to reproduce the issue on Xcode 9.4.1 and Cinema R20.057. That said, where possible, we encourage sticking to Cinema 4D API related data-types in order to grant better performance and superior stability. In your specific case I would go for maxon::BaseArray rather than std::vector and I would have switched from std::vector<std::string> to maxon::BaseArray<maxon::String> Would this be an option? Would you like to share a portion of code to reproduce the issue? Best, Riccardo