## The short answer
They do different jobs. Enscape, V-Ray, Lumion and D5 render your 3D scene. An AI render tool such as OctopusWave takes a view of your scene, a sketch or a photo and produces a finished-looking image from it. If you need a measured, repeatable result from a fully modelled scene, use a render engine. If you need a convincing image of an idea in minutes, or a way to explore light, materials and mood before the model is finished, AI rendering is faster. Most studios end up using both.
## How each one works
**Enscape** runs inside your modelling program, including Revit, SketchUp and Rhino. You keep designing and the render window updates as you change the model. It is the tool for live design review.
**V-Ray** is an offline renderer. It calculates the image from the materials, lights and cameras in your scene, and an image can take minutes or longer. It is the classic choice for hero images where every material is set up by hand.
**Lumion** and **D5 Render** are standalone real-time tools. You bring your model into them, dress the scene with their libraries of plants, people, materials and weather, and render stills or walkthroughs.
**AI rendering** does not simulate light in a scene. It looks at a picture and produces a new picture, using what a model has learned about how buildings, materials and light look. With a tool that keeps your geometry fixed, the building stays yours and the surfaces, light and setting change.
## What that means in practice
| You need | Better fit |
| --- | --- |
| A live view while you design | Enscape or D5 |
| A fully controlled final image of a finished model | V-Ray |
| A large landscape with lots of vegetation and people | Lumion or D5 |
| Five atmosphere options for a massing model by tomorrow | AI rendering |
| A render of a sketch or a photo, with no 3D model | AI rendering |
| Day, dusk and night versions of the same camera | Either, AI rendering is quicker to set up |
| Measured results you must defend technically | A render engine |
## Where AI rendering is the wrong tool
Be honest with clients and yourself about the limits:
- **It is not physically measured.** Light and shadow in an AI render look right but are not calculated from your sun angle and materials. Do not use it for daylight studies or glare analysis.
- **It is not interactive.** There is no walking around the model in real time.
- **Small details can drift.** Text on signs, window mullions and repeated elements need checking in every image.
- **It cannot show what you did not send.** The back of the building needs its own view.
## Where AI rendering saves real time
- **Early design.** A white massing model becomes a believable image in minutes, so you can compare three options with a client instead of one.
- **Competitions and tight deadlines.** Several views in a single style, ready before the model is detailed.
- **Existing buildings.** A photo of the site becomes the starting image for a proposal.
- **Variations.** Same camera, different light or materials, without rebuilding anything.
## How studios combine them
A common pattern: design with Enscape or D5 open for live review, send the view you want to present to an AI render tool for the mood and the materials, and keep V-Ray for the one image that has to be exact. The tools do not compete for the same minute of your day, they cover different minutes.
If you work in SketchUp, Rhino or Revit, OctopusWave has plug-ins that send the current view straight from the program and keep your geometry and camera, so the AI step costs you one click. See the [plugins page](/plugins). For a hands-on look at the geometry lock, read the [SketchUp workflow](/news/sketchup-to-photoreal-render-workflow) or the [Rhino workflow](/news/rhino-to-photoreal-render-workflow).
## A fair way to decide
Take one real project. Render the same view in the tool you use today and in an AI render tool, and compare two things: how long each took, and whether you would show the result to the client. That test tells you more than any feature list. New OctopusWave accounts get five free renders from the plug-ins, which is enough for one honest comparison.