Search

Forum


MVR best practices
You are not authorized to post a reply.
Veteran Member
Posts:299 Veteran Member

--
2023-06-26 16:40

    What are best practices as it comes to using .mvr file exchanges (between Capture and Vectorworks).

    Should I only use Design Layers in Vectorworks?

    Should I move all my classes into design layers before exporting?

    Should I use normal Vectorwork fixtures or rather the GDTF ones?

    How about going back and forth between VectorWorks and Capture? If I change a channel number in Capture, how do I make sure it also changes in Vectorworks?

    I can do all this between Wyswiyg R48 and Vectorworks 2023 (latest servicepack).

    I know that you touched on this in one of the excellent video's, but that was only one way. In the dynamic of a design process we often need to go back and forth between the two programs.

    Floriaan Ganzevoort
    Lighting Designer - Theatermachine
    Veteran Member
    Posts:299 Veteran Member

    --
    2023-06-27 14:11
    Here’s what I plan to test in the coming days. I am really interested in what else you would like me to test. Please add your comments below.

    1. Original file created on Vectorworks using classes, import into Capture, change patch to other universe, add a layer with a new fixture type, import back into VW

    2. Original file created on Vectorworks using design layers, import into Capture, change patch to other universe, add a layer with a new fixture type, import back into VW

    3. Original file created in Capture, import into VW, change patch to other universe, add a layer with a new fixture type, import back into Capture.

    Extra questions:
    - Is there any difference in using Spotlight standard fixtures or fixtures downloaded from the GLTF database?

    - Is there any difference in fixtures that are in the libraries of both Capture and Vectorworks and those that are not?

    - Does the “use .obj” check make any difference?
    Floriaan Ganzevoort
    Lighting Designer - Theatermachine
    Staff Member
    Posts:2016 Staff Member

    --
    2023-08-14 09:13

    One reason we're not particularly inclined to dig into best practices is that this is field with a lot of changes happening between different software releases, not just on our side. Also sometimes best practices will vary depending on you draw things and what your objectives are. 

    There is quite a bit of information that MVR doesn't carry and you may work around in different ways that would break the workflow for someone else. Ultimately you will need to invest the time in trying to make what you need work.

    If the softwares you are going between were identical MVR would work much better - but then what would be the point of using different softwares?

    Technical Director
    Capture Visualisation AB
    Veteran Member
    Posts:299 Veteran Member

    --
    2023-08-23 22:37

    It would be great to use .mvr as a way to collaborate and to keep track of changes in a file. In my world the set department often draws in vectorworks and keeps making changes after I do my initial import into Capture. The need to know at some point where the lighting positions are, so we do an export out of Capture into VW again. How to avoid double items on top of each other? Then when we start plotting, a lighting desk is thrown into the mix and the patch will most certainly change. In the end all the data is archived in the master plot (sometimes VW with Moving Light assistant or Lightwright).

    I am looking for the best way to keep all the departments in sync and I was hoping mvr is the way to go. I understand this is not solved overnight, so I keep hoping all the partners in the consortium keep up the good work and continue building on the foundation that is already there.

    Floriaan Ganzevoort
    Lighting Designer - Theatermachine
    You are not authorized to post a reply.