Jump to content

Mark Eli

Vectorworks, Inc Employee
  • Posts

  • Joined

  • Last visited


23 Great

Personal Information

  • Occupation
    Training Content Specialist
  • Homepage
  • Location
    United States

Recent Profile Visitors

2,398 profile views
  1. Mac OS can be a little weird with network interfaces. If you're on a wired connection, for example an ethernet cable plugged into a dongle that's plugged into a USB port. Shut down Vision and the Nomad software, then disable the wifi, and restart the software. For whatever reason, Mac OS will only show one interface if two are available, and it will always be the wrong one. If you're on wifi, make sure you're connected to something. Any kind of router/AP should work, and it doesn't have to be connected to the internet. When there's no connection, the OS disables all the network interfaces, including the loopback which is how EOS talks to Vision.
  2. I think this is a combination of two things. The VL5 was originally created for version 1 of Vision, and used systems that have since changed to simulated the external dimmer Kevin pointed out. This is why the fixture is always on in Vision. So it will need to be updated in the future to include dimmer control. As a work around, I'd suggest using the VL5 Arc, which has an internal dimmer. The color will probably be different, but the modes and channel assignments are the same. The second part is with how MA deals with these types of fixtures. I don't know much about MA3, but I do know a bit about MA2. From the look of things, they handle external dimmers the same. In your screenshot on the left, you see Patch1 (1.059) and Patch2 (1.060). Assuming it's the same as MA2, Patch 1 is the external dimmer, and Patch 2 is the rest of the fixtures functionality. So it's assuming the dimmer takes 1 channel, and the rest of the functions take another 13, making the footprint 14, even though the actual fixture is only 13. You should be able to set both Patch 1 and 2 to 1.059, which should make things line up correctly. On MA2, it does show an error when I do this, but I ignored it and everything worked as I'd expect. Alternatively, you can use the VL5 Arc profile if it's available.
  3. Unfortunately this is a bug. I'm not totally sure what's causing it at the moment, but I will be submitting a ticket so we can get it fixed. @mherslandI've tried everything I can think of, and I haven't been able to make any geometry disappear. If this keeps happening, please do let us know so we can look into it further. I have found a workaround for working for the fixtures you and @Ben59 mentioned. It may actually be an easier workflow for you. You'll create an empty file with empty layers that have your transforms set. When you open a new or modified file you're working on in vision, you'll merge in the file with the layer transforms by using File>Merge. Then drag and drop the fixtures you want to have dmx xforms into the layers. So you'll still have to assign all 81 xforms to 81 layers, but you should only need to do it once, and then after you can drag and drop. Just in case I'm explaining this poorly, I've made a file as an example. You should be able to merge this file into any other file, then move any fixtures or geometry into the layers and each layer is individually controllable. XFormLayers.vsn
  4. I'll have to investigate if some fixtures not being transformed is intended behavior or not. I don't think it is, but first I'll have to figure out exactly why it's happening. The recommended workflow is, as @TomWhiteLightsaid, using layers. It's faster and easier to work with all around. Using layers also gives you the ability to nest transforms of all objects or subsets of objects within the parent layer, so it has quite a bit of flexibility. As for objects disappearing, I have not been able to replicate it. It could be something specific to the geometry you're using, or something I'm doing different. I'm not really sure. I have way more questions than answers, if you can share that specific file it would definitely make replicating the issue easier. If you're not comfortable sharing it on the forum, feel free to email us directly tech@vectorworks.net If neither is an option, I have a lot of questions. It looks like you were already sending DMX to the X channel when you entered the Delta X, what happens when you pull that channel to zero? What happens of you change the Delta X to something higher or back to zero? Does changing the Delta Y instead of X have the same or different effect? Did this happen with any other objects, or possibly it happens with all the objects with the same geometry? Does it happen after restarting your computer? In general using layers instead of manipulating individual objects should keep you moving forward in any project you're currently working on.
  5. This happens with some GDTF files. Basically what's happening is that the light emitter is behind some part of the geometry. There's a couple of ways to fix it. The quickest is to, in Vision, select Root in the Scene Graph. Then in the Properties window, in the Globals section, change Render Shadows from True to False. The good, it's quick and easy. The bad, it turns off shadows for all the geometry in the scene. Another options is again in Vision. Go to Edit>Vision Preferences. Then under the Graphics tab, change Dynamic Shadows from Objects & Fixtures, to Objects. This will turn off shadows for fixtures. Meaning that your geometry will still have shadows, but your fixtures will not. Again, this effects all fixtures, not just the ones you're having issues with. If you're finished with your design and don't think you'll be updating it too much more, you can also fix the individual fixtures. Click the arrow next to the fixture names to expand the tree in the Scene Graph. In this example I'm using the P18MK2PRHC, and I've expanded unit 103. Select the Beam (Mesh) in the Scene Graph, then in the Properties window, change the Visible option from True to False as shown below. You can expand and select the beam mesh of multiple fixtures at the same time by holding the Control key on your keyboard. Then changing the visibility. After you've done this for all the effected fixtures remember to save your file. The beams may not update immediately. So if you change the visibility to false and nothing happens, don't worry. Move the fixtures pan or tilt, which will update the beam, and all should be good. Last, you can try editing the GDTF file to try to fix it. On windows only you can right click the fixture in the Scene Graph, and select Update Fixture Type, which will open a window to edit the fixture file. Unfortunately, I'm not sure what exactly is causing the issue, so I can't tell you what needs to be done to fix it. But, if you have the time and want to try, GDTF gives you that flexibility.
  6. The P18 is not currently in Visions library. However, it is available for download on the https://gdtf-share.com/ website, which can be used in Vision.
  7. In Edit>Vision Preferences, make sure your texture quality is set to high. IIRC that is a requirement to use alpha textures, and Visions preferences don't carry over from one version to another.
  8. Hey Jesse, In the properties window, uncheck the "Use Alpha Channel" box. I'm not sure if it's intended to be that way or not. Either way, setting use alpha to false makes it look correct for me. Let me know how things work out for you.
  9. @Jesse Cogswell is correct, to use MA-Net2 you'll need a Vision dongle. Artnet and sACN will work with both a dongle or serial number. For MA-Net3, you'll need the MA vis-key. Your distributor or customer service can assist you in switching to a dongle, if you decide you need it.
  10. Yeah, Artnet has always been a bit of a pain to set up. If it's not something you want to deal with, I wouldn't blame you. My thought process is always to try to narrow down possible causes. If Artnet works as expected, at least we know it's specific to sACN. If it doesn't, then we're probably dealing with some outside cause. At least that's the idea. Whether or not it's worth the effort to do that, is entirely up to you. One thing you may try, the DMX Viewer is in the Vision Program folder. It's a standalone application, so you can launch it without starting Vision. That's why it doesn't default to the DMX provider that Vision is set to. The two programs are essentially unaware that the other exists. By starting the viewer without Vision, it should do two things for us. If Vision is somehow causing the issue, Vision isn't running to cause it and the viewer should see the sACN stream. If Windows is blocking the viewer from working because it's being launched by another application, starting the DMX viewer directly should stop that. If it still doesn't work, then the only real possibility is some kind of third party interference, or the MA3. Yes, I agree the idea of the MA having weirdness sounds crazy. It's far from likely, but it is a possibility. MA3 is still very new, and new things love to do unexpected things. I've actually had a similar situation in a personal project several months ago. I was using sACN in a program I was writing, and Vision wasn't seeing the stream and neither was the viewer. I did the exact same thing you did, and fired up sACNView, which saw the stream without issue. Unfortunately, it's been long enough ago I can't remember the exact cause. From what I remember I had set one of the bits high when it should have been low or something similar. Either way it was enough that the DMX Viewer had decided it wasn't an sACN packet and ignored it, but sACNView had no issue. Obviously, the MA engineers do a way better job than I do, when I'm goofing around on the weekends but, anything is possible. One of our guys should have an MA3 now. Hopefully he will be able to either reproduce the issue, or give us a different perspective on things.
  11. Please contact support at tech@vectorworks.net so we can look into this further.
  12. Try running the VisionUpdater in the Vision2021 application folder. Win10(default) C:\Program Files\Vision 2021 Mac Applications>Vision 2021 If that doesn't fix the issue, please contact support so we can provide you further assistance.
  13. Hey AJ, Could you try setting vision to artnet, and then launching the DMX viewer with sACN? So, you'll have Vision set to artnet, the DMX viewer set to sACN, and the MA sending sACN as you have been. I'm wondering if something is causing Vision and the DMX viewer to be looking at different things. In the past I'm seen Vision not be able to pick up an interface because a third party software had taken exclusive control of it. Essentially, I'm wondering if something is blocking, and/or not sharing with, the DMX viewer, and the easiest place to start is by getting Vision out of the way. If you still don't see any DMX in the viewer, then it's either a third party blocking the viewer or something funky with the way MA3 is sending sACN. If you switch everything to use artnet, that should probably give us a better idea of what's going on. If the viewer is still not showing anything, it's most likely a third party issue. Antivirus, firewall, windows UAC, or maybe some other DMX monitoring software you have. Windows loves to block things without notification. If it operates normally, it's probably something with the MA. Sorry if this is kind of all over the place. These kinds of issues are the worst to troubleshoot, because there's so many variables.
  14. Hey Thomas, Which fixture are you having issues with? It could be an issue with your library, but it could also be an issue on my end. In Vectorworks, you can assign any fixture mode to any lighting device by selecting the "Other" option in the fixture mode dropdown box in the OIP. When you select Other, you'll be given a dialog with all the fixture modes in Vision. You can then either pick from the list, or use the search bar below the list. If you don't see the fixture modes in the dialog, there's an issue with your library. If you do see the fixture modes, it's probably a typo on my part and I can fix it. Thanks, Mark
  15. Hi Mark, When I checked the fixture on my end and everything looks to be working as expected. I'd start by making sure your library is up to date by going to Help>Update Library in Vision. Also, it's never a bad idea to double check that your patch is correct, both in Vision, and in your console. If you still can't get them working, please contact support directly Tech@vectorworks.net so we can provide further assistance.
  • Create New...