USDRECORD(1)

πŸ“¦
version 26.11.1 Β· 5 versions
, in arch rolling

πŸ’… USDRECORD(1) πŸ’…

🌸 NAME 🌸

usdrecord β€” manual page for usdrecord 26.11.1. Okay bestie, this is the USDRECORD(1) page from User Commands, and it’s literally giving β€œrender my USD file into images” energy. Obsessed. πŸ’–

✨ DESCRIPTION ✨

Generates images from a USD file. That’s the whole mission, no cap.

Here’s the usage vibe, copied exactly so you don’t have to squint:

usage: usdrecord [-h] [--mask PRIMPATH[,PRIMPATH...]]
              [--purposes PURPOSE[,PURPOSE...]]  [--sessionLayer SESSIONLAYER]
              [--disableGpu] [--disableDrawMode] [--disableCameraLight]
              [--resolverContext {root,inherit}] [--camera CAMERA]
              [--defaultTime | --frames FRAMESPEC[,FRAMESPEC...]]
              [--complexity {low,medium,high,veryhigh}] [--colorCorrectionMode
              {disabled,sRGB,openColorIO}] [--renderer {Storm,Embree,GL}]
              [--imageWidth IMAGEWIDTH] [--enableDomeLightVisibility]
              [--renderPassPrimPath RPPRIMPATH] [--renderSettingsPrimPath
              RSPRIMPATH] [--traceToFile TRACETOFILE] [--traceFormat
              {chrome,trace}] [--memstats] [--abortOnError] usdFilePath
              outputImagePath

πŸŽ€ positional arguments πŸŽ€

  • usdFilePath β€” USD file to record. This is your main character: the file you’re pointing at. 🫢
  • outputImagePath β€” Output image path. For frame ranges, the path must contain exactly one frame number placeholder of the form ### or ###.###. Note that the number of hash marks is variable in each group.

πŸ’– options πŸ’–

  • -h, --help β€” show this help message and exit. Your β€œwait, what does this do again?” button.
  • --mask PRIMPATH[,PRIMPATH...] β€” Limit stage population to these prims, their descendants and ancestors. To specify multiple paths, either use commas with no spaces or quote the argument and separate paths by commas and/or spaces. Very β€œcurate the guest list” of it all. πŸŽ€
  • --purposes PURPOSE[,PURPOSE...] β€” Specify which UsdGeomImageable purposes should be included in the renders. The "default" purpose is automatically included, so you need specify only the additional purposes. If you want more than one extra purpose, either use commas with no spaces or quote the argument and separate purposes by commas and/or spaces.
  • --sessionLayer SESSIONLAYER β€” If specified, the stage will be opened with the 'sessionLayer' in place of the default anonymous layer.
  • --disableGpu β€” Indicates if the GPU should not be used for rendering. If set this not only restricts renderers to those which only run on the CPU, but additionally it will prevent any tasks that require the GPU from being invoked.
  • --disableDrawMode β€” Disables support for USD draw modes. If set, UsdGeomModelAPI's draw modes will be ignored, and no geometry will be replaced with a draw mode standin. Everything will render as if applyDrawMode = false.
  • --disableCameraLight β€” Indicates if the default camera lights should not be used for rendering. Camera lights are not invited to this party. 😌
  • --resolverContext {root,inherit} β€” Indicates which resolver context to use. Choosing "root" will create a resolver based on the rootLayer. Choosing "inherit" will inherit the incoming resolver from the environment.
  • --camera, -cam CAMERA β€” Which camera to use - may be given as either just the camera's prim name (i.e. just the last element in the prim path), or as a full prim path. Note that if only the prim name is used and more than one camera exists with that name, which one is used will effectively be random (default=None). So yeah, no cap: duplicate prim names = mystery camera roulette. 🎲
  • --defaultTime, -d β€” explicitly operate at the Default time code (the default behavior is to operate at the startTimeCode authored on the UsdStage which defaults to 0.0).
  • --frames, -f FRAMESPEC[,FRAMESPEC...] β€” specify FrameSpec(s) of the time codes to operate on - A FrameSpec consists of up to three floating point values for the start time code, end time code, and stride of a time code range. A single time code can be specified, or a start and end time code can be specified separated by a colon (:). When a start and end time code are specified, the stride may optionally be specified as well, separating it from the start and end time codes with (x). Multiple FrameSpecs can be combined as a comma-separated list. The following are examples of valid FrameSpecs: 123 - 101:105 - 105:101 - 101:109x2 - 101:110x2 - 101:104x0.5
  • --complexity, -c {low,medium,high,veryhigh} β€” level of refinement to use (default=low). Pick your render’s glow-up level. ✨
  • --colorCorrectionMode, -color {disabled,sRGB,openColorIO} β€” the color correction mode to use (default=sRGB).
  • --renderer, -r {Storm,Embree,GL} β€” Hydra renderer plugin to use when generating images. "GL" and "Storm" currently alias to the same renderer, Storm.
  • --imageWidth, -w IMAGEWIDTH β€” Width of the output image. The height will be computed from this value and the camera's aspect ratio (default=960). Note that this only affects the command-line output image; it does not affect any render products in scene description.
  • --enableDomeLightVisibility β€” Show the dome light background in the rendered output. If this option is not included and there is a dome light in the stage, the IBL from it will be used for lighting but not drawn into the background. So it’s lit but lowkey camera-shy. πŸ’‘
  • --renderPassPrimPath, -rp RPPRIMPATH β€” Specify the RenderPass prim to use. This overrides any renderSettingsPrimPath specified in stage metadata.
  • --renderSettingsPrimPath, -rs RSPRIMPATH β€” Specify the RenderSettings prim to use. This overrides any renderSettingsPrimPath specified in stage metadata.
  • --traceToFile TRACETOFILE β€” Start tracing at application startup and write --traceFormat specified format output to the specified trace file when the application quits
  • --traceFormat {chrome,trace} β€” Output format for trace file specified by --traceToFile. 'chrome' files can be read in chrome, 'trace' files are simple text reports. (default=chrome)
  • --memstats β€” Use the Pxr MallocTags memory accounting system to profile USD, saving results to a tmp file, with a summary to the console. Will have no effect if MallocTags are not supported in the USD installation.
  • --abortOnError β€” Abort recording and return a non-zero exit code if a Tf error is raised during rendering. No β€œignore the red flags” behavior here, bestie. 🚩

πŸ’– aaaand that’s the USDRECORD(1) manual β€” usdrecord 26.11.1, October 2026. Slay, render, and read your trace files responsibly. πŸŽ€

πŸ“¦ where this page comes from