Panoramas & 360 Tours

A normal render captures a single rectangular view - what the camera sees looking one way. A 360 panorama captures every direction from one fixed point at once: the full sphere around the camera, up, down and all the way around. The engine renders that sphere and stores it as a single flat image in an equirectangular projection - a picture twice as wide as it is tall, where the horizontal axis wraps a full 360 degrees around and the vertical axis spans floor to ceiling. It looks distorted and stretched as a flat file, especially at top and bottom, but that is expected: it is a map of a sphere flattened onto a rectangle, the same way a world map flattens the globe.

The magic happens on playback. A 360 viewer - built into web browsers, phones and social platforms - takes that equirectangular image and re-wraps it back onto a sphere with the viewer at the centre. Now, instead of a distorted flat picture, the user sees a natural view in whatever direction they point, and they drag (or, on a phone, physically turn) to look around freely. On a mobile device the phone's motion sensors can drive it, so lifting and turning the phone feels like looking around the room through a window. It is not full VR - you cannot walk, and you are anchored to that one spot - but the sense of being somewhere and choosing where to look is surprisingly strong, and it requires nothing more than a browser.

A useful distinction is monoscopic versus stereoscopic panoramas. A monoscopic 360 is a single image shown to both eyes - the standard, and perfect for phones and browsers. A stereoscopic 360 renders a slightly different image for each eye, adding true depth when viewed in a headset, at the cost of longer render times and larger files. For the common case - a link a client opens on a phone - monoscopic is exactly right. Reach for stereoscopic only when the panorama will be viewed in a headset and the extra depth is worth the overhead.

The best part for an architect is that rendering a 360 panorama is nearly as easy as rendering a normal view, because the real-time engines you already use build it in. In Enscape there is a dedicated panorama capture: stand your camera in the spot you want, click to render a 360, and it is saved to a panorama gallery you can revisit and share - Enscape can even produce the stereo pair for headset viewing. Twinmotion, Lumion and D5 all offer equivalent 360 or panorama exports. You compose by choosing the position rather than the frame, since the panorama sees everything, and the engine does the rest, producing the equirectangular image ready to view.

Because the panorama captures the whole sphere, the craft shifts slightly from normal rendering. Position is everything: where you place the single point determines the whole experience, so choose spots that make sense as places a person would stand and pause - the centre of a room, the threshold of a doorway, a spot by the window - rather than awkward corners. Everything is on show, so there is nowhere to hide an unresolved area; the ceiling, the floor and the parts of the room you would normally crop out are all visible, so the whole space must be modelled and lit to a consistent standard. And height matters: set the camera at natural standing eye level so the space feels right, neither crouching nor floating.

The same fundamentals from the whole course still apply, and if anything they matter more because the viewer controls the gaze. Good light, believable materials and a clean, fully resolved scene carry a panorama exactly as they carry a still - but you cannot lean on a single flattering composition to disguise weak spots, because the client can look anywhere. Think of a 360 as an honesty test for your scene: if it holds up when the viewer is free to stare in every direction, it is genuinely well made. Get the position, height and all-round quality right and a single click produces an immersive image far more engaging than a flat render, for barely more effort.

A single panorama puts a client on one spot. Link several together and you get a virtual tour - a set of panorama nodes the viewer moves between, so they can effectively walk through the whole project in a browser. This is the same familiar format as the property tours on real-estate sites and the indoor tours on mapping platforms, and clients already know instinctively how to use it: you look around from where you are, then click to move to the next spot.

The connective tissue is the hotspot - a clickable marker placed inside a panorama that jumps the viewer to another node. You render a panorama in each key location (entry, living room, kitchen, main bedroom, terrace), then place a hotspot in each one pointing toward the neighbouring spaces: an arrow on the floor toward the living room, a marker in the doorway to the kitchen. Clicking it transports the viewer to that node's panorama, exactly as if they had walked there. Arrange the nodes to follow a natural circulation route and the result is a coherent walk-through of the building, assembled entirely from still 360 images - light to deliver, and playable on any device.

Hotspots can do more than move you between rooms; they can inform. An information hotspot can pop up a note, a specification, a material sample, a dimension, or a link when clicked - so a tour is not only spatial but annotated, letting a client explore and learn about what they are seeing. The tours are usually assembled in dedicated virtual-tour software or platforms that take your rendered panoramas and let you place the nodes, wire up the hotspots and publish, though some rendering tools offer basic linking directly. Either way, the ingredients you supply are simply a well-chosen set of 360 renders; the tour builder turns them into a navigable, shareable experience. It is a remarkably high-value deliverable for the effort - most of the work is rendering panoramas you already know how to make.

The reason 360 tours have become so popular in practice is their frictionless delivery. A finished tour is typically a web link. You send it, and the client opens it in an ordinary browser on whatever they have to hand - laptop, tablet or phone - with nothing to install and nothing to learn. They drag to look around and tap the hotspots to move. On a phone, the tour can respond to the device's motion so turning the phone turns the view, which feels naturally immersive, and the same phone can be slipped into an inexpensive cardboard-style holder to give a basic but real VR experience for almost nothing. So a single set of rendered panoramas serves every viewer at once: a casual look on a laptop, a hands-on explore on a phone, and a lightweight VR experience for anyone who wants it - no headset required, though welcomed if present.

That reach is exactly what makes 360 tours such a practical part of a visualizer's toolkit. Unlike a VR session, which needs a headset and you in the room, a tour can be sent to a client on the other side of the world, forwarded to a whole committee, embedded in a web page for a public consultation, or handed to a sales team to show prospective buyers. It is asynchronous and self-service: the client explores in their own time, as often as they like, and shares it onward effortlessly. For marketing an off-plan development or gathering feedback from stakeholders who cannot all be in one room, that is enormously valuable.

Set against VR and Unreal, the 360 tour occupies a sweet spot this whole module has been circling. It gives up walking and full presence, and it is anchored to fixed spots - genuine limitations. In return it costs the viewer nothing, needs no special hardware or software, reaches anyone with a browser, and is built almost entirely from panorama renders you already know how to make. For a huge share of real projects, that trade is exactly right: the most immersion you can deliver for the least friction. Master the panorama, the hotspot and the tour, and you can put a client inside your design with nothing more than a link - a fitting close to a module about stepping inside the work, and to the immersive craft this course has built toward.