Consent

This site uses third party services that need your consent.

ROADMAP

What I am building next

This page follows the features I am planning and building. Items move between horizons as priorities change, and most carry no date. Target versions are planning goals, not release commitments.

Loading votes…

IN PROGRESS

In progress

Actively being worked on right now. No release date is implied.

  • No publicly announced items in this horizon yet.

COMING SOON

Coming soon

Prioritised out of Exploring and intended to be built next. Not necessarily started yet.

  • Generate Paperwork from the Scene

    Generate Paperwork from the current version of the Scene. For people that want to have a pile of paper at hand. Picking Lists, Plans, Patchlists.

EXPLORING

Exploring

An idea we find interesting. Whether and when it gets built is still open.

  • Catch planning mistakes before the truck leaves

    FlexViz checks your scene for the mistakes that cost time on site: missing patches, duplicate DMX addresses, universe overflow, missing GDTF data and broken rigging hierarchies. Every finding is listed with a severity and takes you straight to the object that caused it.

  • See what actually changed between versions

    Version history in the language of the job instead of a raw file diff. Since version 12, four fixtures were moved, two were replaced and universe 3 was re-patched. Changes are grouped by object type and position, so you can see at a glance what a revision really did to the plan.

  • One plan, the right view for every role

    Designer, operator, crew, rigger, production and client each see the same scene with the layers, labels and level of detail their job needs. A role can be set on a shared link as well. One source of truth, instead of a separate document version for every audience.

  • Bring in a new MVR without losing your work

    When an updated MVR arrives, compare it against the scene you already have instead of importing over it. FlexViz matches the objects and shows what was added, removed, moved, re-patched or changed type, and you accept the changes one by one.

  • Swap a fixture and see the consequences first

    Replace one fixture type with another across the whole plan and get the impact report before anything is written. DMX footprint and patch consequences, dimensions, weight, power draw and the feature differences that matter, such as zoom range, gobos and colour system.

  • Turn a technical rider into workable data

    Read a technical rider and get its stage plot, input list, power, backline, monitoring and lighting requirements as structured data you can plan with. From there it can be matched against the venue, turned into a first draft plot and paperwork, and diffed when the next revision arrives. Every extracted item stays traceable to its page in the source document, and anything the rider does not state is marked as unknown rather than guessed.

  • Power distribution as a real network

    Model supply, distro, circuit, cable and fixture as actual connections in the scene rather than as notes on a drawing. On that basis FlexViz can derive cable runs and a cable schedule from the geometry, and show load per circuit, voltage drop and phase balance. Please note. This is planning support only. FlexViz performs no electrical inspection, no certification and no assessment of standards conformance, and does not replace a qualified electrician.

  • The numbers your rigger asks for

    Weights per fixture and accessory, device and truss positions, motor positions and aggregated point loads per hang position, in a form you can hand to a rigging specialist. External results can be attached to the plan and stay linked to the version they were approved against. Please note. This is information for external professional planning. FlexViz performs no structural analysis, states no permissible loads and gives no rigging sign-off.

  • Ask your scene, from your own AI tools

    An MCP server for FlexViz, so the AI assistant you already use can reach your scenes. Ask what is patched on a universe, whether anything collides, what a rig contains, or why an import dropped half its meshes, without clicking through the editor for the answer. The first version is deliberately read-only. Access is scoped per organisation, revocable, and goes through the same permissions as the browser, so an assistant can never see a scene you could not open yourself.

YOUR INPUT

Missing something you need on a job?

Votes show me what matters most to you. They inform planning without promising implementation, dates or versions.

Suggest a feature

Suggestions go to the FlexViz helpdesk, and I read each one. They do not appear here automatically or promise implementation.

Release notes in the blog →