Jump to content

Yordan Kostadinov

Vectorworks, Inc Employee
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

24 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. Hi @Sam Jones, I see only one problem with this code: Note that the new functions uses 0 based indexing, the script will work as expected with AccIndex := 0; Let me know if you have further problems. Regards, Yordan
  2. Hi @Sam Jones, I can confirm there's an issue with both LDevice_SetAccPos2D and 3D, they do not currently work. This will be fixed in the upcoming SP3. Also, for LDevice_Get/SetAccPos3D, first are the position parameters, then the rotation, in your example they are swapped. (Edit - I saw it was wrong in the help too, so I corrected it). Also, a minor change in behavior of LDevice_GetAccPos2D and 3D occurs in SP3 - it will return the location where the accessory is rendered (in neutral position, focusing is handled by the lighting device internally), because in SP2 it returned location values only if its position is customized, but not if in default position. Also, as of SP3 Vectorworks supports Body accessories. Attach the Parts record with Body checked to the accessory symbol, and it will be positioned on the insertion point in 2D and the rotation center in 3D, not the front. Thanks for reporting the problem and let me know if you have more questions. Yordan
  3. 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
  4. 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
  5. Hi @A.D.K., You can expect this fixed in the upcoming SP1. Best regards, Yordan Kostadinov
  6. 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
  7. Hi all, This issue is fixed for the upcoming service pack of Vectorworks 2020. Yordan
  8. @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.
  9. 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
  10. 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
  11. 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
  12. Hi @Alex Bridge, This is a known issue, that is fixed for the next service pack. Thanks for reporting. Yordan
  13. 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
  14. 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
  15. 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

 

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