FBXExporter

FBXExporter [FBX] is a terminal utility in classic Fusion 3D. Its Input socket accepts a 3D scene and the tool writes a file to disk; a 2D image, material or MediaOut image cannot be fed directly. This is not a pixel renderer and does not replace Renderer3D.

The export workflow is similar to a Saver: connecting a scene and entering a Filename are not sufficient evidence that a file has been written. Resolve 21 describes triggering the export through Render. Confirm the resulting file and perform a round-trip import. Specific UI entry points in Fusion Studio versus the Resolve Fusion page still require a test in the target build.

Only the connected upstream 3D branch is exported. Branching FBXExporter after Duplicate3D exports that branch rather than automatically capturing a separate complete Merge3D scene. Connect the final Merge3D.Scene when the whole assembled scene is intended.

Exported object, camera and light names generally derive from the Fusion nodes that created them. Give important scene nodes stable names before export. FBX interchange does not, by itself, guarantee full native Fusion hierarchy, procedural materials, shaders or application-specific metadata.

Four original Inspector captures show Controls and the expanded Format, Version and FBX Frame Rate menus. Format includes binary/ASCII FBX, legacy FBX 6.0, general 3D exchange options and specialised motion-capture formats. A menu item is not evidence that every feature works for every selected format.

Filename is a destination, not a source asset. Browse helps choose the output folder but does not import geometry or start the export. Use versioned filenames and check write permissions and absolute paths to avoid overwriting a good delivery.

Version selects the FBX interchange revision. The captured dropdown lists Default and FBX201100 through FBX202000; the Resolve 21 reference explicitly describes Default as FBX2011. Do not equate Default with the highest revision. Check the resulting file in the chosen destination importer.

FBX Frame Rate sets the animation time base written into the FBX scene. The dropdown includes 24.0 along with multiple fractional and high-frame-rate values. Ensure the source timeline and destination DCC use matching time bases; an incorrect setting can shift frame-accurate camera tracking.

Scale Units By affects the exported units/size. The source Inspector shows 1.0. Coordinate-axis conversion and physical size are different issues: verify object dimensions, camera position and orientation independently after import.

Geometry, Lights and Cameras are independent content filters. Enable Cameras for tracked-camera delivery and make sure an actual Camera3D node feeds the selected export branch. Disabling Geometry or Lights does not modify or delete the original Fusion scene.

Render Range is often misinterpreted. The Resolve 21 manual says the checkbox saves render-range information in the output file for other applications. It is not documented as a replacement for selecting the actual frame range in the Render workflow.

File Per Frame (No Animation) switches from one animated file to a numbered static scene file for each frame. Its conditional Sequence Start Frame controls file numbering and is not visible in the captured off state. Reduce Constant Keys is a separate optimisation for adjacent identical animation keys.

Acceptance must include an import into the intended DCC and checks for node names, camera framing, geometry, axes, unit scale and motion at the start, middle and end of the shot. Successful file creation alone is not sufficient evidence of interchange fidelity.

The original screenshots establish Inspector menu labels, not a successful native export, round trip, or support for every format. The four exercises are typed instructional diagrams, not executable .comp templates or pre-rendered .fbx files.