-
Boujou doesn’t work with C4D 11?
Hello, I’m learning Boujou 5 and Cinema 4D R11. What I’ll explain seem to be a problem unsolved in many forums. I still hope someone has a solution out there!
I export a good matchmove from Boujou as a C4D project. Everything correct with frame rate, image size and interlace options etc. (Scale I’m not sure of though).
Opening it in C4D the 3D point cloud is inside the camera (as many described this problem before).
I’ve tried the recommendation of grouping all the track points within the camera into a Null, and placing it outside the Top Null tree. Then I change the new Nulls coordinates to 0. This enhance the situation – now I can view the point cloud through the exported camera – but it doesn’t line up with my matchmoved video I have as reference on a Background object.Not only the scale but the angle seem to be different from my solution in Boujou.
To start with, Is there perhaps a certain scale to always apply when exporting camera from Boujou to C4D?
I promise to share your correct answer to all forums where I’ve encountered this problem!!
Cheers //Erik
-
1 Reply
-
I found a solution to this problem:
And to execute this you need a sw like Komodo to find the keys you’ll change.
https://www.activestate.com/komodo_edit/
or
https://notepad-plus.sourceforge.net/de/site.htmAnd this is what ngambles came up with
. 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,
Cheers
– – – – – – – –But I reckon we still need to group all tracker points which are in the camera, group them and put that null outside the top null tree, and then change its coordinates to 0.
Now this works for me. I hope less artists suffer from this in the future :]
Reply to this Discussion! Login or Sign Up