Hey @mikeudin,

we are aware and working on it. Meanwhile this applies:

Getting Started with the Cinema 4D C++ SDK on macOS: Prerequisites:

Xcode 13 is incompatible with more recent versions of macOS such as Ventura and Sonoma. But you must still use Xcode 13 to build the more recent Cinema 4D C++ SDKs for macOS, as Xcode 13 is the last release that supports the legacy build system. We strongly recommend using macOS Monterey to run Xcode 13 as the circulating hack of reaching into the Xcode 13 package to directly invoke the Xcode app is more and more error prone the further you update macOS. Attempting to build the Cinema 4D SDK with Xcode 14 or later will result in build errors. We are working on supporting the standard build system of Xcode.

See also the forum thread Development requirements for C4D 2025.

Cheers,
Ferdinand

Hey @no1astrologer,

this will be fixed in the next release.

Hey,

so, I fixed this now, in the sense that the TOC is now back in these classic API type and module pages.

c2f5944c-90e4-49f9-a194-44f7be96b281-image.png

I renamed the old a bit wordily named "Functions Signatures" and "Functions Documentation" to Overview and Functions (or Methods for classes) . Opposed to the old pre 2024.3 TOCs (which were completely broken in many ways), these categories now also show up in the TOC:

adcc5c03-d5fd-4f97-b206-7d69cef2d81e-image.png
bc7bac63-8959-487a-8aa7-81e729fcc92a-image.png

The old Types and Inheritance section has been merged into root element as I do not see a good reason why it should appear in the middle of the page. The obvious thing would be to now add links to the individual elements on a page, so that you can quick-jump to a particular function. But that turned out to be not so easy with the mess we made there before and stubborn docutils. As evident by the C4DAtom example and other cases our TOC trees are very broken in this part of the docs and I now already almost spent two days with fixing things to this state.

This will be shipped in the current state with the next release of Cinema 4D. When I have some time to waste, I will try to add the function links.

⚠ The manual and maxon API TOCs are unaffected by this, they continue to work as intended. The classic API does its own thing here (as always 😄 ) which why this is such a mess.

Cheers,
Ferdinand

@ferdinand Thank you! Yes, hopefully Google will index the new site soon.

Dear Community,

as always, things took me a little bit longer than expected, but links on the forum should be patched now. All postings should correctly display attachments and references to downloads and the docs should also correctly resolve again.

I also scanned the forum and removed or translated URLs. This concerns for once legacy ASP.net forum URLs which have been replaced with the matching NodeBB URL (to be found in the Legacy Forum, e.g., here). Removed have also been a substantial amount of non-resolving URLs. Most relevant are here links into our old developers.maxon.net platform, such as download and posting links. They cannot be mapped to new content hand therefore had to be removed. For such postings you find then find [URL-REMOVED] markup in the postings to signal where links have been removed. Find an example here.

Finally, I have also replaced all legacy documentation links ( /docs/Cinema4DCPPSDK/... and /docs/Cinema4DPythonSDK/...) from before we distinguished between versions in our online docs. While legacy links will continue to resolve, e.g., link, you should always use the new URL scheme.

There will be no further maintenance work on the forum in the near future.

Cheers,
Ferdinand