What you need before you start
The software, renders, camera points and model you need to make an ArchviewVR tour.
Software
- 3ds Max with Corona. The guide and the ArchviewVR Exporter are written for 3ds Max, and the render settings for Corona.
- A computer with a modern browser. Your renders are read and resized on your own computer, so a desktop or laptop is best for uploading.
The three things in your folder
| What | File types | Where it comes from |
|---|---|---|
| Renders | 2:1 JPEG or PNG | One spherical 360 render per camera. See Rendering 360° with Corona. |
| Camera points | .txt or .json | The exporter’s points.txt. See Export with the ArchviewVR Exporter. |
| Proxy model | .obj, .glb or .gltf | A simple version of the building. See Making a simple proxy model. |
What makes a good tour
- Enough cameras. One every 2–4 metres, in every room, along hallways and in doorways. Most homes need 20 to 60. See Placing and naming cameras.
- Eye height and level. About 1.6 m above each floor, with no tilt or roll.
- Matching names. Each render named exactly like its camera, with no spaces.
- A consistent look. The same exposure, white balance and tone mapping on every camera, because neighbouring renders are blended as buyers move.
- A light model. Floors, walls, ceilings, stairs and big joinery, windows capped, under 150K polygons.
Limits to know
- Each project can hold up to 500 MB, counting every render size and the model.
- A trial project saves up to 10 renders. Publishing lets you save them all. See Trial vs published tours.
Tip: not ready for a whole home? Try a trial with a few cameras in one or two rooms first. It’s the quickest way to see how your renders and model come together.
If you don’t use the exporter
The points file is plain text with one line per camera: the name, then x, y and z, in the same units as the model. For example Cam_Kitchen_01 412.5 -86.0 160.0. A name can’t contain spaces.
Was this helpful?