You can export geometry, cameras, light, axes and point clouds into an FBX (.fbx) or Alembic (.abc) file using the WriteGeo node.
| 1. | Create a WriteGeo node and attach it to a Scene node. |
| 2. | In the WriteGeo controls, select fbx or abc in the file type dropdown, and check the objects to export: |
• geometries - to write the scene geometries into the file.
• cameras - to write the scene cameras to the file.
• lights - to write the scene lights into the file (.fbx only).
• axes - to write the scene axes into the file.
• point clouds - to write the scene point clouds into the file.
| 3. | If you’re writing FBX files: |
• Check ascii file format if you don’t want to write out a binary .fbx file.
• Check animate mesh vertices if you want the mesh vertices animated and keyframes created at every frame. The animated meshes use vertex point caches for the data. A directory with _fpc appended to the file name is created to contain the point caches. By default the animated meshes check box is off so the point cache directory is not created.
| 4. | If you're writing Alembic files, select the storage format to use when writing the file: |
• HDF - A storage format that maintains backwards compatibility.
• Ogawa - A storage format that offers faster file reading and smaller files.
| 5. | Browse to the destination you want to save the .fbx or .abc file in the file field and give it a name. |
| 6. | Check the limit to range box if you want to disable the node when executed outside of a specified frame range. In the frame range fields, enter the range of frames you want to make executable with this Write node. |
| 7. | Select the views to export, such as left and right for stereoscopic projects. |
| 8. | Click Execute. |
| 9. | If necessary, you can change the frame range you want to include in the file using the pop-up dialog and then click OK. |
A progress bar displays, and the selected file is saved to the specified directory.
|
|