Jump to content

JBenghiat

Member
  • Content Count

    880
  • Joined

  • Last visited

Everything posted by JBenghiat

  1. JBenghiat

    UNKNOWN TOOL in VW2019

    Even embedded lights shouldn't display in VPs, regardless of the light object display preference. This behavior looks unique to lighting devices and looks like it might be a 2019 bug.
  2. JBenghiat

    UNKNOWN TOOL in VW2019

    You're actually seeing the render light that's embedded in the Lighting Device symbol. Render lights should never show up in viewports (only the effects of the light), so this might be a bug. As soon as you render, whether in hidden line, OpenGL, or RW, they should go away.
  3. JBenghiat

    Instrument Summary / Colors

    The summary is looking at the symbol that represents each type of light. If you want all the lights to have the same fill color, then edit the symbol. Otherwise, you’re looking at per-instance data, which isn’t what the Summary is designed to represent.
  4. JBenghiat

    Templates

    All I use my template for is scale, page size, and grid settings. Any symbols, textures, scripts, or other resources I bring in as needed from my library files. Any plug-in defaults I have saved as red symbols or plug-in styles, and bring those in from my library as well. This includes my title block and drawing border. Default layers and classes I have saved to a Standards file (Library/Defaults/Standards), so I can just import them as needed in the Organization dialog. I also take advantage of Library/Defaults for other resources that I want available in their respective tools and menus: hatches, line styles, focus points, etc. I'm usually starting with scenic and venue files from others, so being able to bring my standard elements into an existing file is important. I also don't work often enough in the same theater to merit making a template — if I'm doing a repeat I'll usually start with the last project and delete the layers with design elements.
  5. JBenghiat

    Curved LED Wall

    Add Surface is for 2D objects. Try Add Solids. Or to combine NURBS surfaces Stitch and Trim Surfaces. You may also want to look at Surface Arrays. In your case I would: - Create the plan contour of the wall as a Polyline - Convert to NURBS - Copy and Paste in Place - Set the z height of the copy to the top of the wall - Use the Loft tool to create a NURBS surface - Create a symbol for one LED panel (the top is the surface that faces out) - both Sand Create Surface Array
  6. A viewport doesn't actually have an origin, only a bounding box, so what you are seeing is the geometric center of all the objects in your viewport. Viewport placement seems to follow a few rules: - If the sheet layer internal origin is inside the page area AND if the entire viewport fits on the page when aligned, the design layer origin will align to the sheet layer origin - If the sheet layer origin lies outside the page area OR the viewport is larger than the page area, the viewport will be centered on the page So, if your VP or cropped VP is smaller than the page size, you can shift your sheet layer page area slightly to the right, and your VP will create to the left of the center of the page
  7. This has come up before a few times. See this thread:
  8. JBenghiat

    SDK equivalent to VectorScript SetDimText function?

    You can access most of the dimension parameters with object variables. I would set ovDimShowValue to false, then set the leader text to your desired value. This also ensures that the text doesn't reset if the dimension receives a manual edit or is associated.
  9. Do you need a 3D view? Your post just mentions two Top/Plan views. If you are 2D only, you just have to use a graphic language that shows you are drawing a vertical position and don't worry about stacking the positions (other than for calculating beam angles). You have two options: 1. Draw the positions in elevation the way you would a ladder, with the light symbols below the bars and pointing down (or the reverse for an FOH position). In addition, draw a "footprint" or "shadow" of the position in plan view. This a top/plan view of the position, using shaded or hatched regular symbols (not lighting devices), just as you would do for a ladder or boom. 2. Draw the both pipes in top/plan, offsetting one of the pipes (usually the top). Indicate that the top position is N.T.P.L. (Not True Plan Location), or your favorite note to indicate as such), and use arrows at the ends of the pipe to indicate that this position stacks on the other. If the hanging configuration is radically different from the bottom pipe or uses a different inventory, also include footprints in their true position.
  10. JBenghiat

    Viewports

    A few things: - The orange box is just the selection boundary, so you can ignore its size. It is relevant in that it will tell you where you can click and select the Viewport, but should otherwise have no effect on output. - Because it is the selection box, it's going to include annotations, as those are part of the entire viewport object. - Cropping will have some effect on the selecting bounding box, but the bounding box will always be the union of the crop object and any annotation objects' bounding boxes. - The bounding box also includes any planar objects, even if you can't really see them in a rendered 3D view. You can try unchecking Display Planar Objects in Object Info and see if that resizes according to your expectations. (Note, that means any dimensions will have to be VP annotations)
  11. JBenghiat

    Spotlight Beam Wireframe upside down

    @mjm You do have an alternative tool for this at your disposal 🙂. If there’s something it’s not showing for you, let me know.
  12. JBenghiat

    Accessing Object Data in another file

    I don't know 100% the process, but a lot of the title block data gets written to a hidden record format, and I imagine this is what gets read. (Essentially writing to the record format's defaults). You can browse the file's resource list, import the record format, read the data, then delete.
  13. I'm using RunTempTool() to call a custom tool that inserts a plug-in. If the user clicks the first point, then hits the delete key, the tool operation is aborted, like pressing escape. I would like for the tool to instead go back to waiting for the first click. Is there a way to change this behavior? The tool action at this point also is kAction_OnEnterReturnKeyForToolCompletion, which makes it difficult to tell if the user has hit the delete key or the enter key.
  14. JBenghiat

    Accessing Object Data in another file

    You can extract data from a resource in another file, but not an object. If you create a reference to the other file and a referenced viewport, you should be able to read the data via the viewport. The only other option would be to have the file write data to an external data source (xml, text, sql, etc).
  15. JBenghiat

    Assign Class to Selected Symbol via Custom Script

    A single object is easy: SetClass( FSActLayer, ‘Class Name’ ); All select objects takes a bit more code structure. Look at ForEachObjectInList, which will iterate through objects. You can set the function to traverse all selected objects.
  16. JBenghiat

    MultiCell Help

    There is no good way to do this, and being able to swap out multicells is towards the top of my wishlist. Your best bet is to redraw the position and use LW to transfer the data. Either keep both versions and copy/paste data, then delete the old version, or turn off data exchange, export instrument data (only the fields you use to do a match), then merge into LW, matching by either position/unit number or by channel. This will get new Spotlight IDs into LW, at which point you can resume data exchange.
  17. JBenghiat

    Date function - data structure changed in 2019?

    You can find examples under the PythonExecute reference: http://developer.vectorworks.net/index.php/VS:PythonExecute The Begin/EndContext calls allow you to treat each execute call like a new line in the python script, maintaining variable values among lines.
  18. JBenghiat

    Date function - data structure changed in 2019?

    Along with file access, date function limitations were a big incentive to develop python support. Even if you're not ready to make the jump to python, PythonExecute will let you run python from within vs and take advantage of the date and time functions. If your script is not encrypted, use Set/GetVSVar to pass data between vs and python. If it is encrypted, you will have to use the string repository (Rpstr_…) to pass values, which is still fairly easy.
  19. The older resource pop-ups allowed content to have categories, which displayed as shaded bands between icons. This option should create dividers for each folder. That said, I would recommend using IResourceManagerContent instead, which will give you a full Resource Manager for the control. //Header: VectorWorks::Extension::IResourceManagerContentPtr fContent; ... //Constructor: fContent( VectorWorks::Extension::IID_ResourceManagerContent ) ... //OnInitializeContent(): fContent->InitByTDType(kMaterialNode); fContent->AddContent(kObjectsEntLightingGobos); VWImagePopupCtrl* texturePopup = this->GetImagePopupCtrlByID( kPopupTexture ); texturePopup->PullDownResourceLayoutInit( fContent ); texturePopup->PullDownResourceLayoutSetSelectedResourceName( fSelItem );
  20. JBenghiat

    Realistic hardware spec for OS X

    I still have a 2013 MacBook Pro, which maxes out at 16MB of RAM. It has no problem with Vectorworks and rendering, so minimum specs of anything new are going to be fine. That said, I would get as fast and as much RAM as you can afford. Also, check the configuration of the RAM for each model you're looking at — if you're not maxing out, you can upgrade the RAM later, but if you have 1 slot of 16, that's more cost effective to upgrade than 2 slots of 8, etc. The one thing I wish I had more of is storage — 500MB fills up pretty quickly.
  21. JBenghiat

    Lots of Fixture Errors that may be connected?

    Orientation and projection are two separate processes. If a fixture isn't orienting correctly, something is probably wrong with the assignment of the Parts record to the 3D components. See here: http://app-help.vectorworks.net/2019/eng/index.htm#t=VW2019_Guide%2FLightingDesign1%2FLighting_Instrument_Specifications.htm What is your rendering mode? Make sure Cast Shadows is turned on. Various other fill and texture settings can affect this. VW doesn't have a means to automatically fill in the brightness level of the lamp. You can use the visualization palette to edit the render lights and give them a lumen or peak candela value. This only will affect RW renders. Also note that illuminance is affected by a lot of factors, including properties of materials, so if you're using VW to get a sense of accurately rendered brightness, you're probably not getting good results. If I'm just adjusting a rendering for lights that I know should feel brighter, I just up the "Brightness" setting to more than 100% using the text box. You can input any percentage in there.
  22. JBenghiat

    Spotlight Inventory Color Summary Not working

    Each instrument summary takes it’s own set of parameters. If all the summaries are identical, you can make a symbol out of a summary and change the summary in the symbol. If each summmary has different display options, 2019 should support object styles for all plug-ins, so you should be able to define a Summary as a style and have the object list refer to the style. I haven’t tired this yet, though. If you want to copy the settings of one summary to another, use the eye dropper tool, This wall copy all the plug-in parameters, though.
  23. JBenghiat

    Parellipsphere 170 not in Fixture Library?

    As long as we can still see which fixtures have the ground wire omitted.
  24. JBenghiat

    How to rename plugin files?

    To expand, your plug-in depends on reading values from your strings files in the.vwr, so you need to change the line above as well as any resource calls that name the .vwr path explicitly (usually menu bar and image calls). In your case, because it can't find the strings file, the plug-in is using an empty string for the category, which prevents it from showing up in the Workspace editor, though it should show in the Plug-in Manager. Also note that changing the file name won't change the universal name, which is coded in the plug-in implementation, or the display name, which the definition structure should read from the strings file.
  25. JBenghiat

    Parellipsphere 170 not in Fixture Library?

    This is what many of us used pre-internet: Photometrics Handbook https://www.amazon.com/dp/0911747370/ref=cm_sw_r_cp_api_i_WTngCb8NAC1N9

 

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.

×