JBenghiat

Member
  • Content count

    578
  • Joined

  • Last visited

Community Reputation

33 Great

7 Followers

About JBenghiat

  • Rank
    500 Club

Personal Information

  • Homepage
    www.benghiatlighting.com
  • Location
    NY, NY
  1. Open Lighting Symbol Maintenance in the Spotlight>Paperwork menu. If all the data data is correct, click the Update All Lighting Devices menu, and click OK. All of the Light Info data will push out to existing lighting devices.
  2. You have a couple of methods for displaying text going at once. If you're coding a plug-in object, you code just create the text object over the symbol, eliminating the need for linking text to a record. If you want to used linked text, then the value you provide needs to be to a record attached to the symbol instance inside the PIO, not to the PIO itself. Think of the PIO as a container, like a symbol or group. After inserting the symbol, get a handle to the symbol instance inside the PIO: hSymbol := LNewObject; Now, set the record value for hSymbol, not H1. You may also need to reset the symbol instance for the data to refresh: ResetObject(hSymbol); This also means that if you need to make use of other values stored in the record attached to the PIO, you need to manage those manually -- they will not link to any objects inside the PIO. A better approach might be to use more PIO parameters for your data. Also, you might want to add some error checking. For example, check that GetObject(pTee) doesn't return a nil handle. HTH, Josh
  3. Actually, not quite so easy if we're talking sheets and viewports. You have to step through each viewports and run GetVPClassVisibility() / SetVPClassVisibility() to toggle the class.
  4. It's possible, though I would recommend just duplicating all your sheet layers, as technically your drawing set consists of two full sets of plates. You may also want to adjust the title block to indicate if this is a sheet that should have notes or not. To turn off your classes, use the Visibilities mode of the Organization dialog. You should be able to toggle visibility in all your duplicated viewports at once. When you Publish, save two sets of sheets, and you can easily toggle between the two in the Publish dialog. -Josh
  5. Though keep in mind that variegated gels work because they go in front of the lens, not at the gate. The result is a blended color not a sharp projection of the colors, that has particular interplay around shutter cuts, gobos, and shadows. Vectorworks doesn't quite have the capacity to perform that degree of simulation -- possible caustic photons and a modeled sheet of gel outside the lens will get you close, but the rendering time may not be worth it. Possibly a Photoshopped version of the gel with softer blends (approximating the end result, rather than the actual gel layout) will give you the best results. -Josh
  6. The VectorScript editor has a button at the top-left for creating and inserting criteria, but there's nothing wrong with your menthod. You can find find documentation in the VectorScript Language Guide, which you can access through the help system. -Josh
  7. Look at ForEachObject(). You specify a search criteria and a function to act on each found handle. -Josh
  8. You may find CreateText() more reliable. If I were to guess, you're getting blank lines included at the end of the text block. Converting a PIO instance to group might help confirm this. Also, for good measure, make sure to specify units with your dimensions, i.e. 5" (or mm, or whatever). Otherwise, will get very different results if you switch units. HTH, Josh
  9. Try McMaster Carr. They may have a few options and have 3D models for most of their hardware.
  10. Have you looked at Building Services/Realistic lamps? That might not be as decorative as you would like, but could be a start. If you're refining a reflexive texture, having an environment to reflect and a specular light source can make all the difference. -Josh
  11. The tick marks are lines, and like any lines can have arrow markers at the end. Either through class attributes or through the attributes palette, you have turned on arrows for the ticks. -Josh
  12. It's been that way for years (10+?) -- it's actually a shortcoming of the PASCAL language on which vs is based. The "fix" is actually python support. -Josh
  13. This has been a problem for a while. As with Sam's script, you can manually parse each line and deal with repeating tabs properly. File handling is one of the big motivators on the adoption of Python, and VW highly recommends using py for file handling and data reading. There are many file parsing techniques built in to Python and they are fairly well documented. You can also mix py and native vs if you're not ready to make a total switch for this script. Calling one from the other is fairly easy, though passing data is a little trickier. -Josh
  14. Lighting Device objects contain a render light, and as soon as you add a render light to a drawing, Vectorworks "turns out the work lights," or in other words, does not create the automatic directional light that comes from over your left shoulder. The easiest workaround is to add in a directional render light to your model. I'll sometimes put this in its own layer so it's easy to turn on and off. HTH, Josh
  15. The other workaround is to turn off developer mode when you're testing radio buttons. It's always a bummer when you forget though... I finally hunted down a VW plug-in that triggers this behavior, and this is slated for a fix. Possibly not until 2018, though. -Josh