AtomSplitter has been updated to v1.6, available through cmivfx.com
Updates:
- Exports Terragen .tgd scene file format
COMMAND LINE HELP
OSX:
AtomSplitter.app/Contents/MacOS/AtomSplitter <chan file> [out file]
Linux:
AtomSplitter <chan file> [out file]
Windows:
AtomSplitter.exe <chan file> [out file]
=========================================
HELP:
>>> AtomSplitter -h
Usage: AtomSplitter <chan file> [out file]
Options:
-h, --help
show this help message and exit
-o OBJ, --obj=OBJ
Optional nuke-exported pointCloud .obj file
-f FPS, --fps=FPS
Set FPS rate (default 24)
-x WIDTH, --width=WIDTH
Set frame width (default 2048)
-y HEIGHT, --height=HEIGHT
Set frame height (default 1556)
--filmwidth=FILMWIDTH
Set film aperature width in mm (default 24.576)
--filmheight=FILMHEIGHT
Set film aperature height in mm (default 18.672)
-s SCALE, --scale=SCALE
Scale the translation values by this amount
-F FORMAT, --format=FORMAT
Output format (fbx, action, terragen)
AtomSplitter has been updated to v1.5, available through cmivfx.com
Updates:
- Added the ability to convert point cloud data, exported from Nuke as a .obj, to be included in the fbx/action export.
AtomSplitter (chanToFbx) has been updated to v1.2, available through cmivfx.com
Updates:
- Camera rotation order set to ZXY, which is the Nuke camera default
- Fixed a bug where the FocalLength value was not being keyframed properly
- Added a scene scale field, for adjusting the translation values globally.
If you haven’t visited cmiVFX.com before, PLEASE check them out. Chris Maynard does an amazing job rounding up top talent in the industry to create these outstanding visual fx tutorials. The information is always cutting edge.
I had received a mailing list email from cmiVFX, where Chris Maynard was challenging the community to write a tool that could convert a nuke camera .chan file to a functional FBX format. This was apparently meant to compliment the new 3d camera tracker in NukeX. So I decided to take on the challenge.
The tool started out as a command-line python script that would translate the chan files simple column-style output to fbx. But in testing specifically with Flame, Chris found that the fbx simply would not import all the channels properly. Thus, I was asked to integrate a solution by Georges Nakhle for converting the chan to an .action format, which is native to Flame. So with George’s .action code, Chris’s testing with the scaling in Flame, and the rest of my code, we seemed to have all the bases covered in getting the .chan file into a universal format.
Chris asked if I would wrap the tool into a GUI, to allow easier access to the few options the script provides. Using the cmiVFX.com website as a reference, I threw together a nice looking GUI in PyQt. It was fun because I got to really play around with CSS and skinning in PyQt, which is something I never really had to do before. I learned how much of a pain in the ass Palettes are, and how freaking simple the CSS route makes it to control the look or widgets.
Chris released it today: http://www.fxmogul.com/
Currently there is a version for both OSX and Windows. I have been having some issues packaging the code under Linux, but I just need to really sit down and figure it out. The build is kinda larger than I hoped, but thats what I get for distributing PyQt 
.chan To FBX GUI (osx)
