FBXMesh3D

Resolve 21 describes FBXMesh3D as an importer for polygon geometry from FBX as well as OBJ, 3DS, DAE and DXF. It is a geometry source rather than a processor that requires an incoming scene, so it can operate standalone and already outputs scene3d.

With direct FBXMesh3D import, geometry in the file is combined into one mesh with one pivot and one transform. This is convenient for a single asset but does not preserve independent object hierarchy inside the file.

Animation is a crucial boundary: the Resolve 21 introduction says direct FBXMesh3D ignores animation applied to geometry. To preserve cameras, lights, meshes and object animation, use Fusion > Import > FBX Scene, which creates individual nodes/hierarchy. Take Name therefore should not be taught as an ordinary standalone animation picker.

FBXMesh3D has two optional inputs. Orange SceneInput accepts an additional classic scene3d branch and combines it with imported FBX geometry. Green MaterialInput accepts either a 2D image or a 3D material.

When MaterialInput receives a 2D image, Fusion uses it as the diffuse texture of the built-in Basic Material. When an external 3D material is connected, the built-in Material tab is disabled and the external material becomes the surface path for the imported geometry.

Controls / Size is specifically useful for import-unit normalization: the manual notes that FBX meshes are often much larger than Fusion's default unit scale. The regular Transform tab then handles placement/animation in the scene. Size and Transform Scale are different layers.

Object Name and Take Name are associated with FBX Scene import metadata. The reference describes them as fields set by Fusion during scene import; with a blank Object Name, file contents are imported as one mesh. Do not turn these into an invented object/take browser inside the direct node.

The current Inspector capture shows a Streams area containing 'No data - render me!'. The main Resolve 21 text does not document Streams as a distinct artist control, so this article records its UI presence while leaving exact target-build behavior for live verification.

Wireframe has a renderer dependency: Resolve 21 explicitly states that wireframe rendering is supported only by the OpenGL/Hardware Renderer3D path. Keep that separate from ordinary shaded rendering.

Visibility, Lighting, Matte, Blend Mode, Normals/Tangents, ObjectID, Material and Transform are common classic-3D controls. Troubleshoot object-level and material-level lighting/shadow switches independently.

FBXMesh3D Output is scene3d. Neither file import nor MaterialInput produces an RGBA image. Renderer3D is required before MediaOut and normal 2D effects; Merge3D is useful for cameras/lights/other branches, but standalone FBXMesh3D does not require SceneInput.

Bundled captures verify current Controls, common Blend/Normals/ObjectID, Material and Transform tabs. Core semantics were cross-checked against the Resolve 21 reference and Fusion Tool Reference; live Resolve 21/21.1 execution with a real FBX was not run for this package.