Jump to content

Scott C. Parker

Vectorworks, Inc Employee
  • Posts

    560
  • Joined

  • Last visited

Everything posted by Scott C. Parker

  1. Was this file built recently? Or, is it possible the original file was built in a prior version of VW? Either way, what happens if you import the layers from your file into a new blank file? This sometimes cleans out old issues. If it works, you would then share the refreshed file with your team.
  2. How are you adjusting the dimensions? Are you editing the dimension in the OIP? Or dragging the blue control point in the drawing? Dimensions will likely shift according to their starting point. But, it's possible their based on left to right insertion. I'm not sure. What happens when you try dimensioning from the farthest light from the CL towards the CL on the Center-Right side? You'd get the same dimensions, but they'd have their starting points reversed and should respond as how you're trying to do. Side note: have you tried @Sam Jones's dimension tool for pipes? I use it as it's very fast. When I shift a pipe's lights, I delete all the dimensions and run his tool again.
  3. Luke, would you please share a file showing this issue? It's easier for us to assist with the actual file. Thanks, Scott
  4. Christiano, would you please send me a file with your results? I'm working on some snapping improvements and this file would help helpful. Thanks, Scott
  5. fyi, as this is a new bug, it'll likely take a little time to fix. It won't be in the next update. Sometime afterwards.
  6. It's not your symbol. This is working in viewports set to shaded mode. But not in final-quality render mode. It's a bug that I've just reported. To test, I made a file with only a light bulb object and played with the viewport settings. The viewport set to FQ render mode refused to see the class override. You're welcome to play if you'd like. Final Quality RW fails class color override.vwx
  7. This is a bug that's been fixed in the upcoming update. Sorry about this. When you get the update, you'll find it works better using the plug-in versions of the symbols than the plain symbol versions—working on this issue. As for legacy, back saving should still work if you're using the same legacy version of the tool. You are correct that using the new tool won't back save to the old one for editing needs. We had to make changes to offer the full gamut of spotlight symbols in the summary key. The instrument summary key tools was/is packed with so many features that it was very hard to include every function out of the gate. I confess I missed a few of the details during the design process. I feel we included a good number and will continue to refine it.
  8. we're playing with your file. Hope to have news soon.
  9. Hi Dan, It's on the list, but since there is a viable workflow to filter by layers using the new tool, not likely as soon as we would like.
  10. Can you post a file? That doesn't sound like it's working as expected. Are you sure you have deselected the prior ones before making the changing? What happens if you try in a new blank file?
  11. Here's a process course on building distributors. https://university.vectorworks.net/mod/overview/view.php?id=3074
  12. Would you mind posting a sample symbol of what you're working on?
  13. If you could post a couple of sample files, some that are working and another that's not, we can take a look.
  14. I'm working on a project and needed info for a bunch of 3D Loci. Here's a simple Data Tag for 2D Loci. The insertion point of the tag will report the insertion point location all by itself if not attached to a 3D Loci. Getting the tag to attached to a 3D Loci can be hit or miss depending on your snapping mode. I hope this is helpful to anyone who needs it. 3D Loci Data Tag.vwx
  15. @ChrisSterman I would make a copy of the symbol and change it from a 2-way corner into a 3-way T. You'll have to move the geometry inside the symbol to have it align to the cords. You might play with making into a Custom item. I've not tried this. Years ago, I made some custom-angled corners and made a video that might be helpful. It shows info on how the L1, L2... measurements work.
  16. Did you use a new serial number? It's possible they added braceworks and issued a new S# to trigger the permissions.
  17. They should stay in sync. Can you share a sample file? Explore Design Layer Viewports instead. aka, DLVP. You can have any view you wish. If the booms have static sidearms, you could build them as a rigging object and hang lights, etc. The lights would land on the floor first and then you raise them to the appropriate heights to match the sidearms. Have you watched @markdd's YouTube video? He shows both booms with sidearms and a system of multi-level catwalks with balconies as lighting positions shown in schematic views.
  18. My favorite response, ever. 🙂
  19. Do you have a link to a spec sheet for these items?
  20. I think the parts of the array may have come from the libraries, but the symbol is a collection of parts. It's the overall saved array symbol that is causing the copy/paste issue.
  21. Can you post a screenshot and a sample file please? What do you mean by "light source?" The lens is usually considered the light source for VW lighting fixtures vs. the actual lamp or LED engine, though the light source point is inside the light. Are you speaking about the beam of light? Or the results of where the light beam is hitting the stage? Or, the beam of light traveling through the air? These are usually controlled by the gel color listed for each light, and that might be overriding your class setting.
  22. I've played with the file you sent to Juan. The speaker array itself might have issues that is causing VW to freeze. Do you know how the symbol was constructed? The copy/paste works as expected when I build a new one. Do you have an original file in which the speaker array was assembled? Your array symbol is likely from a prior version of VW, and the data records are out of date. I recommend removing them and adding a fresh version using the array tool. Thanks, Scott
  23. @HLSTR Ok, it's us, not you. There's a bug in update three, and it has been fixed in the upcoming update 4. After update 4 is released, you'll be able to refresh the summary keys, and you should be good to go. Sorry for the delay.
  24. I've seen another French user having the same issue. Here are the settings that should work. If they don't, please send me a file for testing.
×
×
  • Create New...