JBenghiat

Member
  • Content count

    605
  • Joined

  • Last visited

Community Reputation

40 Great

About JBenghiat

  • Rank
    500 Club

Personal Information

  • Homepage
    www.benghiatlighting.com
  • Location
    NY, NY
  1. How do you plan on drawing the position? Rotate the 2D portion how you would like, vertically, at an angle, etc. The footprint is what gives you a top/plan representation of the position. The main 2D component is a schematic view of the pipe that you would use to draw lights etc. in elevation. If you simply need a 3D pipe without the schematic 2D view, extrude a 1.9" diameter circle.
  2. Set the J Rotation to 90. The rotation affects the 3D component and the footprint of the position.
  3. Well, ambient occlusion isn't an OpenGL option, it's a light and shadow option, just like the ambient lighting settings, that affect all raster renders, not just OpenGL. This is like the DPI settings, which affect OpenGL but are not exclusive to OpenGL. One thing that is a bug is that AO should not be dependent on ambient lighting being on. You can turn it off and still see AO (especially if using RW and HDRI lighting) even though the options are grayed.
  4. Also, the render style has Artistic Edges on. (Possibly a change to the style?). If you don’t want this, when you edit the style, you can turn these off.
  5. Both OpenGL and Custom Renderworks have options to turn off both textures and colors. The style Pat mentions above combines those Custom RW options with a few others to make the render look more stylized.
  6. Before installing, rename or delete your old 2018 application folder. Or, in other words, when prompted by the installer, don’t select an existing install. The SP installers will do a full install, not just an update of changed files.
  7. It looks like you rendered in Dashed Hidden Line, which shows any "x-ray" lines as dashed. Sound like you want to be in Hidden Line mode. OpenGL replaced shaded poly around VW 8, at least on the Mac, so if you are noticing a difference in rendering for the same object, it is more likely due to how VW stores the data to describe the object.
  8. Shaded Polygon is really a legacy render mode that predates OpenGL. I think what you want is an OpenGL background render and a Hidden Line foreground render.
  9. Try installing SP1 in a clean folder rather than over your old install. This is actually recommended practice, but it’s easy to ignore, and has never been an issue for me in the past.
  10. You've defined LTSymbol as your main procedure, so any other procedures need to be inside that scope, i.e. place sub-procedures after the main procedure's TYPE, CONST, and VAR sections. Refer to the VS language guide for information on scope: http://developer.vectorworks.net/images/7/72/VectorScriptGuide.pdf
  11. What Mark is saying is that when you have things set up correctly, the combined symbol is unused and the parts show up as used. Indeed this is the case when you look at the actual symbols in use — you don’t have any Lighting Devices actually utilizing the combined symbol, only separate Lighting Devices for each part. Counting, on the other hand, looks for unique Instrument type data, not unique symbols. This is by design: you might have multiple symbols representing the same type: over hung / underhung, plan view / front view, etc. I have a version of my source fours that is slightly shorter for pipe ends, etc. This also works for strip lights, where you count up all the cells, but also divide by the number of cells per unit. You can have whatever symbol you want to represent them in the key. For long PAR 56 strips, I have a symbol with a break line showing only the start of the strip. I would never actually use this symbol for a lighting device.
  12. I may have a solution that doesn’t involve losing your user settings: when updating service packs, do not overwrite your old 2018 install location. Rename or remove your old 2018 application folder before running the installer. You actually get prompted to do this during the install process, but it’s easy to ignore. It’s never given me trouble before, but as the Braceworks libraries are revising, there isn’t a 1 to 1 replacement with old files.
  13. These look like they were manually created.
  14. To add, criteria and variables can be tricky, especially with strings. The Criteria type is actually a string, but the vs compiler will parse a function’s arguments, when it accepts Criteria, and tries to convert it into a string. When a variable is involved, as you may imagine, this can be imprecise. The safest option is to define a variable for the entire Criteria string, and use Concat() to build the Criteria first: critStr = Concat(... SelectObj(critStr); You also usually need to add to critStr the single quote marks that would be around the class name. To escape the quote mark, repeat it two times (plus one to end the string): Concat(‘(C=‘’’, linetype, ’’’) ...
  15. One thing — HowMany is less strict than FEO, so you could get selected objects that aren’t Lighting Devices. Either define HowMany as Count(), using the same criteria as FEO, or iterate with IIndex := 1 to Index, where Index should also equal the number of stored objects.