Jump to content

Yordan Kostadinov

Vectorworks, Inc Employee
  • Content Count

    84
  • Joined

  • Last visited

Community Reputation

23 Great

1 Follower

About Yordan Kostadinov

  • Rank
    Apprentice

Personal Information

  • Location
    Bulgaria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello @JimDenaultASC, We are not able to reproduce the problem as described. Could you please send me your file, or a simplified version with only the described problem, in personal message here or via e-mail so we can test it. The file will be used only for in-house testing purposes. Best regards, Yordan Kostadinov
  2. Hi @A.D.K., I'm afraid files created in SP0 are still corrupted. I cannot think of another way to fix it, but the attached script. Close Lightwright, download the file and run the script from the menu in Tools->Plug-ins. Perform complete export and the issue should be resolved. Let me know if you still have this problem. Best regards, Yordan Kostadinov ClearLWIDs.vs
  3. Hi @A.D.K., You can expect this fixed in the upcoming SP1. Best regards, Yordan Kostadinov
  4. Hi @A.D.K., This is a known issue, that will be fixed in an upcoming SP. To force refresh the dialog, change its height by resizing it. Best regards, Yordan
  5. Hi all, This issue is fixed for the upcoming service pack of Vectorworks 2020. Yordan
  6. @JGuffin2010, thanks for the info. The mirror tool actually flips most the objects, making them look like you're seeing them in a mirror. Mirroring again flips the truss again and fix it. Until we resolve the problem, you can workaround it also by using the Flipping menu commands.
  7. Hi @Sebastiaan, The Eyedropper functionality works not only for Lighting Deceives, but also for Stages and many other objects, listed in the help box below. Also, the amount of Eyedropper preferences is such big, that we should be careful when adding more fields. This is to say, that we will prefer some Label Legend specific resolution for your problem. One solution that currently exists and can try is the Create Label Legend from Instrument menu command. Create new label legend from the source Lighting Device and apply it to the others. If you want to disable the automatic repositioning around the Instrument, based on its bound size, you can disable the Use Layout Symbol check. One option for future improvement, that can give you control similar to the Eyedropper and the ability to choose 2D or 3D Label Legend would be the Assign Legend properties to selected context menu. This command was designed for control over the single 3D legend, but can be extended to support the layout legend as well. The dialog that opens is initialized form the right-clicked instrument, so the workflow would be to select the desired Lighting Devices and run the command from the one, that you would Pick Attributes from when using the eyedropper. Let me know what you think, Yordan
  8. Hi @JB_Tech3, I can confirm this is an issue with the Truss object. I'm not able to find a workaround, but you can try replacing the truss type and setting it back to the same one. To avoid the problem, make the destination class active before inserting the truss. Best regards, Yordan
  9. Hi @Rob87, I tested your file and I can confirm both are problems with the numbering command. Here are the workarounds you can use until we fix the problems in a future update: First about the removed Lighting Device parameters, that are still available for numbering - below is a single line script, that will delete the document numbering settings. After the script is executed, the Spotlight Numbering dialog will be initialized with the current parameters of the Lighting Device. Any modifications or reusing parts of the script may result in other problems. DelObject( GetObject( '__NNA_SpotlightNumbering' ) ); Second, drawing object with an attached record is currently possible, only if the record is in the root of the document. All your records are in the Record Formats folder and the Numbering commands does not find them. Thanks for reporting these problems. Best regards, Yordan
  10. Hi @Alex Bridge, This is a known issue, that is fixed for the next service pack. Thanks for reporting. Yordan
  11. Hi @the.dreamer, You can create your own Data Tag objects, that can visualize different parameters and containers. See the attached file. Regards, Yordan hp data tag.vwx
  12. Hello @LenLindhout, For now you can use the Number of units per increment field. In your example, if Circuit Number restarts at 6 and increments by 1, you have to enter 6 in Number of units per increment for the Circuit name field. In Vectorworks 2020 we have improved address numbering, that is related with the DMX Patch command. We will consider your proposal for Numbering improvements in future versions. Thank you, Yordan
  13. Hi @Sebastiaan, It was considered merging or replacing the Label Legend with Data Tag. But the Label Legend is designed especially for the entertainment industry and provides greater layout flexibility, that is lacking in the Data Tag for now. We will reconsider this as the Data Tag evolves. It's technically possible to add "Use Dynamic Text / Define Tag Field" when selecting text in the Legend Layout, but I'm afraid it may conflict with the exciting Manage Label Legend workflow. For now you can group text-blocks with the created Label texts for static texts. If the Label Legend is missing something available in the Data Tag, you can create your own custom Data Tag styles for Lighting Devices, or for any other object in Vectorwroks. Regards, Yordan
  14. Hi @Sebastiaan, The Custom Plan Rotation field is the replacement of the VW2019 field Enable Z Rotation. Once fixed, we will make sure to test that all the mentioned workflows are working correctly with Custom Plan Rotation. About single label attributes - by design it's a single text object and is assigned to one class. If the Single label class Use attributes at creation, the text will use these attributes, otherwise the Lighting Device attributes are used. But as you correctly guessed, in VW2020 SP2 the Single Label is assigned to wrong class, because the default Single Label class is not created. If the chosen single label class already exists in the document, it will be assigned correctly. We are working on the problems and I'll inform you when fixed. Thanks for your feedback and testing, I highly appreciate it.
  15. Hi @Sebastiaan, Thanks for the detailed information provided on these problems. I'll try to answer all of them: 01-3D Legend flips by plan rotation: I'm able to reproduce this problem in VW2019, this behavior is not affected by the Rotate 3D Legend with Z Rotation field. I confirm this is an issue, I created a bug report for this. 02-3D Legend leader lines: I'm able to reproduce this problem in VW2019, I created a bug report for this. 03-3D Legend assign attribute properties: For VW2019 the 3D Legend Use 2D Containers option was replaced with the 3D Layout. The Ligting-Label-3D class is not created anymore in VW2020 SP2, the 3D layout is created and controlled in the same way as the 2D layout. You can use the Eyedropper tool to pick and apply Label Positions for the 2D layout. This will be extended to the 3D layout as well. 04-3D Legend 3D label class forced on field: fixed for VW2020 SP2. 05-2D Non rotating Grouped rotate and 06-2D label container shifts: I'm able to reproduce this problem in VW2019, I created bug reports. 07-2D Grouped Labels do not move anymore: The problem is with Text objects that are not labels and are outside a group - in your case they are in the 3D layout. The workaround is to select these text objects and Send To Front. The control point will appear correctly and you'll be able to move it. I created a bug report for this also. Let me know if you have any questions.

 

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