Jump to content

klinzey

Vectorworks, Inc Employee
  • Content Count

    1,622
  • Joined

  • Last visited

Posts posted by klinzey


  1. First, make sure you running the 2019 SP3 versions of both Vision and Vectorworks.

    If there are missing lights in your ESC that is usually an indication that the fixture mode is not set. We try to default to an appropriate mode but some fixtures have no default mode.

    If you are still having issues please contact tech support directly.


  2. 2 hours ago, Gaspar Potocnik said:

     

    If this is the case, and vision won't convert units, then it should be stated somewhere, either in the dropdown, special pop up or something. Coming from VW were you can use any unit anywhere and the app will convert it, it makes no sense to be given an option to change units but only millimeter will work. 

    Vision only operates in inches. In the dialog you are selecting the unit measurement used by the file being imported so it can properly be converted to inches. Regardless of the units used by the application the MVR file will always be stored using millimeters by the current MVR specifications. In future versions we will disable the units option when importing an MVR file. (Earlier versions of the MVR specification did not specify the units so we had to account for different types in the import dialog till the 1.0 specification was adopted by everyone.)

     

    Right now the units selection is similar to the units selection in Vectorworks when you import a DWG/DXF file. When we see an MVR file and we default to millimeters and we are correct 99% of the time but since there could be an MVR file from another application not following the new standards we have to allow you to change the units just in case.


  3. Great! By the specifications, the MVR file always uses Millimeters for the units.

    The Vision import dialog supports multiple file types so the units option is always available.

    We are looking at forcing the units setting to Millimeters when you select and MVR file but for now you will have to remember to always use Millimeters with MVR files. 

    • Like 2

  4. First be sure you are using SP3 of both Vision and Vectorworks.

    Can you post your file here or submit it to tech support and we can take a look?

    We have done extensive testing with MVR but it is still a new and developing format  and you may have found a situation that needs some more attention.

     

     

    • Like 1

  5. @Keylight The suggestion @Robert Anderson will work for new documents.

    To fix your template file activate the Soft Goods tool and then in the modebar click the wrench icon.

    This will open up the properties dialog where you can set the default options.

    Click OK and now the tool will place objects with these defaults.

     

    This settings button should be available for most tools.

     


  6. A quick look at one fixture focused on Table 16, Table 2 in the file shows the fixture Z height at -15' and the focus at 0'

    If you look at the file in elevation you can see a lot of things at varying Z heights.

    Since you have layers at different layer elevations your objects are ending up at different overall heights than you expect.


  7. @jcbw You probably chose not not convert non-hybrid and selected "Always do" in the dialog at some point .

    You can reset the action from the Vectorworks Preferences > Session tab, click the Reset Saved Settings... button.

    Check "Always do..."

    Click OK.

     

    This will reset this dialog and all "Always do" dialogs to display again.

     

    You should also create an 1 1/2" x 25'  rectangle, group it with the extrude and then convert.

    This will create a hybrid object that can be viewed in 2D and 3D.


  8. In Vision it's all done in the Properties Palette.

    http://app-help.vectorworks.net/2019/Vision/index.htm#t=2019_Vision%2FVision%2FThe_Properties_Palette.htm&rhsearch= emissive&rhhlterm= emissive&rhsyns=

     

    With the object selected expand the "Emissive" group.

    Enter "RGB" for the Fixture Type, and specify a Fixture Candela value as well as Fixture Universe and Channel number.

    This will set the object color to be controlled by 3 channels R,G,B.

    You just have to select or make a simple 3 channel RGB fixture profile in the console.


  9. If you are not rending the spheres in Vectorworks you don't need to make them into lighting devices.

     

    The best thing to do is to make a symbol out of the sphere and simply place them as symbols.

    Be mindful of how you create the sphere and your 3D conversion resolution settings. The performance of various types of 3D geometry for a sphere can be very different.

     

    Once you export into Vision you can select the geometry and set them to be RGB emmsive objects.

     


  10. You probably checked the "Always do" option in the dialog so it will always do the option you selected the last time the dialog was displayed.

    From the Vectorworks Preferences > Session tab, click the Reset Saved Settings... button.

    Check "Always do..."

    Click OK.

     

    This will reset this dialog and all "Always do" dialogs to display again.

    • Like 1

  11. We recommend selecting "Use Geometry" for compatibility with Braceworks and MVR. Both systems rely on having unique geometry and identifiers inside of the hanging position in order to properly process the hanging position. If you are not using Braceworks or MVR as part of your workflow it's safe to select "Create Symbol".

    • Like 1

  12. @Benjamin Weill I can't reproduce your problem in a simple test file.

    You can set the default label legend in the label legend manager.

    Place a check-mark in the active column next to the label legend you want to use as your default.

    Since you are getting <None> you probably don't have anyone marked.

     

    I have seen some very old files where I have had to do this twice to get the choice to stick. So if it does not work the first time open the dialog and try it again.


  13. The video format should be a simple avi file. [YUV format using the  DV Video, MPEG-4 (XVID) codec]

     

    We texture map the video based on how the image is texture mapped to the object, so the image you use in Vectorworks should be the same size as your video.

    Vision does not allow you to do any texture mapping so it all has to be done in Vectorworks.

     

    The "Vision 2017 Demo" in the "Demo Documents" folder contains a sample using a video file if you want to take a look at a working example.

    It uses the firecinepak_xvid.avi found in \textures\scene\ folder.


  14. The problem is likely your source image. Just like a real gobo, your source image needs to fit within the circle generated by the light.

    It's a little hard to tell because your image is also a rectangle but if you look you will see that your missing areas are clipped by the circular light.

    The overall image must be square.

    We recommend a 2"x2" square with black filled to the edge and then a slightly smaller circular area for the image area.

    Image Area.jpg

    A lot of gobo shift would work but you will then start to see light bleed around the gobo image.


  15. You have to specify a Vectorworks texture.

    Specifying a dds, jpg etc. image files will not work.

    If the Vectorworks texture does not already exist you can use the Create Gobo Texture command to create one from the image.

     

    P.S. dds files are obsolete and not supported by Vision on Vectorworks. dds files are automatically replace with jpg by Vision.

 

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.

×