Search is based on keyword.
Ex: "Procedures"
Do not search with natural language
Ex: "How do I write a new procedure?"
WriteGeo
Writes out geometry to a specified file. You can export:
• OBJ files
• FBX files containing meshes, point clouds, cameras, lights, and axes.
• Alembic (.abc) files containing meshes, point clouds, cameras, or axes. For more information on Alembic, see http://code.google.com/p/alembic/.
You can write the geometry by clicking the Execute button and specifying a range of frames you want written or by running the Nuke script with the -x switch.
See also ReadGeo.
Inputs and Controls
|
Connection Type |
Connection Name |
Function |
|
Input |
unnamed |
The geometry or scene you want to write out to a specified file. |
|
Control (UI) |
Knob (Scripting) |
Default Value |
Function |
|
WriteGeo Tab |
|||
|
file |
file |
none |
Enter the file path and file name or use the folder icon to browse to the required location. |
|
Execute |
Execute |
N/A |
Click to write the input geometry to the file specified in the file control. |
|
frame range |
first |
1 |
When limit to range is enabled, enter the first frame to write to the specified file. |
|
last |
1 |
When limit to range is enabled, enter the last frame to write to the specified file. |
|
|
limit to range |
use_limit |
disabled |
When enabled, enter the first and last frames to write to the specified file. |
|
views |
views |
main |
When you’re working with stereo footage, select the required view. |
|
file type |
file_type |
none |
Select the file type you intend to write: • none - Nuke attempts to guess the file type from the file name, but you cannot set any type-specific controls. • abc - when the WriteGeo node is connected to a Scene node, writes to an .abc file and exposes the Alembic-specific controls (see abc Options). • fbx - when the WriteGeo node is connected to a Scene node, writes to an .fbx file and exposes the FBX-specific controls (see fbx Options). • obj - write to an .obj file. |
|
abc Options (These controls are only exposed when file type is set to abc.) |
|||
|
geometries |
writeGeometries |
enabled |
When enabled, write the scene geometries into the .abc file. |
|
pointClouds |
writePointClouds |
enabled |
When enabled, write the scene point clouds into the .abc file. |
|
cameras |
writeCameras |
enabled |
When enabled, write the scene cameras to the .abc file. |
|
axes |
writeAxes |
enabled |
When enabled, write the scene axes into the .abc file. |
|
storage format |
storageFormat |
HDF |
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. |
|
fbx Options (These controls are only exposed when file type is set to fbx.) |
|||
|
geometries |
writeGeometries |
enabled |
When enabled, write the scene geometries into the .fbx file. |
|
cameras |
writeCameras |
enabled |
When enabled, write the scene cameras to the .fbx file. |
|
lights |
writeLights |
enabled |
When enabled, write the scene lights into the .fbx file. |
|
axes |
writeAxes |
enabled |
When enabled, write the scene axes into the .fbx file. |
|
point clouds |
writePointClouds |
enabled |
When enabled, write the scene point clouds into the .fbx file. |
|
ascii file format |
asciiFileFormat |
disabled |
When disabled, a binary .fbx file is written. Check ascii file format to write the scene as an ascii .fbx file. |
|
animate mesh vertices |
animateMeshVertices |
disabled |
When enabled, the mesh vertices are animated and keyframes created at every frame. The animated meshes use vertex point cache for the data and a directory with _fpc appended to the file name is created to contain the point caches. |
|
Python Tab (These controls are for Python callbacks and can be used to have Python functions automatically called when various events happen in Nuke.) |
|||
|
before render |
beforeRender |
none |
These functions run prior to starting rendering in execute(). If they throw an exception, the render aborts. |
|
before each frame |
beforeFrameRender |
none |
These functions run prior to starting rendering of each individual frame. If they throw an exception, the render aborts. |
|
after each frame |
afterFrameRender |
none |
These functions run after each frame is finished rendering. They are not called if the render aborts. If they throw an exception, the render aborts. |
|
after render |
afterRender |
none |
These functions run after rendering of all frames is finished. If they throw an error, the render aborts. |
|
render progress |
renderProgress |
none |
These functions run during rendering to determine progress or failure. |
Step-by-Step Guides
Exporting Geometry, Cameras, Lights, Axes, or Point Clouds
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
Thanks for taking time to give us feedback.