Task Relay

Task Relay guides · Research / Model / Present

Render selected Rhino views for a design review

Reuse the cameras saved in your model and produce a consistent set of review images from the selected revision.

The problem

How to export saved views together or render only selected named views? Use the cameras saved in your model to prepare a consistent set of rendered images for review.

Rhino already has BatchRenderNamedViews. Use that directly for a simple all-views export. Relay is useful when the renders belong to a reviewed model revision and will feed a later presentation stage.

Prepare the model once

You provide: an exact .3dm with saved named views, materials and lighting, plus the requested view names and resolution. Rhino 7 or 8 must be installed and licensed on macOS.

You get: a PNG and execution checks for each approved render operation. Relay's current render operation handles one existing named view per operation, using built-in Rhino Render at 64–1024 pixels per axis. Several views need several explicitly listed operations.

Give Relay this request

Inspect this selected .3dm and confirm named views [Overview] and [Street].
Prepare a separate built-in Rhino Render operation for each view at
[1024 x 768]. Use this model's existing materials and lighting.
Show the exact model, view and resolution for each operation before Start.
Return each render PNG and its checks for my review. Keep the source model
unchanged. After I select the images, use them in a new design-review PPTX.

Keep the outputs comparable

  1. Confirm the named views exist in the selected model. Create or correct cameras in a separate model edit if needed.
  2. Review each prepared render specification before starting the host operations.
  3. Inspect the returned images for camera framing, lighting and material appearance. A successful file check is not visual acceptance.
  4. Select the images for the presentation stage. For a later model revision, select that exact version and render the same named views again.

This operation uses the model's existing setup. Third-party render engines, automatic material creation and dependency packaging are outside it. Its resolution limit makes this a review-image workflow; high-resolution print output needs a separate route.

Capability check: rhino.inspect and rhino.render are present in the audited app bundle. See the operation documentation for implementation scope and recorded checks. This article is a workflow recipe; its exact prompt has not been qualified through a complete live Relay run. Forum reports establish a problem, not measured time savings.