Explore presentation directions from one selected Enscape still.
RENDERCAD receives one flat PNG or JPEG still exported from Enscape. It does not connect to Enscape, open host models, or inherit live links, cameras, materials, BIM data, or hidden geometry. Shared page media shows general architecture and Onshape examples, not Enscape output or an integration.
Enscape runs beside supported Revit, SketchUp, Rhino, Archicad, and Vectorworks projects as a real-time visualization plugin. Teams can navigate the current scheme and create image captures, panoramas, video, virtual-reality experiences, and other review material. The available hosts and capabilities differ between Windows and macOS.
The same exported-still process works across Enscape hosts. Host-specific setup is covered in the Revit, SketchUp, Rhino, Archicad, and Vectorworks guides, so use the guide for the authoring application behind the image when its controls or project structure matter.
Decide where the image will appear: a review slide, proposal cover, competition panel, leasing crop, or portfolio spread. Set the intended aspect ratio, then choose an exterior, interior, courtyard, or approach that remains clear at that size.
Lock the horizon, crop, major edges, openings, circulation cues, and scale references before experimenting. Then test one concern per round, perhaps planting density, seasonal character, entourage, tonal hierarchy, or the emphasis of an existing finish.
Place every option beside the original frame and reject attractive pictures that describe a different scheme. Use the surviving direction as presentation material. Send geometric revisions, BIM records, specifications, and documentation back to the authoring application. Manage viewpoints, assets, visual settings, and cameras through Enscape's connection.
Open the correct authoring file, note its revision, launch Enscape, and settle the visualization. Confirm the viewpoint, visual preset, assets, lighting, horizon, and context. Make sure the frame answers the issue planned for the meeting or layout.
Save the settled frame in PNG or JPEG form at the planned aspect ratio and dimensions. Clear away interface panels, selection marks, and unrelated markup. Use a revision and frame name that lets the team find the same checkpoint after later design work.
Upload that single picture with a concise brief. State what must stay recognizable and what may change. A request might hold the facade rhythm while adjusting planting maturity, or protect a room arrangement while testing a quieter tonal balance.
Review each option at its final display size beside the source. Trace fixed edges and relationships rather than judging mood alone. Keep a useful visual direction. If it reveals a design change, revise the host file; if it reveals a visualization change, update the Enscape setup.
The shared motion clip uses a general Onshape source supplied by CADSharp rather than Enscape work. Movement is inferred from the submitted picture, without an Enscape camera path or connected project context.
Mark a surface, sky, planting area, or surrounding context and describe the presentation change. The edit affects pixels, not Enscape materials or host geometry.
Explore atmosphere, material emphasis, landscape maturity, entourage, or composition from the same settled frame. Compare every option with the exported Enscape still before selecting it.
| Feature | RENDERCAD | Enscape host-plugin workflow |
|---|---|---|
| Engine | Generative image models | Real-time architectural visualization connected to a supported CAD or BIM host project |
| Output | Presentation images and optional generated video | Still images, batch renders, panoramas, video, virtual-reality experiences, and supported standalone presentation formats |
| Resolution | Up to 4K image output | Controlled by Enscape capture settings, output type, host context, and the available system resources |
| Image Speed | Image completion is usually around one minute. | Live-view response and still-export time vary with project complexity, quality settings, resolution, and hardware |
| Optional generated motion | Completion time varies by video model and settings. | Video preparation and export time vary with path, duration, quality, project complexity, and hardware |
| Scene Set Up | Flat source image and written presentation direction | Host geometry, materials, assets, lighting, visual settings, camera or saved view, and surrounding context |
| Input | One PNG or JPEG image | A supported Revit, SketchUp, Rhino, Archicad, or Vectorworks project accessed through the Enscape plugin |
| Hardware | Cloud processing | Windows supports all five named hosts; macOS supports SketchUp, Rhino, Archicad, and Vectorworks, with capabilities varying by host and system |
| Install | Web app | Install Enscape for the supported host applications used on the workstation |
| Cost | See current RENDERCAD pricing | Current access and commercial terms are provided by Chaos and can vary by region and offering |
The upload is only an image and carries no model-scale metadata. Keep geometry, BIM information, specifications, and documentation in the host project; keep visualization settings and cameras in Enscape.
Record the host project revision, Enscape view or camera, aspect ratio, visual preset, and export size. That checkpoint keeps later presentation rounds comparable after the design changes.
™
RENDERCAD™
Use PNG or JPEG with the intended frame, important edges, openings, materials, and context readable. Remove interface chrome and unrelated review marks before upload.
Get StartedEnscape supported hosts, exported images, model authority, and presentation limits
Use it for the shared still-image handoff across supported hosts. For host-specific setup, use the Revit, SketchUp, Rhino, Archicad, or Vectorworks guide. The comparison page explains how RENDERCAD and Chaos Enscape differ.
Windows support covers Revit, SketchUp, Rhino, Archicad, and Vectorworks. macOS support covers SketchUp, Rhino, Archicad, and Vectorworks, not Revit. Exact features and requirements can differ by host and operating system.
No. The upload is an image rather than a model handoff. The authoring file and connected Enscape session stay separate, so RENDERCAD cannot inspect or update project elements, materials, settings, or saved viewpoints.
Choose one settled camera that explains a specific question, such as an arrival, facade, room, courtyard, or landscape relationship. Keep fixed edges, openings, circulation cues, and important context readable at the intended presentation size.
For the upload, choose PNG or JPEG at the frame size and proportion needed by the final layout. Inspect edges, materials, and context after export, and leave interface elements or markup out unless they explain the review.
The host file governs geometry, BIM information, specifications, and documentation. Enscape manages the connected visualization, including views, assets, visual settings, and cameras. A generated presentation option does not revise either source.
Check the silhouette, openings, levels, facade rhythm, room relationships, furnishings, planting layout, and fixed context. Reject any option that changes a design-critical condition, even when its atmosphere or finish looks convincing.
No. The video model invents movement from the submitted picture; it does not follow an Enscape camera path or reveal the connected project. Use the clip only as a visual sketch, never as a verified walkthrough.