Turn Houdini and Solaris views into AI concept stills for look development.
Develop Houdini Redshift and Solaris work-in-progress views into AI concept stills for look development and shot discussion.
Develop Houdini Redshift and Solaris work-in-progress views into AI concept stills for look development and shot discussion.
Redshift for Houdini is used to render procedural assets, simulations, environments, product arrangements, and look-development shots from Houdini. In a traditional Houdini context, a Redshift ROP carries render controls such as sampling, motion blur, output, and AOV settings. In Solaris, Redshift works on the USD stage: the Render Settings LOP controls render settings, including camera and resolution, while the USD Render ROP initiates output with the selected render delegate. A Render Product LOP and Render Var LOPs are relevant when the final Solaris render needs defined AOVs. RENDERCAD fits the earlier, exploratory image task rather than replacing that controlled render pipeline. Start from a clean Redshift IPR, Houdini viewport, or Solaris Scene View that already conveys the important geometry, camera, and rough light direction. This can be a pyro silhouette, vellum fabric test, groom, instanced landscape, procedural prop, material study, or a blocked product scene. Use the view to develop a polished still for a pitch, art-direction review, dailies discussion, or client-facing mood reference. Bring the selected visual direction back into Houdini for the approved camera, materials, lighting, simulation cache, animation, and final Redshift render. Redshift remains the source of truth for frame sequences, repeatable settings, AOVs, and compositing deliverables.
Choose a Redshift IPR, Houdini viewport, or Solaris Scene View that clearly shows the intended camera, main forms, and useful context. Avoid a debugging view, missing-texture state, or an image where the subject is hidden by interface panels. For an FX shot, use a representative simulation frame; for a procedural asset or product scene, use the angle that makes scale, silhouette, and material intent legible. Use RENDERCAD to explore a presentation still with alternative lighting mood, environmental context, or composition for a review or treatment. Treat that image as visual direction, then reproduce approved decisions in Houdini. Use the Redshift ROP for classic Houdini output, or pair the Solaris Render Settings LOP with the USD Render ROP for final Solaris output. When compositing needs passes, define the required Render Vars and collect them in a Render Product before rendering. Keep final animation, render quality decisions, AOV naming, and delivery output in Redshift.
Modeled by CADSharp in Onshape. Rendered with RENDERCAD.
Add | Change | or Remove referenced objects with the stroke of a brush.
RENDERCAD uses a maintained selection of image-generation models for different rendering tasks. Results can vary by model and input, so compare generated output with the source design before relying on geometry, materials, or dimensions.
| Feature | RENDERCAD | Redshift for Houdini |
|---|---|---|
| Engine | Generative AI | Biased production renderer with GPU and CPU rendering options |
| Output | Images + Video | Still images, frame sequences, AOVs, image files, and Redshift proxy exports; deep output is available for compatible workflows |
| Resolution | HD / 4K | Set through the render camera, Redshift ROP, or Solaris Render Settings LOP and constrained by the scene and available hardware |
| Image Speed | Image renders complete in 60 seconds. | Interactive viewport and IPR previews through to longer final renders, depending on scene complexity, sampling, volumes, motion blur, and compute hardware |
| Video Speed | Videos complete in 2-5 minutes. | Animation is rendered frame by frame and can be submitted through command-line or render-manager workflows |
| Scene Set Up | No separate local scene | A Houdini scene with Redshift materials, lights, cameras, and render settings, or a Solaris stage using Render Settings and USD Render ROP nodes; Render Product and Render Var nodes are used for Solaris AOV output |
| Input | Screen Snip | Houdini scenes containing geometry, cameras, materials, lights, simulations, and Solaris/USD stage data |
| Hardware | Cloud GPU | Houdini desktop workflows on supported Windows, macOS, and Linux configurations |
| Install | None | Install Redshift and configure the matching Houdini and Solaris plugin paths, commonly with a Houdini package or environment configuration |
| Cost | from $9/mo | Commercial licensing is required; availability and terms depend on the account and region |
Read the numbers. We trust you to know theirs.
Skip a separate local scene build. Pick a condition, material, and background while RENDERCAD handles the image-generation step. Image renders complete in 60 seconds.
™
RENDERCAD™
Use the browser workflow directly, capture a selected view with the desktop app, or start from the browser extension.
Get StartedCommon solutions for Redshift for Houdini users
Add a familiar scale cue such as a person, hand, or furniture item, then verify the generated relationship against known dimensions in the source model.
Image renders complete in 60 seconds.
Generation runs on cloud infrastructure, so a local rendering GPU is not required. The device still needs sufficient resources for the source application, browser, and network connection.
Context prompts can provide a visual scale cue, but the source model and known dimensions remain authoritative. Do not infer measurements from generated imagery.
RENDERCAD starts from a 2D image and uses generated material and environment direction. Built-in renderers may provide direct scene, geometry, lighting, and material control.
Provide a material reference or describe the intended scale, then compare the result with known dimensions and the source model.
Yes. An authorized location photo can guide a background option. Verify scale, placement, perspective, and site conditions before using the generated image.
Yes. Mask each region and assign an authorized texture reference or instruction. Review material boundaries, scale, and product fidelity after generation.
Photograph an authorized prototype or sample and use it as a material reference. Verify color, texture scale, gloss, and product fidelity because generated output will not match reality exactly.
Capture the model, describe the wood species and grain direction, and add an authorized material reference when needed. Generated grain varies and should be reviewed for scale and orientation.
Upload a CAD screenshot, real photo, or hand drawing and describe warm golden-hour light and the intended direction. Review the generated color and shadows because the interpretation can vary.
Start from an image that clearly shows the existing separated components, then choose the Exploded View product motion. Review the clip against the source because generated motion can alter part boundaries or relationships.