Good idea Tim. I'm submitting that request to Adobe now.
On Thu, Mar 21, 2013 at 6:36 AM, Tim Leydecker <[email protected]> wrote: > How about asking Adobe to support *.fbx? > > They already support reading *.ma files for cameras, lights and nulls. > > An upgrade to a filtered support of *.fbx, e.g. only the camera, > nulls and lights or maybe even any kind of (plotted/baked) keyframe data > (you can always plot/bake SRT animation to a light if everything else > fails) > might be an interesting I/O asset to have for Adobe? > > If they could even write the data out in *.fbx, that might be something, > too. > > Many Flame seats still have an AE/C4D assistant seat, where > camera/tracking/roto > is done and Flame speaks *.fbx, so does nuke and nukex brings an assistant > soon... > > Cheers, > > > tim > > > > > On 20.03.2013 22:06, Rob Chapman wrote: > >> hang on a minute... thats a bullet point... months of work, minimum! >> >> On 20 March 2013 22:01, Byron Nash <[email protected]> wrote: >> >> I think the point is that it would not take much effort at all for AD to >>> add minimal export functions to export camera and nulls to AE. We don't >>> need the kitchen sink, just a reliable camera and some nulls. >>> >>> >>> >>> >>
