MVR Import

Hi there,

Has this process been resolved in some way? I never had a problem importing using the VW plugin and VW2022, but cannot get the VW Export MVR -> EOS Import MVR workflow to work - same problem as Rob above. Can someone from ETC make a tutorial video showing this?

Thanks, 
Rick

RickPM 

As there are many different issues mixed in this thread would you mind pointing out which problems you can see as well? Please also state what software version you're using (numbers please, rather than "the latest one"). If you can provide the MVR file that would help as well. If you don't want to post the file here you can can send it to eos(dot)moderator(at)etcconnect(dot)com..

x, y, z and rotation data do not import into EOS and have to be manually added. Exact versions listed above. The site won't allow me to upload a GDTF file, but it's the one from GDTF Share for the Elation Proteus Lucius: 2023-06-01 First Release. https://tinyurl.com/55vy27kx

A video tutorial would be really great.

Ah yes, sorry, didn't see the version. Got it now.

GDTF and MVR are not the same thing. GDTF is a fixture definition while MVR contains 3D model(s) and patch data, including xyz. If you import GDTF (possible starting with 3.2.4) there won't be any xyz data.

So sorry, I wasn't clear that I was coming out of Vectorworks 2023 SP7. On the VWorks website, they describe the process here: https://blog.vectorworks.net/getting-started-gdtf-mvr

So, I presume that if I add GDTF fixtures to Vectorworks lighting devices, add them into a design and in 3d model space, that the VW "Export MVR" command packages the 3d data into that export, no? The ETC plugin did this, but now that it doesn't exist for VW2023, what is the process to get VW 3d data into EOS?

A step by step video would really help here.

Thanks again,

Rick

In Eos 3.2 we added native support for importing your scenic model and your patch in one step via the Vectorworks MVR format. This replaces the old plugin.  As before, you'll still need to "map" the fixtures in the MVR file to Eos fixtures.

While MVR format can contain GDTF definitions, the MVR import function in Eos ignores GDTF to maintain the mapping process. So if you want to import GDTF, that is the separate import process. GDTF import was introduced in v3.2.4 and has some limitations which are outlined below:

https://support.etcconnect.com/ETC/Consoles/Eos_Family/Software_and_Programming/GDTF

Here's a workflow from blank documents - can you tell me what I'm doing wrong in VW2023 and EOS 3.2?

VW - new document, add Proteus Lucius

VW - give light x,y,z values, attach GDTF from GDTF Share, select extended mode, give a channel value.

VW - export MVR

EOS - import MVR, map fixture to correct personality

Augment3d - fixture does not appear, no x,y,z values have been imported

Very simply, this worked with the 2022 plugin - and now does not. Can someone describe the process so that I can successfully import into EOS Augment3d? It used to work, and now it does not as far as I can tell - I'm absolutely open to not doing it correctly, and eagerly wait for the step that I'm missing. Thanks again.

Here's a workflow from blank documents - can you tell me what I'm doing wrong in VW2023 and EOS 3.2?

VW - new document, add Proteus Lucius

VW - give light x,y,z values, attach GDTF from GDTF Share, select extended mode, give a channel value.

VW - export MVR

EOS - import MVR, map fixture to correct personality

Augment3d - fixture does not appear, no x,y,z values have been imported

Very simply, this worked with the 2022 plugin - and now does not. Can someone describe the process so that I can successfully import into EOS Augment3d? It used to work, and now it does not as far as I can tell - I'm absolutely open to not doing it correctly, and eagerly wait for the step that I'm missing. Thanks again.

So, an update after more attempts. Working in VW2023 SP7 and EOS 3.2.4 build 58. With any fixture, including stock ETC fixtures in either the Standard or Premium Libraries. With or without adding GDTF info in VW: The only information that transfers from a VW MVR export is the fixture type, channel and patch. x,y,z does not transfer nor does any database information (note fields, etc.). Focus information does not transfer, nor rotational information (position or orientation in EOS).

Can you please send the files you are using to the Eos moderator as they spoke above?

Thank you for providing the files.

I successfully imported your mvr using the default settings in the dialog:

This was the result:

Let's start by comparing the import settings. What options did you choose?

I've just tried your settings, except to say that they are not precisely the "default" for me: Beam, Position and Orientation default to IGNORE and when I choose automatic, they populate to Beam, Position and Orientation - it's not possible for them to show "(Automatic)" on an import like your screenshot. When changed to Beam, Position and Orientation, the import of these parameters does not succeed using the same MVR file that I sent to you.

OK! So, Deep Clear worked for me. The default settings now are identical to your screenshot and the import successfully brings in everything. Thanks for taking the time on this - it must be some bug in years and years of updating Nomad on this machine and never doing a deep clear. Thanks so much for the help.

Warmly, Rick

 eos moderator Not sure why the logs are showing that. Like Rick said those fields default to [Ignore] for me. I manually selected "Automatic" for each and they then filled in the names of the field, they do not say "Automatic" like on your screenshot. Still can't get XYZ data to import after another deep clear.

eos moderator Any other suggestions?