Consent

This site uses third party services that need your consent.

WORKING NOW RENDERING

The renderer: a believable rig in a browser, on the hardware you have

FlexViz is a 3D stage lighting visualizer and simulation that runs in a browser tab: beams, gobos, colour and the way they land on surfaces. The target is optical credibility. A designer should recognise their rig and trust what the beams are doing, on whatever machine the production office happens to have. Most of the work goes into keeping the picture reliable across those machines.

Live view at full quality: the demo rig with beams and haze.
WHAT IT DOES
BUILT TO BE TRUSTED AT A GLANCE
The goal is a rig you recognise and beams whose angle, colour and coverage you can judge. Leaving photorealism out is what keeps the scene interactive.
LIGHTING ATTRIBUTES FROM THE GDTF
FlexViz draws supported lighting attributes from the fixture profile, including colour wheels and mixing, gobos, iris, zoom and frost. Motor-speed, service and other non-visual channels are not shown in the renderer.
GEL COLOUR YOU CAN STILL SEE
Lee 181 Congo Blue takes roughly 98 % of the light out. Rendered literally, the beam would be correct and practically invisible. FlexViz darkens it hard and then stops, so the beam stays readable and the colour stays recognisable.
STAND-INS WHEN A PROFILE HAS NO MESH
A GDTF profile without geometry gets a generic body from a small library: PAR 64, a Source-Four-style profiler, an ARRI-L10-style Fresnel, a strobe and audience blinders. You choose which, once for these fixtures, the project or all your projects. The plan still reads correctly.
IT RUNS WHILE YOU WORK
There is no separate render step to wait for. The scene stays live while you patch, rig and move fixtures, and rigs of 80 or more fixtures run interactively on the test machines today.
HOW IT HANDLES YOUR MACHINE
THE FULL VIEW ONLY WHEN IT ACTUALLY RENDERS
A browser reporting WebGPU support only tells you the API exists. FlexViz requests the adapter and draws an invisible test frame with it. If that frame does not come back, FlexViz switches to the simpler view before you are standing in front of a client wondering why the viewport is black.
THE SIMPLER VIEW RUNS ON A 2013 LAPTOP
The simpler view is a complete renderer. It runs well on 2013 integrated graphics, so if the machine in the production office is older than the show file, it will still draw the rig.
WHERE THE TWO DIFFER
Beams are the one visible difference. The full view raymarches them; in the simpler view that would cost more performance than it returns, so beams are drawn with a lighter technique and look somewhat different. The rig, the patch, the plan and the colour are the same scene either way.
MEASURED IN FRAME TIMES
Renderer changes are judged on frame times and 95th-percentile figures, and kept or reverted on that evidence. Published numbers follow once the beta measurements are stable.
WebGPU render of a dark stage in haze: moving heads on three truss runs, soft volumetric beams, a gobo breakup on the floor
The same view on WebGL2: the beams drawn as narrower cone shells with sharper edges, the same gobo breakup on the floor
The same saved view, once in the full view and once in the simpler view. Drag the divider: the rig, the colour and the gobo on the floor match; the beams differ.

Depends on

A current browser. A reasonably current graphics card gets the full view, drawn with WebGPU. The simpler view, drawn with WebGL2, runs well on the integrated graphics of an Intel 4th-generation Core at 1.20 GHz, a laptop chip from 2013.

Not yet

FlexViz does not aim for photorealism; it is not Depence in a browser. Beams look different in the simpler view, because it skips raymarching. How many fixtures run at what frame rate on which hardware is being measured in the beta, and this page will state it once the numbers hold.

Open your own MVR against this and tell me where it breaks.