VecomDesign
Technology

The technology behind the demos

On the home page, what counts is what your customers see. Here is how it is made — for anyone who wants to know exactly.

Adaptive Experience

Every device gets the best version it can carry.

The page measures what your device can do and picks the tier by itself. Look and framing stay the same on every tier, only the workload changes. You can switch it here to try.

Technology, comparison, streaming For anyone who wants to know how it works — three short parts.

The technology behind it

One sentence per tool. More if you want.

Blender

Your object is rebuilt digitally — so precisely that it looks photographed.

More

Modelled at true scale in Blender 5.2, rendered with Cycles on an RTX 5070. The villa has 647 parts and 26 materials; the garden with more than 600,000 blades of grass, cypresses built from sprays of twigs, a dry-stone wall of some 7,800 individual stones and olive groves exists only for the photos.

Path tracing

Light is computed the way it travels in reality — hence the look of a photo.

More

Blender Cycles with a physical sky, real glass refraction and caustics, up to 32 light bounces. Exposure is measured: sunlit white render at 0.83–0.86 display luminance, the way a photographer would set it on location.

Three.js

Your visitor turns the model right in the browser — no app, no plugin.

More

Three.js r185, served from our own server. The house arrives as a GLB with 32,280 triangles: 2.0 MB on disk, 127 KB over the wire. It only loads when someone wants to turn it.

Adaptive Experience

The page adapts to every device — nobody gets a stuttering version.

More

Our own core (experience-core): device check, a short benchmark, five tiers. A governor lowers the tier when the frame rate keeps falling and carefully raises it again.

Unreal Engine

For premium properties: cinema quality, and your client is in control.

More

Unreal Engine 5 with Lumen for the real-time version and path tracing for film. The same villa is already set up there and calibrated against Cycles.

Pixel Streaming

A server computes the graphics — your client sees them on a phone.

More

Pixel Streaming over WebRTC. It only starts on a click, with a time limit and a monthly cap, because every minute costs a rented graphics card.

Before / after

A normal website or an experience?

Both have their place. This overview is meant to make the decision easier — not to talk down normal websites.

Normal website

Product photo

Enough when your product comes in one version and a good photo shows everything.

Vecom Experience

Product you can turn

Worth it when there are variants: 72 table versions from one model instead of 72 photo shoots.

Normal website

Property photos

Enough when the property is finished and photographs well.

Vecom Experience

Rendered viewing

Worth it when it is not built yet, far away, or you want to pre-qualify leads.

Normal website

Classic company site

Enough — and right — when customers should call: trades, practices, workshops.

Vecom Experience

Motion and storytelling

Worth it when you sell a mood: hotel, winery, brand.

Normal website

Image gallery

Enough for true one-offs — a used car wants real photos.

Vecom Experience

Configurator

Worth it with many versions: colours, sizes, materials, equipment.

Pixel Streaming

High-end graphics on a phone, too

A server in a data centre computes the image and sends it as video. Your visitor steers with a finger — their device computes nothing.

  1. Server

    A graphics card in the data centre renders the Unreal scene.

  2. Stream

    Finished frames travel as video, touches travel back.

  3. Phone

    Shows the image and sends swipes and taps back.

To be honest: a stream costs money every minute. That is why it never starts by itself, only on a click — and for the villa on this page, for now, only by appointment.

Back to the home page

Message me