JeroenS. Posted April 7, 2022 Share Posted April 7, 2022 Hi everyone, I love using datatags as lighting labels in 3D viewports. To limit the amount of design layers I often clipcube a single object or construction. While placing datatags using the "All Eligible Object Mode", objects outside of the clipcube also get a datatag. This can result in some lighting devices having the wrong datatag. Is this a known bug and are other people also experiencing issues with this? 1 Quote Link to comment
Vectorworks, Inc Employee jcogdell Posted April 7, 2022 Vectorworks, Inc Employee Share Posted April 7, 2022 As far as I know this is not a bug but the intended behavior of this mode of the Data tag tool. The selected eligible object insertion mode was added in 2022 to provide a better insertion workflow in Design layers due to this behavior. Quote Link to comment
JeroenS. Posted April 7, 2022 Author Share Posted April 7, 2022 (edited) Adding a option to only apply datatags to symbols within the clipcube bounding box would be a great timesaver! I hope this feature will be up for concideration. Using "Single Eligible Object Mode" will also show all the symbols outside of the clip cube at the moment. Edit: Please note that I'm using this tool in viewport annotations Edited April 7, 2022 by JeroenS. Quote Link to comment
Vectorworks, Inc Employee jcogdell Posted April 7, 2022 Vectorworks, Inc Employee Share Posted April 7, 2022 Ah I thought you were using them in a design layer not in a viewport annotation. That sounds more like a bug to me in this case, I'll get a bug report opened for it. 26 minutes ago, JeroenS. said: Adding a option to only apply datatags to symbols within the clipcube bounding box would be a great timesaver! I'll make an enhancement request for this 1 Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted April 7, 2022 Vectorworks, Inc Employee Share Posted April 7, 2022 Hello all, Not seeing this on my end in VW 2022 SP3. A test file or a screen recording showing the issue would help in finding out what is going on. Best Regards, Nikolay Zhelyazkov Quote Link to comment
JeroenS. Posted April 7, 2022 Author Share Posted April 7, 2022 (edited) Here's a screen recording of whats happening: Edit: I'm using Vectorworks 2022 SP3 Build 636848. Same issue on both Windows and Mac. This issue existed also in previous builds. Edited April 7, 2022 by JeroenS. 2 Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted April 7, 2022 Vectorworks, Inc Employee Share Posted April 7, 2022 Thanks for the recording @JeroenS.. Unfortunately I am still unable to reproduce this on my end. Would it be possible to share a test file showing the issue? Quote Link to comment
JeroenS. Posted April 7, 2022 Author Share Posted April 7, 2022 Hi Nikolay, I'll send you the file in private chat. 2 Quote Link to comment
JeroenS. Posted January 24, 2023 Author Share Posted January 24, 2023 It's been a while since this was reported as a bug. Are there any updates on this issue? The behaviour of datatags with the clipcube seems still the same in Vectorworks 2023 SP3. 1 Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted January 24, 2023 Vectorworks, Inc Employee Share Posted January 24, 2023 2 hours ago, JeroenS. said: It's been a while since this was reported as a bug. Are there any updates on this issue? The behaviour of datatags with the clipcube seems still the same in Vectorworks 2023 SP3. - hello @JeroenS., The fix for this issue turned out not to be trivial and we are still working on it. Sorry for the inconvenience and thanks for your feedback and patience. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.