Jump to content

Mark Eli

Vectorworks, Inc Employee
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Mark Eli

  • Rank
    Greenhorn

Personal Information

  • Occupation
    Training Content Specialist
  • Homepage
    https://www.vectorworks.net
  • Location
    United States

Recent Profile Visitors

966 profile views
  1. You probably missed it because, once you have a fixture mode selected, it removes the text box and reads the footprint from the vision fixture profile. I usually scroll past it at least once while looking for it. I've highlighted it in this screen shot for you. If you're ever unsure about a fixture profile, you can email tech@vectorworks.net, and we'll be able to answer any questions you have.
  2. Just in case someone else comes across this post later, I can help with most of this. At the time the VLZ Profile was added to Vision, there wasn't a 56 ch mode. This is actually pretty common. On the Varilite website, you can check their DMX Map in the downloads, and it's version 2.01, which is a good indication changes were made. If you put in a fixture request for the mode, I can add it in for you. Unfortunately, this is the one bit of bad news I have for you. Vision does not currently support HSI fixtures. So I won't be able to fill any requests for those fixture modes. It's not that I don't want to, it's that there's no way for me to replicate it in Vision. Looking at the VL 1100 TID profile in MA2, and the VL 1000 T-TI in Vision, the profiles look the same so I don't think you'll have any issues there. The mac TW1s are kind of oddballs. They supported an external dimmer which, at one point, we replicated in Vision, and that's what the extended mode was. In the future we will again, which is why they are still in the library. As for seeing the DMX footprint, that's already available just in a different way. In Vectorworks, once you've selected a fixture mode, the object info pallet will show the number of channels used under DMX Footprint. In Vision, if you select the fixture, either by selecting it in the viewport, or selecting it in the Scene Graph, it will display the footprint in the Properties Window, under Num Channels. In the future, once GDTF is implemented in Vision, you'll be able to view, edit, and create your own fixture profiles. So, that is in the works.
  3. LJ is correct. Since MA makes the driver, we have no control over what it does, or when it gets updated. I forget exactly what the MA driver is doing that's outdated but, I think it was a registry entry and maybe one of the DMX provider files on the Vision side. At one point we did have the driver installer bundled with Vision, but we removed it because it's a third party's property. That is correct, the MA requires the use of a dongle instead of the normal serial number, to be able to use the driver. Your sales rep should be able to help you get set up with a dongle.
  4. Ok, the only other option I'm aware of, is that the MA driver overwrote something during its install. The easiest fix is to reinstall Vision.
  5. After installing the driver did you setup the driver? The driver doesn't actually start working until you set it up and run it. You'll need to go to the Windows Control Panel, and select grandMA - ESP Vision Driver. By default the control panel is set to Category which won't display the MA driver, so you may need to change to icons at the top right by View by. Once you select the driver, in the window that comes up, you'll change the MA-Net Mode to MA-Net2(unless you're using an MA1) Station IP Address you'll set to 127.0.0.1 if you're using MA2onPC on the same computer that you're running Vision on. For any other setup, like an actual console, you'll pick whatever the other option is. It's different for each setup. Then for MA Session ID, you'll set that to whatever is in the MA, default is 1 for the driver and console. Then press Ok, and start Vision, you should see grandMA in the DMX Provider dialog.
  6. Hi All, I've made some adjustments to the encore. You'll need to update your library in Vision and then restart the program to see the changes.
  7. Fixtures are released for Vision as they're completed throughout the day/week. There's not currently any logging of what gets added, and there's nothing in place to be able to track it.
  8. Hi All, I just wanted to pop in and give a little clarification here. Brandon is mostly correct here. Most, Vision fixtures that do not have moving heads are modeled as hung. In this particular case, it is not. As Brandon has said, the exporter looks for moving heads and flips them. Everything else is left alone, which is what's causing your issue. That particular fixture, needs to be flipped during the export, but isn't. So the quickest and easiest fix is the one he described. Here's a bit of extra detail in case it's helpful. In Vectorworks, select all of the fixtures that are being exported incorrectly. In your case, the SGM P-5. Under the Shape tab of the Object Info Palette, the first data field under the Edit button is the Device Type drop down box. By default, it is set to Light. Change that to Moving Light as highlighted here: Vectorworks may take a moment to update the OIP, once you've selected Moving Light. When it does, reexport your file, and open in Vision. All of your P-5s in Vision, should now be oriented to match Vectorworks. I've attached my test file as well. I've set the right fixtures Device Type to Moving Light, and the left to Light, so it should be easy to see the difference. P5 Orientation.vwx Hopefully this helps, Mark
  9. Hi Liam, I'm sorry to say I haven't tested with Vista in quite a few years, and when I did it was still V2. That being said, iirc it worked at the time. Generally speaking, if the offline editor outputs Artnet or sACN, Vision should be able to see it. The only thing you might have to watch out for is, if Vista is picky about it's IP addresses. At one point, having the correct IPs was a major issue, but in recent years offline editors and consoles have become more capable of adapting to whatever your computers IP happens to be. For specifics, you'll need to check Vista's documentation. Beyond that, there shouldn't be anything other than the editor that needs setup. Thanks, Mark
  10. Hi @GloriamLT I'm going to jump in real quick and try to get you pointed in the right direction. In the real world, a console is how you control lights. There's a bunch out there, so take your pick. I can't teach you how to use any of them, because they're all different and, that's why we have youtube. So the console and the lights need to be patched, this will be covered in most console tutorials. The important part is that the console and light need to have matching patch information. Beyond that, you're going to need to do some research on how all these things work together in the real world. As for using Vision, you'll build your scene in Vectorworks, and then export it to Vision, assuming you have a license. In your case, since you're using the demo, you can still use the scene you've made but, you'll be limited to 5 lights. Vision acts the same as a real light. So you'll need a console to control the lights in Vision, the same as you would in the real world. Also, just like the real world, the patch information that's in vision for each light needs to match what's in the console. I can see from your picture of the patch window that your patch information isn't exporting correctly. That's why there's a bunch of lines highlighted in red. What you'll need to do to correct that is go into Vectorworks then go to File>Document Settings>Spotlight Preferences and a new window will pop up. Click on the Lighting Device tab if it isn't already selected, and then click the bottom right button labeled, Edit Visualizer Data Mapping. This will give you a new dialog box with a bunch of options. The only ones you really need to worry about are the ones labeled Universe and Channel. This is how you tell Vectorworks and Vision where to find the patch information in Vectorworks. As a guess, judging from the picture of the OIP you posted, you'll want to set Universe to Universe, and Channel to Address. Then send your file to Vision again, which should give the lights the correct patch information. As for getting the patch information from Vectorworks into the console. In the case of QLC, and most others, there's no way to do that. Patching is usually a manual process. So, once again, google some videos, there's lots. Also, here's a link to our getting started guide, which may give you some additional insight into how vision works. https://www.vectorworks.net/training/2019/getting-started-guides/vision/what-is-vision
  11. That looks like you've got some Z fighting going on. Basically, two faces of the geometry are in the same place and fighting to be the one that's being rendered. You'll have to find whatever geometry isn't your screens and either move it, or delete it.
  12. hey Mark, I've tried putting this fixture request through your link on this page as well as through the service select portal but neither seem to be going through.. so here is my request: 

    We need to add all three PRG Ground Control Followspot fixture profiles into Vectorworks as well as Vision please:
    Bad Boy
    Best Boy
    Super Ray

    Currently, none of these are in the Vision profile library so you can not export them to Vision

     

     

     https://www.prg.com/technology/products/luminaires/groundcontrol-followspot-system

     

    thanks!

    Vickie

  13. Hey Dan, As a guess, there's probably an antivirus or firewall somewhere blocking the update. It could also be the user account control. Microsoft has done a lot of weird things with permissions and a lot of settings can get changed when they update. If you could, send me an email tech@vectorworks.net and I can send you some instructions for updating manually.
  14. Hey Robert, You're using the Sunstrip Active, which doesn't have dmx controlled rotation. You want the Sunstrip Pro which does. Easy fix though, you should be able to just change the fixture mode in the OIP in Vectorworks and reexport.
  15. Hi Anthony, unfortunately because of the issues currently present with visions capture card functionality, we don't have any verification on which cards are working and which aren't. For the moment, because I can't say capture is working for everyone, I'm going to say, this isn't working at all. As much as I hate saying it, I'd rather tell you that, than send you down a rabbit hole that you might not find the bottom of. I've been told it's on our list of priority fixes, but I have no information on where exactly they are in the process.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...