Jump to content

Gabriel Chan

Member
  • Content Count

    95
  • Joined

  • Last visited

Everything posted by Gabriel Chan

  1. Trying to delete a class leads to this pop up window: Unable to delete the objects. One or more of the objects that you are trying to delete is a required component or automatically generated component of a plug-in object and cannot be deleted. As shown in the first attachment. I did a custom selection search as seen in the next snapshot. No plug-in objects using that offending class however. Am I missing something or is this a bug? Happy Holidays everyone! Gabriel ------ Vectorworks 2017 with Spotlight Module MacOS High Sierra iMac Retina 5K 27" 2017
  2. Thanks Rob! Just as a follow up question, are fixtures made now GTDF compatible? Or are they only limited to Vectorworks 2020?
  3. Hi Rob, Would you be able to repost this in Vectorworks 2017 file format? Vectorworks Service Select is also not available in my country of residence. Gabriel
  4. Try it without selecting any of the fixtures. That will update every single fixture. Gabriel
  5. Hi folks, It's been a while since I was active on this forum. Happy to be back though. I've been holding out on upgrading for a long long time. Still on the 2012 MBP retina, the very first batch. Now that the 16inch MBP comes with an escape key and possibly a better typing experience, it removes all my red flags in the previous gen models that prevented me from upgrading. So the question is, should we go for the i-9 8 cores processing at a lower individual core speed, or would we benefit more from the i-7 6 cores with a higher individual core speed? I suppose it's more of how Vectorworks utilises these cores. My work mainly revolves around the VWX entertainment module and a fair bit of rendering. I use mainly hidden line renders for 3D. Any thoughts? Gabriel
  6. Perhaps place those ancillary items on a separate class? I vaguely remember being able to set limits of what Lighwright counts and just having those on a separate class should do the trick. Gabriel
  7. Say if I would like the label legends to be above the fixtures, but not too far away, do they all appear over the truss? Or are they obscured? That is a flexibility that will be appreciated, but I do prefer the xyz offset option if it's still available? Definitely not an efficient way dragging the 3D labels when you have 400 over fixtures. Still, will be another few years before my upgrade cycle - guess I can hold onto 2017 for now. Thanks for updating! Gabriel
  8. There's the DLVP method of showing a front on view that will keep all your fixture counts coordinated. It's different from drawing a top plan view of a fixture front on but that should be able to achieve what you are asking. Alternatively, place the two LX positions on different layers, create 2 viewports, one with each layer and you can place them so that they don't stack (one will obviously be out of position) I personally prefer the DLVP method though. Gabriel
  9. Still on VWX2017, but this was one of the gripes I had with the DLVP solution. It still is a good way to do achieve most of what I want, and I still use it to a great extent, but 3D labels indeed need to progress further. When you have lights hung in tight positions and you want 3D labels to appear clearly, sometimes the truss chords or other fixtures themselves get in the way when using hidden line rendering, which unfortunately is the way forwards in terms of getting clean lines and not wireframe 3D messy lines. It would be helpful if the adjust 3D labels position command had a z option to push them in front of all the hardware. Right now adjusting in the x and y plane is quite restrictive. Unless other people have better solutions? Gabriel
  10. Seconding @scottmoore method. I keep a master file of all symbols I've ever used so I never forget where that new symbol was created. Also, I tend to create folders in this file's resource library and categorise the fixtures by manufacturers, which then eliminates the need for multiple vectorworks files for Martin fixtures, for Varilite fixtures, for ROBE fixtures and the likes. There's also a resource folder for truss symbols, scaffold parts, rigging gear and so on. Endless possibilities. Gabriel
  11. Well... no matter... Figured out 3D power pack> Revolve with Rail was the solution!
  12. I've been trying to do a sweep of an organic curve (as seen in the Elliptical Sweep.png file) and then trying to scale the sweep object on its y axis so that from plan view, it looks like an oval (as seen in the Elliptical Sweep 2.png file). However, nothing seems to happen after I run the scale operation. Does anyone have any other idea how to achieve a 3D model of this? Gabriel
  13. Thanks Marissa. I am indeed on 2017. Planning to upgrade on a five year cycle - gotta make the price of the software count! Will be certain to look out for improvements in Marionette next time I upgrade. Meanwhile, will be taking baby steps to learn Marionette. Cheers, Gabriel
  14. Seems I have found the answer to my question after a bit more digging at this weblink: http://developer.vectorworks.net/index.php/VS:Search_Criteria Subtypes are under ST, so the criteria I had to make was ST=CIRCLE. Marionette is getting more interesting!
  15. This is way over my head... Goodness.. But I'm trying. My very first Marionette! I think based on all the descriptions of the nodes I understand what is going on, and also the Debugging mode helps to see what data is flowing through. I have managed in the very first node "Objs by Crit" to get inputs to recognise rectangles (i.e. the default criteria T=Rect) or ovals (T=Oval). However, when I input T=Circle, I get this Execution Error pop up: Error: Invalid call-back function parameter type. Parameter index= 0 name=objectHandle So I went to search for the list of Object criteria and I found this http://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix#attrCrit So yes, under types there aren't any circles?? They do appear under Sub types though... How would I get the node to recognise the circles? Gabriel
  16. Here's a tricky one to start the year... I have a set design that roughly has 1500 circles, all of the same diameter of 60mm. I'm looking to extrude them at a range of different heights, somewhere between 200mm and 800mm. The dispersion of these different heights should be as random as possible to create an organic feel. Is there any way of efficiently doing the above, possibly with scripts? Gabriel
  17. It is possible to achieve what you want. Select the hanging position that you want. Under Spotlight > Object conversion > Replace with Stock symbols. The pop up window will ask you what symbol you want to replace with. Gabriel
  18. How true! I tend to receive set drawings from set designers so more often than not that's a done deal and I just replicate in VWX (they mostly come in DWG). This definitely helps with edits. Great workflow ūüôā
  19. I second Kevin's method. Although I tend to place the different configurations on different layers rather than classes. So the class assignment is for different components of the set. I duplicate the first configuration onto a new layer, rotate it to a new configuration - rinse and repeat. This is applicable to non-turntable sets as well. Gabriel
  20. Thanks Rob! Helpful to know how you arrived at those candlepower numbers in the stock symbols. However approximated they are, at least they give me a degree of confidence with using those numbers.
  21. Trying to get some semblance of lux readouts from VL3500 wash in Vectorworks based on their data on their website. http://www.vari-lite.com/clientuploads/directory/downloads/VL3500W_Photometrics032508.pdf What figure should I be looking out for to input into the candlepower data field, speaking of which, what is the unit associated with this field? Footcandle? Lumens?
  22. That's pretty weird. I'm assuming you are on LW5 at the moment? Because I'm not sure if LW6 works w VWX 2012. Briefly off the tip of my mind I do recall a three way compatibility issue between VWX, LW and macOS somewhere in 2015-2016 so depending on the permutation of all three softwares you may have a problem there. Also, in LW5 DMX addresses were still input under the dimmer field, not DMX address. There's also a whole link under John Mckernon's website devoted to explaining data exchange which you can find here: https://www.mckernon.com/supportmenu/vwdataexchangeaddr.html See if that helps?
  23. Is there a rectangle of sorts in place of where your I-Cue symbol is on your VWX file? I can't remember for sure but LW references the VWX symbol from one of the data fields - i.e. "3D Symbol Name", "Model Name" or "Inst Type". They need to tally so if you changed the name slightly in LW it syncs back to VWX and VWX would try to find the symbol to display on the drawing based on that new name. SO because it ca't find it, it displays a rectangle. If I'm not wrong, I think it references "Model Name". Alternatively, you could just refresh your drawing and see if it works. I do remember markdd's way of editing symbols to get it to become an accessory back when I was on VWX2011, and it did work as intended with the then LW5. Keep us posted!
  24. @markdd is spot on. And I guess you're right @pytld it's never too late. There's always something to learn from this community!
  25. Sorry for the really late reply. Been busy getting my show to open. I've had a look at your file, and basically copied your I Cue symbol and one ETC S4 symbol to a new file. If you refer to the snapshots I have attached: You'll find that your existing I-Cue symbol Device Type = "Light" at the moment. This should be Accessory or Static Accessory for you to be able to associate the I Cue symbol with the lighting fixture. Just change that to Static Accessory or Accessory and you shouldn't have any problem, as seen in the second snapshot.To do that, go to Spotlight > Reports > Lighting Symbol Maintenance. Hope it wasn't too late! Gabriel

 

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