Jump to content

klinzey

Vectorworks, Inc Employee
  • Content Count

    1,830
  • Joined

  • Last visited

Everything posted by klinzey

  1. You can PM me with the details but please let me know if the problem still exists in a new 2020 file. If it does please include your machine details and any settings that you may have changed from the default Vectorworks settings. We have not been able to reproduce the issue so it may be a problem isolated to specific hardware or settings.
  2. No. The lighting device will always decompose the symbol and the marionette node will be lost.
  3. This should no longer be a problem in 2020.
  4. The lighting device extracts the geometry from the symbol, so any special data or you have will be lost once the symbol is used by the lighting device.
  5. @Gaspar Potocnik A chart with how the fields are mapped is available in the help: http://app-help.vectorworks.net/2020/eng/index.htm#rhsyns= &t=VW2020_Guide%2FLightingDesign1%2FVisualizer_data_mapping.htm
  6. It's worked this way for at least several versions as far as I can remember. (I checked 2018 and it was the same.) "Draw Beam" will give you the outline with no fill, "Draw Beam as 3D Solid" will give you the fill when rendered. If you are just looking at in in wire frame both will appear to have no fill.
  7. Projectors in Vision and Vectorworks are not designed to project an image. Images and video can only be configured to apply to a surface. Both Vision an Vectorworks need the texture mapping on the screen surface in order to orient the image properly. The video screen objects allow you to properly orient the screen image. Select Vision Video Source is designed to create a screen surface from a 3D polygon, it can not be used with a lighting device. We plan to better support projectors in both Vectorworks and Vision in future versions.
  8. The fill color of the beam is set by the "Color" field of the lighting device. If the field is empty or contains an invalid value the beam is drawn in black. (I set the color to R26.)
  9. @zeroInf We have added support for the Scia version of the DTSV file with Braceworks 2020. Please let us know if you have any issues when using the export option in 2020.
  10. @Chris_W Remember the bounding boxes are square so you would need significant space to fit the last one in the first row because of the angles and it's intersection the right side. The other seat is probably being eliminated because it's crossing the line. If you look at the row you can see the far left seat is behind the line, the next seat is touching the line, the next seat is overlapping the line which means the next seat is probably even further over the line.
  11. @TReimann If you find something missing from the manual let us know and we will update it. This is a user manual and not a substitute for training. Vision has been lacking a training till recently. We recently released the first in a series of training courses for Vision. NEW- Vision online training seminar for people who need more than the basic information the manual provides.
  12. Vision has the same style user manual that is available for Vectorworks. It's accessible via the help menu or by pressing F1. It always going to be difficult for Vision to compete with "Free" software. If the programmer is happy with the rendering speed and quality they get from GrandMA 3D it's going to be almost impossible to sell them Vision because of the additional cost. The user needs to want something more or different than they can get from GrandMA 3D for them to even look at Vision.
  13. @Roccondil The problem you describe points to a missing Light Info Record on the 50deg symbol, When you imported a new version of this symbol it probably brought in a new version with the proper Light Info Record attached. You may have deleted the record if you chose to remove it from the inventory list at some point.
  14. Scia wants a special version of a DSTV that is slightly different than the standard DSTV. We are looking at exporting the Scia version of the DTSV file in a future version.
  15. This is working as designed. "Exit" is on exit from the dialog, not exiting the application. The option will be always be unchecked when you launch the dialog. Checking this option forces a full export from Vectorworks and causes Lightwright to reconcile with Vectorworks. Vectorworks will cause Lightwright to automatically reconcile if the data exchange file is bad or has been deleted and needs to be recreated.
  16. Other user's fixture modes and Vision fixture requests will de delivered via the Content Updater you can run from within Vision. They will also be delivered to other users with Service Packs of Vectorworks. Vectorworks symbol fixture requests will be delivered by updating the libraries available in service select which will automatically show up in the Vectorworks Resource Manager.
  17. @santmart New fixture modes can only be created by Vectorworks. If you are a member of Vectorworks Service select you can submit your fixture request here. https://serviceselect.vectorworks.net/support/fixturerequestform Vision users can using the link at the bottom of this page to request new fixture modes. https://www.vectorworks.net/en/vision Please be sure to specify the needed fixture mode.
  18. When you placed it in the document did it insert as a symbol or as a lighting device. If it inserted as a lighting device it may have the Parts record improperly attached to the geometry in the symbol.
  19. I've done it before and you just need to keep track of things very carefully. Give all the controls that don't change ID's before the ID of your dynamically created controls. (VW doesn't like it when you skip control IDs.) In the case statement make sure you have events for all of the static controls. At the end of the case statement you will need an OTHERWISE Here is where it gets tricky... You have to do some math to figure out which item the user clicked. You need to be sure the ID is greater than the last static control and less than the last control you created. In the simplest case you will probably have a label (item=N) and then the hatch control (item=N+1) You can setup your data structure when you create the dialog so that the dialog item is an index into the structure if you want to keep it simple or with a little more work you can convert the dialog item into an index into a more compact structure. As you are building the controls for the dialog you need to handle the first control placed after your fixed controls separately and then from then on you iteratively add controls once the pattern is established with the first control. Done right it works great but it is a little difficult to debug.
  20. This is strange. The insertion point of the lighting device should not change. Many tools use the bounding box center of the entire object. Pasting an object is probably going to use the bounding box center rather then the object's insertion point if you are pasting the object at a location. If you look at the location reported in the OIP of the lighting device it should match the insertion point in the drawing.
  21. Try this one. The Light Instr Robe Spiider HUNG had the display marker outside of the base group. Testy Spiider Rotation.vwx
  22. It looks like you have the Parts Record attached to the Base group as well as the parts inside the base group. Edit your symbol and enter the base group. Either ungroup the group in the base group and choose not to transfer the records or enter the group and detach the parts records from the objects. You will have to replace the instrument with the same symbol, save and open the file or something else to force the lighting device to update. Testy Spiider Rotation.vwx
  23. Without seeing the file it sounds like all the fixtures are patched to the came address in Vision. I would suggest opening the Patch window in Vision to check. You can reassign the fixture addresses from there if necessary. Depending on how old the video you watched as a tutorial there may have been some changes in Vision and Vectorworks. Vision and Vectorworks use different names for Address and Channel and you need to make sure your settings in Spotlight Preferences are set correctly to map the fields you used in Vectorworks fields to the Vision fields.
  24. Make sure you are running the latest service pack. There were some issues in this area that were fixed by service packs. If you are still having issues please post your file or send it to tech support so we can investigate.
  25. Also make sure you are usingthe latest version of Vision and Vectorworks. MVR is evolving rapidly mixing different service packs between Vectorworks and Vision could cause issues.

 

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