Hello, I don't have a Cinmea 4D R14 version so I can't test that case. But in R20 some symbols have changed. E.g. c4d.DESCFLAGS_SET_0 was changed to c4d.DESCFLAGS_SET_NONE. Similarly, c4d.USERAREAFLAGS_NONE was c4d.USERAREA_0. best wishes, Sebastian

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

@Cairyn Thanks again for the detailed explanation. I'll put this to rest. At least for now I know the limitation and the commands to avoid. @s_bach Thanks for the confirmation. Have a great day ahead!

Hi @Rage, I think this question is related to the another topic you posted, so I will not explain again how import/export works in CInema 4D. In your case, you have to use FBXEXPORT_TRIANGULATE and not FBXEXPORT_TRIANGULATE_GEOMETRY. And yes you are right, currently, no symbol is defined for the FBX exporter so you have to use 1026370 directly. Cheers, Maxime.

Hi @rage, you first have to configure the exporter plugin then Load the document/ Merge it. Cinema 4D will automatically use the settings you defined in the plugin. You can find examples of the procedure in our github repository. Finally, symbols for supported exporter/importer are exposed in this page of the Python documentation. Unfortunately, there is no area describing each symbol for each exporter in the python documentation, but you can find them using the search engine in the C++ documentation. (I linked you the C++ symbols of OBJ, import) If you have any questions, please let me know. Cheers, Maxime.

Probably not that helpful but there is an existing script for the C4D OBJ Sequence Exporter https://richh.co/c4d-native-obj-sequence-export-no-plugins/

Thanks for the confirmation @a_block Will hope for the best in the future regarding sublime Have a great a day ahead!

@C4DS Works as expected. Phew! I never knew it is this complicated. Thanks again. Have a great day ahead!

Hi, @merkvilson thanks for pointing this function is private and have no use case since its return the type of a c4d.gui.Gadget which is only used internally. Cheers, Maxime.

Gotcha. Thanks for clarification!

@mp5gosu Thanks for the response and for the link regarding recursive and nonrecusive distinction, but I think the recursive version is shorter to write @Cairyn Thanks for the revised script. Works as expected. To be honest, I really do not know Python in C4D per se. I'm just winging it. Hahaha. So, thanks for the explanation!

Thanks, Andreas! This is a really interesting approach.

Hi @Fransua welcome in the plugincafe community. Do not worry since it's your first post but please read and follow these rules (I've setup your post correctly) How to Post Questions especially the tagging part. Q&A New Functionality. Unfortunately, a complete list is not available for the moment. But if you are looking only for object there is this page Object Types and Fields Object Types which refer to all symbols available to describe an object. To know a specific object id, you can drag and drop this object/element to the console, for more information see Python Console, Scene Elements. Finally, you can also retrieve for the full list of id by their type with c4d.plugins.FilterPluginList Cheers, Maxime.

Thank you for your answer. That was exactly what I was looking for. John Thomas

Hello @r_gigante Thank you for your time and answer. I will try the other way then. Best, Ogers

@a_block Hi Andreas, Thanks for your help and you are never too late! That actually makes more sense. Unfortunately I can't seem to replicate the issue again on my machine, as it seems that it's been working for all my updates. I will have a look on one of my team machines when released and see if that could be the problem. Thank you again!

Thank you Maxime. My current solution looks pretty similar to yours and works . Implementing an own gadget is of course out of scope - I don't even get paid for that.

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++

Thanks Sebastian. I did not realize it was a generator. Couldn't find it mentioned in the docs. However I was searching for VolumeLoader in the docs and on here, and I think the official docs searching system doesn't always return the results. Anyway, all good now. Thanks again.

Thanks, Andreas! I was looking for interface_icons_2x for a while