Import an MVR

Open File › Import › MVR. The wizard has five steps — File, Layers, Fixtures, Summary and Import — and nothing is written to your project until you reach the last one, so it's safe to explore before committing.

1. Choose a file

Drop an .mvr file onto the wizard or browse for one. Nothing is written until the last step.

Once a file is chosen, the right-hand panel shows what it contains — how many layers, fixtures, 3D objects and distinct fixture types, along with the file's size, MVR version and what created it. Anything the panel can't bring in is called out here too — a file with 8 × Truss objects it won't import, for example.

The File step of the MVR import wizard after a file has been dropped, showing its filename, size, and layer count. — A file loaded — its contents on the right

2. Layers

Every layer in the file is listed with its fixture and 3D object counts, all selected by default. Uncheck the ones you don't want — all and none are there to speed that up — and the panel on the right totals what's left: layers, fixtures, 3D objects, and how many distinct fixture types are involved.

The Layers step of the MVR import wizard, listing the MVR file's layers with their fixture and object counts. — Layers in the file, with fixture and object counts per layer

The fixture types list previews what's coming in the next step — you choose how fixture types without a 3D body are displayed there.

3. Fixtures

Every fixture type in the file gets a display choice: in file when the MVR already carries a usable GDTF profile, or a toggle between Stand-in and GDTF Share for the rest. A stand-in draws a plain procedural body sized from the profile — nothing is downloaded. GDTF Share replaces it with a real profile from gdtf-share.com, or a shortcut across to a matching profile already in your library.

When a GDTF profile has no usable 3D mesh, FlexViz says so and asks what to draw instead:

The Fixtures step of the MVR import wizard, showing the missing-mesh resolution flow for a GDTF fixture with no usable 3D body. — Resolving a fixture with no usable mesh — Mac Aura XB

4. Summary

A last look before anything is written: the layers table on the left, and how each fixture type will be displayed — from this file, from GDTF Share, or as a stand-in — with the source profile named where one was found.

The Summary step of the MVR import wizard, listing layers and fixture display choices with a validation warning about a fixture with no 3D body. — The Summary step, with a fixture that still needs a decision

A fixture type can fail here too — a GDTF Share match with no mesh of its own, say — and the wizard says so in red, right where the choice was made, so you can go back and pick another profile or fall back to the stand-in.

The panel on the right totals what will actually happen: layers, fixtures, 3D objects, and how many GDTF profiles still need to be downloaded from GDTF Share before the import can run.

5. Import

Press Import and FlexViz works through three steps: downloading any outstanding GDTF profiles, placing fixtures and scenery, and writing the scene.

The Import step of the MVR import wizard after completion, showing the import summary and a Download log button. — Import finished, with a per-fixture log to download

The finished screen totals what happened — how many fixtures imported cleanly, how many have something worth reading about, and how many couldn't be represented at all — and offers a Download log with the detail behind every one of them. It's the thing to send back to whoever exported the file if something looks wrong.