Jump to content


Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Everything posted by klinzey

  1. @MWilson101010 The Vision console will only control the attributes of a conventional fixture that are not controlled via DMX.
  2. All the address fields sync. If you enter 2/101 into the Universe/Address field. The Absolute Address will update to 613, Universe 2, DMX Address 101. If you change any of the other fields, the other fields will update in a similar manner.
  3. The "FixtureID" field in the "Light Info Record" determines the default for the "Fixture Mode" if it exists. We do a simple string match search starting from the beginning of the string to match the FixtureID with the available Fixture Modes. If there is no match or partial match the fixture mode will be set to None. If you are having issues keep in mind that we match from the beginning of the name. So if the mode is "Vectorworks" -"Vector" will find a match -"work" will not find a match -"Vector1" will not find a match
  4. If you are a member of Vectorworks Service Select you should use the Spotlight Fixture Request Form. https://serviceselect.vectorworks.net/support/fixturerequestform otherwise you can fill out the fixture request form on the Vision page https://www.vectorworks.net/en-US/vision Please request a specific fixture mode in needed for each fixture. Active Vision Pro users receive priority service so be sure to include your serial number in your request so we can verify your license status.
  5. We believe this happens in some file contains more than about 10 Label Legends in the document. You should see the fix in an upcoming service pack. VB-167028
  6. Since NDI operates in real time you can not export a movie from Vision and have the NDI input sync to the recorded DMX. You can do 2 things, If you don't need super high quantity you can use screen recording software or an external capture device to record the screen. (This is how we make most of the instructional videos.) If you need higher quality your best option is to convert the NDI stream to a video file and use the video file as the source. Vision can sync the video file when exporting to a movie.
  7. No. It's probably better to use sACN is you have the command wing.
  8. Check the permissions on your plug-ins folder. By default the entire application folder is read-only.
  9. @fuberator We are searching our office for similar hardware so we can test and see if it's something hardware specific. One more thing to try. Try switching out of dark mode. If it works OK then try switching back to dark mode and see if the problem still exists. There was a strange issue with dark mode that solved itself by going into light mode and did not return when we switched back to dark mode.
  10. @TomWhiteLight This may work but probably will not stay when the object is modified. The object looks to the settings created by the menu command because there are multiple text objects with different attributes in the same object.
  11. This is a global setting for all the hoists in the document. In the Default Spotlight workspace the text size for the Hoist Number and the Dimensions are set with a menu command. Spotlight>Hoists>Set Hoist Number and Dimension Display.
  12. @fuberator Make sure you don't have a dialog, like the Vision Preferences, open in the background. Several dialogs in Vision put you into a restricted view where you can navigate but not switch tools. Does this happen all the time or only when lights actively changing in the scene? What connection protocol are you using? Do you have any other applications running? Try opening up one of the demo files included with Vision and play the pre-recorded DMX. Make sure tools work correctly in the sample files. If everything works correctly in the demo file then please contact tech support and send them your file with some dmx recordings if we need them to reproduce the problem. We have tested on the same OS you are running but not on the same hardware. If you have issues running the demo file let us know and we will see if we can reproduce the issue on similar hardware.
  13. You should use a house light symbol for each dimmer and then assign each house light to the same channel. Wat you are really doing is assigning the same channel to multiple dimmers that same way you would do it in a console. Typically when I draw a venue I will place the houselights in the correct location and assign them to the proper dimmers, circuits and channels. This way if I change my mind and need to have more control I don't have to go back and figure out how the lights divide out.
  14. I haven't seen the error before. It's probably something specific with your file. Can you post it here or contact tech support so we can investigate your file further to determine the problem?
  15. The data mapping was removed in 2020 because of the implementation of DMX patching and other features. Since certain data is required to be in specific fields we could no longer support variable filed mapping. Exporting to MVR and Vision have specific filed use requirements that are listed the documentation.
  16. I did a quick check in 2020sp2 and it looks like it's still an issue. I could not find the issue in our system for this specific problem so I created one so we can take a look at the problem. You can reference VB-166672 is you have any further information to add the the issue.
  17. Can you post the file or a sample showing the problem?
  18. What is the beam and field angle of the instrument? I usually see this when the angles are set to 0.
  19. There is no zoom control in Vectorworks, you simply enter in the desired beam and filed angle into the OIP.
  20. No, "Send to Vision" still uses the .esc format.
  21. @tw0fer Can you post the file or a sample that shows the problem?
  22. @DBLD Dan, Someone in the office was having the same problem this morning. We tracked the issue down to having some extra folders inside of Vectorworks. Take a look in C:\Program Files\Vectorworks 2020\Vision\ If there is a Gobos and/or Library folder, delete them and launch Vectorworks. Vectorworks should now use the same resources as Vision. Let me know if this was your problem and we will do some more testing to figure out how those folders got into that location.
  23. By default beams take on the color designated by the "Color" field in the lighting device. You probably have the color set to a shade of red.
  24. @James H. There is a class setting for the beams in Spotlight Preferences.
  25. @O.P.S. Take a look at the information here: DMX Connectivity Articles The articles were written for earlier versions of Vision but the same information applies to the current version of Vision. Because MA and HES have not updated their installers in a long time we heard of some users having issues after installing the drivers because they over-write some of Vision's newer files. So if after installing the drivers you still have issues run the Vision Application Updater and select the repair option.


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...