Hi @m_adam, following your typescript example it worked now to connect! Thank you very much for your help 🙂

Merry Christmas and a Happy New Year!

I would heavily recommend using the extension, as it will automatically curate the paths for you. I.e., when you use the extension and connect to a Cinema 4D instance, it will make sure that the dummy modules of that Cinema 4D version are on the search paths.

But when you really do not want to use it, you can also just edit your config so that the dummy module paths are discoverable for auto complete and the linter.
2a76cd6c-35aa-451f-82db-02b03694e72d-image.png

What you will need in any case, is the Python and Pylance extension for VS Code, as they are the extensions which make use of these settings. When you install the connector, they will be installed automatically as a dependency.

0b5d77af-5f23-4203-9a0a-276b8eafc62e-image.png

Cheers,
Ferdinand

Thank you, @f8bet00net.
Yeah, I remember I had gone though this with you before. But recently, we found there is a way to customize TreatSpecificWarningsAsErrors settings in projectdefinition.txt for MSVCBase.props for windows VS projects.
So I asked this question again just to double confirm if we could do similar things for MacOS XCode settings.
Thanks for confirming this is not possible on MacOS.

Good to hear. When you want to know more about how to expose libraries, I would recommend reading the Python Libraries Manual, as there are quite a few differences to a vanilla CPython. The guide is a little bit dated, I haven't updated it yet to the pip support Maxime is adding, and I also did not yet cover there mxutils.LocalImportPath.

Cheers,
ferdinand

Hey @spedler,

Thank you for reaching out to us and for pointing out that issue. We are aware that our code signing documentation requires an overhaul. This not only means updating the rather dated MacOS guide, but also providing a guide for Windows since code signing also has become more and more important under Windows. And although not yet as restrictive as MacOS, the Microsoft Secure Future Initative is pointing to a future of execution policies on Windows similar in strictness to the one's found on MacOS.

Cinema 4D itself is evolving in a similar fashion, as recently lined out in About the necessity of code signing plugins. We have currently no immediate plans to make code signing for all plugins technically mandatory, Cinema 4D is currently still loading unsigned binaries, but we strongly encourage users to (properly) sign their plugins, especially under MacOS. What has changed since Cinema 4D 2024, is that Cinema 4D will not load binaries with an expired certificate anymore (note that an expired certificate is not the same as an expired license, see the linked posting for details).

I currently plan to update the guides in 2025 Q1 or Q2. It was actually already planned for 2024 but I never got to it. But just before I left for vacation I at least already requested the necessary licenses to further research and write the new guides 😉 But this is neither my current or next task. However, given the relative closeness of the task of overhauling the code signing documentation, I will probably not 'monkey patch' the current documentation.

When there are any questions regarding code signing plugins for Cinema 4D on either Windows or MacOS, please do not hesitate to ask or discuss them here.

Cheers,
Ferdinand

PS: I am still on vacation, so I will likely not respond to any follow-ups until I am back.

Hi @César-Vonc ,

Cinema 4D uses OS clipboard to some extent, namely as you can see from the CLIPBOARDTYPE enum there's text and image clipboard options. For other Copy&Paste functions the built-in clipboard system is used, hence the OS clipboard stays untouched.

Cheers,
Ilia

Dear development community,

just as a clarification, as I was not very clear about that above. We are working on a solution for the build system for the SDK (as I hinted at before in other postings). But for 2025 we will stay with this a bit cumbersome legacy build system solution for macOS.

Please excuse the inconvenience but there are a few more moving parts in the background than it is obvious from the outside (to fix this, we must move away from the project tool).

Cheers,
Ferdinand

Hey everyone,

I fixed the issue, the legacy SDKs now have again the correct line endings, the downloads have been updated.

Cheers,
Ferdinand

@ferdinand Great thanks!

Thanks for the info!

Dan

Hey @lasselauch,

We are not able to reproduce this crash on an Intel, M1, or M3 MacBook with 2024.4.0. Please provide and submit a crash report when this is still a problem for you. I would also recommend reinstalling Cinema 4D to rule out that your installation was damaged.

Cheers,
Ferdinand

Hi @mikeudin ,

To me it sounds pretty much like this issue here: issue with inserting fieldlayers in r2024, particularly after I couldn't reproduce this issue with the internally available next version of cinema.

Cheers,
Ilia

Hi sorry for not answering this topic earlier, I finally found some time to investigate and sadly there is nothing you can do in your side, this memory leak is coming from the Illustrator Importer and can be big, since all the points and tangents of the file are leaking. A fix will be available in the next update.

Thanks for the report !
Cheers,
Maxime.

Hello @veenamandhan,

Welcome to the Maxon developers forum and its community, it is great to have you with us!

Getting Started

Before creating your next postings, we would recommend making yourself accustomed with our forum and support procedures. You did not do anything wrong, we point all new users to these rules.

Forum Overview: Provides a broad overview of the fundamental structure and rules of this forum, such as the purpose of the different sub-forums or the fact that we will ban users who engage in hate speech or harassment. Support Procedures: Provides a more in detail overview of how we provide technical support for APIs here. This topic will tell you how to ask good questions and limits of our technical support. Forum Features: Provides an overview of the technical features of this forum, such as Markdown markup or file uploads.

It is strongly recommended to read the first two topics carefully, especially the section Support Procedures: Asking Questions.

About your First Question

First of all, you first posting is a violation of our "one subject per topic" rule. When you have questions about multiple subjects, you must open multiple postings. For details on this subject, please see Support Procedures: Asking Questions.

We usually cut newcomers some slack in this regard as they cannot know our rules in advance and one usually also has more questions than there are atoms in the universe when starting out with a new API. But we must ask you to conform to this rule in future postings.

Regarding your questions:

It depends a bit on what you would expect from an "audio input field", but generally, yes. We have the FilenameCusstomGui and the SoundEffectorCustomGui. The former is for letting the user select arbitrary files, the latter is a specialized GUI for sound files (but also hooks into tracks). In the end this also depends a bit on what plugin type you want to use, because not all plugins use the same GUI paradigms.
352630af-9dba-4e39-ac71-5f40da6d26ab-image.png. Yes, that is possible. You are however bound by the threading restrictions here as inserting tracks (your "audio") means modifying the scene graph. Which in turn means that you cannot do this in any of the major payload methods of scene element plugins like ObjectData::GetVirtualObjects, or TagData::Execute as they all run off-main thread. You can do this with all plugin types but for scene elements (everything derived from NodeData) you must usually be a bit more careful, as a lot of methods are there being called in parallel. That is a very ambiguous question. I am not really sure what you mean with "custom boxes like asset boxes", but in general you can implement any kind of custom GUI you want in C++. It again depends a bit on the plugin type you use. For dialogs, custom GUIs are realized by GeUserArea, for descriptions, i.e., stuff in the Attribute Manager, you will have to implement a CustomGuiData (and possibly a custom data type). The GUI paradigms manual is here also entry point for this subject.

In general I would recommend opening a thread for each of these subjects, as this thread will become otherwise very convoluted and hard to read and understand for both you and future readers. Before you do that, I would however recommend that you start a thread asking for help which plugin type to choose, while briefly explaining what you want to do.

Cheers,
Ferdinand

Hey @InterfaceGuy,

you did nothing wrong here, that was an understandable mistake and we do not mind moving topics from time to time. But at the same time we still have to uphold our rules.

Cheers,
Ferdinand

Thank you, @ferdinand

@ferdinand Thank very much! i'll check what can i do. 🤔

Hey @Cankar001,

thank you for reaching out to us. It is great to hear that you found your solution! But I have troubles understanding all details of the rest of your question. However:

PluginStart ist just an alias for the plugin message C4DPL_INIT. A Cinema 4D instance has various stages in its startup and teardown sequence, as expressed by the plugin messages C4DPL_MESSAGES (see also: Plugin Messages). Through out the startup and teardown of Cinema 4D not all systems are available, as binaries/modules are loaded and unloaded and the systems associated with them are being pulled up and torn down. In the end it depends a bit on what you tried to do concretely, but generally speaking, it could very well be that something is not yet "up" when C4DPL_INIT is emitted. But in general, most modules, registries, etc. should be accessible at this point (plugins are loaded after the core and unloaded before the core).

To get here a more precise answer, I would recommend opening a new topic with concrete code.

Cheers,
Ferdinand

Thank you, @ferdinand. I modified sourceprocessor.py for now, and it works.

Hey @BruceC,

you are not expected to. In fact you cannot delete any topic as a user here once it is older than 60 minutes (no replies or not). Postings, a reply in a topic, can be deleted without restrictions. But deleting is not really deleting in NodeBB anyway, true deletion, NodeBB calls its purging, is not available for users at all.

Long story short: We do not want users to delete topics as they tend to delete valuable information for others with that, even when they consider the topic failed or obsolete.

Cheers,
Ferdinand