Jump to content

Gabriel Chan

Member
  • Content Count

    95
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Gabriel Chan

  • Rank
    Apprentice

Personal Information

  • Occupation
    Lighting Designer
  • Homepage
    www.gabrielchan.me
  • Location
    Singapore

Recent Profile Visitors

1,190 profile views
  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

 

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