C. Andrew Dunning

100% my pleasure! Have a good one!

Our tools and the stock tools are 95% identical. The functionality youxre wanting applies to the stock tools. The manual is free-of-charge...

Definitely doable! See the manual found on https://www.landrudesign.com/AudioToolSet.htm.

2 things: 1) Edit the speaker's Symbol definition and change "Throw 1" from "100 ft" to "100'." 2) For each Speaker instance using that Symbol, either switch Symbols and then return to the E5 or enter "100'" in the Range 1 "Throw Distance." The Hatch is not being applied because the Throw Distance you are using is shorter than the given dispersion lines. 100' is way more than you need but the tool will "trim" that automatically at your Listening Height. I hope that helps.

Would you mind posting or DMing me a copy of your file?

Others might offer differing opinions, but my $.02US: Unless there is a good reason, such as needing a dynamic list of options, stick with a pre-populated list to save on the overhead. And...if you DO choose to clear and re-populate, do that in the WidgetPrep Event (41).

Buy a license to one of our VideoScreen suites: https://www.landrudesign.com/VWPlugIns.htm.

Yes. Think of fullness as "in addition to." I'm glad the link is helpful. I have found Rose Brand resources to be quite valuable over the years - in addition to the company simily being a great vendor.

@Peter Telleman, this explanation on Rose Brand's Web site might help you understand what the "Fullness" parameter for our tool does: https://www.rosebrand.com/custom-curtain-services/curtain-fullness?srsltid=AfmBOorfdgYYMIuz4xfIexewc-pkFf7EyFFw41Z3dKFlqj7NhJ13HsQ2.

Yes!

This is not correct. The panel counter system does compensate for >0 "Vertical Tied Fullness" values.

@Peter Telleman, things are actually working correctly. See the attached file. This really isn't a question of Styles. For yoiur 3000mm instance, only one panel is needed because your run is 3000mm, which is the same as your stock panel width. "Minimum Overlap" only applies if more than 1 panel was needed. So, the 1200mm "Minimum Overlap" does not enter into the calculations. For your 4800mm instance, two 3000mm panels are needed. They overlap each-other by 1200mm. So...for each...1800mm not overlapping x2 for a total of 3600mm. That 3600mm + 1200mm "overlapping" is the 4800mm total. In the demo file are both "stock" and "Landru" instances with "Show Drape Breaks" and "Show Overlap" toggled on so you can see how the tool is "thinking." I also included an "Overlap Demo" showing that the internal logic is effectively doing. I hope that helps. curtain question - Landru.vwx

What you posted is actually working as-designed. I was concerned when you mentioned a "square" being displayed as that WOULD have been a bug. The extrustion, though, is correct. The instances the tool creates are intended to be "representations" of curtain, truss border, and pipe-and-drape runs - not fully detailed models. Yes, higher levels of detail would LOOK nice but modeling that via a tool would quickly become impractical.

What version of Vectorworks are you running? Would you post a file containing the SG instance exhibiting the issue? Or, would you DM me a copy?

@mwuebker, what build of SoftGoods 2 are you running? The most current release (2.5503) works correctly - with one caveat: If the "Adjustable Length" is 14', the "effective" drape length with end uprights is actually 13'-10.5" as 14" is from upright center to upright center. So, no center upright will get created/shown and the OIP will report "Contains Non-Standard Slider(s)." If you make the Adjustable Length 14'-3" (half of each of 2 uprights + 1.5" for a center), you'll get the spacing you're expecting.

For rectangular decks the minimum deck width and depth are 12" and 8" (305mm and 203mm).

"Height" is the height of the top face from the Layer Plane (floor). "Top Thickness" is the thickness of the main area of the deck. "Trim Height" is the height/thickness of the trim around the edge of the deck. All should be adjustable when you have chosen "Deck Only."

I'm not seeing any issues, here. I did past copy of your SoftGoods 2 object into a blank file to make it easier for me to see/test. The only thing I would change is to un-check the "Scale and adjust texture" box in the 3D Options dialog. Also, you have chosen the "Scrim" Texture. Its semi-transparency will only work in Final Quality Renderworks. When I opened your file it was set to use the "Shaded" rendering mode. So...it appears that the Texture is being applied correctly; you're just not seeing the desired effect. 1 question: What SoftGoods 2 build do you have installed? Look at the bottom of the OIP w. an instance selected.

Use the Speaker/AudioBox 2 tool. (Speaker is the stock Spotlight tool; AudioBox 2 is the Landru Design version.) Assuming your Symbol is properly configured, the tool will insert your Hybrid Symbol (within the PIO "wrapper") and can flip it on its side and/or tilt it. If the Symbol is flipped and/or tilted, the tool will generate appropriate replacement 2D geometry so 2D plans will look right. Your Symbols will be kept "native" and won't get "broken. See the manual found HERE for more detailed info.

If you are using the Landru Design version of the tool, this is fixed in the current release. If you are using the Spotlight version, the fix will be reflected in a forth-coming update.

In Developer mode the code gets totally re-processed each time the tool is called. Are you running 4K monitors? If so, make sure you are running the most current VW2026 update. There was an issue early-on that should be rectified in the current build.

@Ben Garcia - Sheesh...I can see why you are frustrated. I would be too!!!! I opened your file in both 2025 and 2026 and am not seeing the sorts of delays you are. I also tried the same configuration with the Landru Design version of the tools - in both your file and in a fresh one. Would you check/try 2 things:? Please be sure that you are not running VW in "Developer" mode ([Tools][Options][Vectorworks Preferences...][Session]). Make sure "Run scripts in developer mode" is NOT ticked/checked. Having this box checked will cause the sort of slow-down you are seeing. Most users never tick this box but it is worth at least checking. With VW NOT running, would you find your "SavedSettingsUser.xml" file and move it to a safe place. Restart VW. Please a S.A. instance and open the Configuration dialog. Is it now a usable size?

If you would post or DM me a copy of a file containing the array/configuration that is giving you issues I'd be happy to take a look. Intricate tilted Symbols continue to be a challenge but default Symbols and Library/Catalog objects should be similarly fast. As to the posts to which you linked, they are 3-4 years old and, while there is admittedly room for improvement, many of the concerns/requests have been addressed in recent builds.

Yup. Edited.

SetObjectVariableBoolean(1160,HANDLE,FALSE) will set an object to the Layer Plane and SetObjectVariableBoolean(1160,HANDLE,TRUE) will set it to the Screen Plane.