6

Cinema 4D Engine

Here at Cluster Studio we are working on an engine for Cinema 4D. Is this something that would be interesting to you? Let us know your thoughts by adding comments or dialogue to this post (you need to be signed in to do that!).

7 comments

  • 0
    Avatar
    Sebastian Kral

    Hi,

    we would love to see this in action. How far along are you guys?

    Best,

    Sebastian

  • 0
    Avatar
    Armando Ricalde

    Hi Sebastian,

    We haven't had time to continue working on this since September (so many things we're working on), but it's on our schedule to continue next week, along with the AE one.

    Cheers,
    Doc

  • 0
    Avatar
    Sebastian Kral

    Hi Armando,

    how are you? Hope everything is going well at Cluster. Did you have time to work on the two engines, i.e. Cinema 4D and After Effects?
    I would love to see those out in the wild.

    Cheers,

    Sebastian

  • 0
    Avatar
    Armando Ricalde

    Unfortunately not, although we've solved the sockets problem with the AE engine so with one more week of work a basic engine with saving and snapshoting functionality could be released.

    The problem with publishing goes beyond the software mechanics itself, but in the way MoGraph artists like to work, is not like Nuke where the work is shot based, so we are still discussing with the artists how to deal with this without modifying (too much) the way they work .

    Cheers,
    Doc

  • 0
    Avatar
    Sebastian Kral

    That sounds great, I know what you are talking about, we had some talks with our artists and their workflow as well.
    What about the Cinema Engine? I have to admit I am almost more interested in it than the AE one.

    Cheers,

    Sebastian

  • 0
    Avatar
    Rodrigo Rodriguez

    Hi Sebastian!

    I'm glad to hear about your interest in the cinema 4d engine! Let me do some comments.
    The engine still has some bugs, the biggest one occurs while restarting the engine. Mainly, because the cinema 4d's plugins have to be a pyp file type, but those files doesn't play well with all the other python code. I think we have to change our approach on registering the plugin. This problem doesn't allow us from changing the work area.
    Last december, I sent a pull request to the shotgun team looking for some feedback. They haven't check it yet, maybe becacuse of their busy schedules.
    I was testing it this week and even fixed some other problems. I'll be testing the common apps these days to see if everything goes well, so please tell me if you are especially interested in some feature. We would be glad to share it with you in exchange for some ideas or help to improve it.

    Regards!
    Rodrigo

  • 0
    Avatar
    Chris Jubb

    Hi glad to see you've started to look at this. I'm investigating it further.

    Am I correct in saying you need to provide some code specific to the application (Cinema 4D in this case) that interacts with Tank? For example Tank knows how to display the UI (provided you can startup pyside from the application). You have to write the part that deals with opening scenes, referencing objects in etc.

    Thinking about this in layers, does it look like this:

    Qt UI

    pyside

    Tank       <----> shotgun servers

    Cinema 4D

     

    I see that the Maya and 3DS Max integrations are actually very little code (looking at them on github).

     

    It sounds like you've just tried the python api for Cinema 4D. What about the C++ one too - could this get around any of the issues you're having?

Please sign in to leave a comment.