Search

Forum


Removing support for Cinema 4D
You are not authorized to post a reply.
Staff Member
Posts:2100 Staff Member

--
2025-02-11 20:56

    We are planning to remove the support for Cinema 4D import in the near future and would like to hear from you how that would impact your workflows.

    The reason for removing Cinema 4D import is that it is becoming cumbersome to maintain and we're not very happy with the state it is in. Key shortcomings include lack of PBR material support, only supporting flat and UVW texture mapping and no support for animations. Given that Cinema 4D now has glTF export we would rather spend the development time on more relevant features than revising the Cinema 4D import.

    We have tested Cinema 4D's glTF export to the best of our ability. It appears to have a few shortcomings, but on the whole we're confident that it represents a better and more capable workflow than importing Cinema 4D files directly into Capture.

    If you are among the users that still use the Cinema 4D import in Capture we would like to ask you to please try using glTF instead and lettings us know if this leads to any problems on your side.

    Technical Director
    Capture Visualisation AB
    Veteran Member
    Posts:346 Veteran Member

    --
    2025-02-13 15:53

    Thanks for sharing this consideration on the forum, I personally do not get many drawings in this format. As long as I can use Blender as an intermediate I wouldn't put too much effort into supporting this file format.

    There are more and more set designs coming in in the Rhino native file format. Maybe it is possible to support this instead?

    Floriaan Ganzevoort
    Lighting Designer - Theatermachine
    New Member
    Posts:1 New Member

    --
    2025-03-07 09:23

    Would love to keep it, as my main 3D app is C4D.

    It will be a hassle otherwise.

    Thanks, robert

    Staff Member
    Posts:2100 Staff Member

    --
    2025-03-07 09:25

    Thanks for your feedback Robert. Have you tried going to Capture via glTF/GLB? It should have benefits, especially with regar to materials. And you wouldn't have to save your C4D files with polygon cache any more.

    Technical Director
    Capture Visualisation AB
    Veteran Member
    Posts:346 Veteran Member

    --
    2025-03-07 10:05

    To clarify, if I understand correctly, Capture will remove the support just for the file format, not the exports that can be made with Cinema 4D.

    Floriaan Ganzevoort
    Lighting Designer - Theatermachine
    Staff Member
    Posts:2100 Staff Member

    --
    2025-03-07 10:42

    Indeed, we are looking to remove support for the C4D file format.

    Technical Director
    Capture Visualisation AB
    New Member
    Posts:1 New Member

    --
    2025-04-10 17:16

    The import of a Cinema 4D file is very important for my workflow. I don't even work directly with c4d.
    I design my models in Vectorworks and also mapped my textures there. For simple straight shapes, it is sufficient to export them with MVR. But if I have rounded shapes or surfaces with several sides textured, I have to use the export as C4d, because then my textures are mapped perfectly in the correct position and not just blank white. This is very helpful and saves me a lot of work and time.  Do you have a solution for this problem?  If you need more information, please let me know.
    Best regards from Germany Martin.

    Staff Member
    Posts:2100 Staff Member

    --
    2025-04-11 15:48

    Our suggested solution is exporting to glTF or GLB instead!

    Technical Director
    Capture Visualisation AB
    You are not authorized to post a reply.