Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Maxon Cinema 4D boujou to C4D

  • boujou to C4D

     Greg Brand updated 9 years, 9 months ago 2 Members · 2 Posts
  • Tom Ma

    April 21, 2011 at 5:44 am

    Anyone know of a good tutorial on getting a boujou v.5.0 camera solve to C4D 11.5?

    I see a lot of scattered information online and workarounds as well as some very painful videos.

    I am hoping someone has figured this out and made it clear.

  • Greg Brand

    April 24, 2011 at 6:29 am

    Not sure if this is just adding fuel to the fire, but so far, this was the only workaround that actually did work for me…

    got this off of some forum post, couldn’t really tell you where…

    Hi tomgeraedts,

    This poor C4D export behavior has been an issue for Boujou since they updated from version 4.0 to 4.1. At that update they changed from using a LightWave version 1 file to a LightWave 3 file type. Even though it says it’s a C4D file they use the Lightwave file format. I can’t tell you why they messed it up but I can tell you how to fix it and get a good track into Cinema.

    Here’s how:

    In Boujou

    when exporting C4D type

    Set ‘Start Index’ to 0, not to the ‘default’

    failure to do this can result in the C4D file having the first frame twice, which causes your 3D export to be one frame longer and when placed in your AE comp it will be one frame behind. If you’ve already rendered then just offsetting the layer in AE will fix that issue too.

    After C4D export, open the *.c4d file in any text editor

    Do a search for “Key -3.141593”
    Change it to “Key 0.00000”
    Change the value directly above that from “Key -0.00000” to “Key 0.000000”
    Now do a document wide find and replace:

    Find – “ParentItem 10000001”
    Replace with – “ParentItem 10000002”

    This makes all your null objects children of the proper layer – “reference_points” and not the camera

    Save all changes, and close file.

    Now open the file in C4D and all should be correct.

    Why this bug wasn’t fixed with version 5.0 is beyond me because I know they got complaints about it after the update from 4.0 to 4.1. At least it’s an easy fix once you know what to do. Perhaps it fell through the cracks with the change from 2D3 to Vicon.

    Good luck 3D motion tracking,

    maybe copy paste the post into your search and it should come up with the source

    oh and these vids were a little painful but they did help a lot

    hope that helps

Viewing 1 - 2 of 2 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy