SamIWas

Ohh...the XML thing looks fun. I might look at that for a future re-write. I'm not wiring too much data. I limited the number of stored data lines at 20, and each line will have 10-20 fields.

Hmm...both options sound interesting. I will look more at the File I/O option. I don't think I want to do it as a worksheet because then the settings are based per drawing rather than global across all drawings, which is a large part of the option.

After many years of toying with the idea and thinking it too difficult to implement, I finally came up with a working system for "User Presets" within some of my plug-ins. I've been able to store the appropriate parameter settings, and recall them in a dynamically-updating existing pop-up menu (which also has static options from the parameter definition). So far it is working exactly as I had hoped. But, I'm wondering if I'm going about the best way of storing them. Right now, then you hit the Save Preset button, it gives you a dialog for a name, checks to make sure that name doesn't already exist, then stores the preset in the SavedSettingsUser.xml file. Each preset is stored with the same overall header like <IllumiVizBoom>, then an incremented name like <Saved_7> as the saved setting, and the setting is a delimited string with all the settings.. This was working great until I did a Vectorworks update, and it seemingly erased all of those settings, while keeping others. So, I'm wondering if that's the best way to store user presets to be recalled in a PIO later. I also thought about using Plug-In Strings, but that wouldn't give access to use the settings across multiple plug-ins or outside management. Anyone out there use user-saved presets, and what do you think is the best way? Pay no attention to the parameters in the image. This is my garbage test tool where I experiment with different things.

Some of you may have seen the previous set of plug-ins with the boom lists, scissor lifts, and telehandler. I now have another set of Plug-Ins ready to go. This set of Plug-Ins are Lighting Stands used everywhere and Grip Frames used mostly in film and tv production. The lighting stands are broken up into two Plug-Ins: Lighting Stand, which is the more standard stands (Combo, Low Boy, C-Stand, etc), and Lighting Stand Large, which is for the larger stands used mostly in film/tv (RoadRunner, Long John Silver, etc). For Lighting Stands, each one has height adjustment. Stands that have rocky legs or can take wheels have those options. There are also several mounting/rigging options such as grip heads, grip arms, menace arms, tee pipes, beaver boards, and the ability to add a custom symbol to the mounting point of the stand. There are several texturing options for the various parts to make them look more realistic in renders. Grip Frame has options for gel frames, flags, large frames, and mounted large frames, with an option to make the flags and frames into floppies. Each one has a default selection of materials, or they can be customized with textures for more realism in 3D renders. There is full control over roll and spin of each frame. Control grids can also be added to any frame. All of the Plug-Ins are also fully hybrid with separate 2D display options, so that the 2D plans are clean. If these interest you, head on over to illumiviz.com. Also be sure to check out "The Workshop" which shows other things I'm toying with. Please pass along to anyone you think might find these useful. One note...sending license keys is a manual process and may take me up to 24 hours to get them out between sleep and work.

Hmmm...I will try this. Assuming it's not too resource heavy...if updating 20 PIOs at once, I wonder how quickly that executes.

I've been trying to build a Loft NURBS in one of my PIOs. I draw the Polylines, convert them to NURBS, and do a loft. It works, as long as I'm in Top/Plan. But, if I am not in Top/Plan, the NURBS jump to what appears to be screen plane. I have tried using SetObjectVariableBoolean(h,1160,TRUE/FALSE) and SetPlanarRef(h,0 and -1) to set the NURBS curves back to the right plane, but neither works. The attached image shows the stack of poly lines, and what happens when they are changed to NURBS. Does anyone know the proper way to tell the NURBS to stay where they were?

I write most of my stuff in 2026, then re-create it in 2021. 2021 has two things in the script editor that drive me crazy: compiling returns to line 1, and there's no search function. So, I've found it easier to do all of my writing in 2026, then just copy/paste back to 2021 and re-enter all the parameters. Thus far, I have not found any procedures that don't work in 2021, but I'm not doing anything really crazy. However, I have found some ways in which the script functions slightly differently depending on 2021 vs. 2026.

Thank you for the info. I'll check it out! Is there an actual listing of the codes somewhere, or is this one of those "undocumented" features. I don't see it anywhere in he auction reference, so maybe in the SDK? I am not an SDK user, so I'd have to delve into that.

Just saw this post. Wondering how you associate an object with another in VectorScript. I'm going to guess this wouldn't allow lighting devices to track position of a plug-in written in VectorScript, like they do with truss and pipes? because that is my most-requested feature! @Pat Stanford @Julian_Carr @Jesse Cogswell

A few people have commented about that one. I'll make that the next priority.

Thanks, man! These plug-ins were used extensively in the production of ST. The telehandler was largely developed for ST.

Thank you so much for the review, Scott!

I have finally finished some plug-ins that I use heavily in my own work, and thought they might be useful to other people. The plug-ins are a Boom Lift, a Scissor Lift, and a Telehandler. Most of my work is in film and episodic television, and we use these constantly. They are designed with Film and TV production in mind, but could be used for pretty much anything. They are all fully customizable for size, arm heights and angles, platform height and extension, etc, along with either color presets or custom colors. Each one also has several "presets" to quickly select different models. There is a Film/TV version of the Boom Lift which has numerous standard rigging options available with customization of each one. They are also fully hybrid with separate 2D display options, so that the 2D plans are clean. If these interest you, head on over to illumiviz.com. Also be sure to check out "The Workshop" which shows other things I'm toying with. Please pass along to anyone you think might find these useful. Cross-posting this in General as well. One note...sending license keys is a manual process and may take me up to 24 hours to get them out between sleep and work.

Hey all, I have finally finished some plug-ins that I use heavily in my own work, and thought they might be useful to other people. The plug-ins are a Boom Lift, a Scissor Lift, and a Telehandler. Most of my work is in film and episodic television, and we use these constantly. They are designed with Film and TV production in mind, but could be used for pretty much anything. They are all fully customizable for size, arm heights and angles, platform height and extension, etc, along with either color presets or custom colors. Each one also has several "presets" to quickly select different models. There is a Film/TV version of the Boom Lift which has numerous standard rigging options available with customization of each one. They are also fully hybrid with separate 2D display options, so that the 2D plans are clean. If these interest you, head on over to illumiviz.com. Also be sure to check out "The Workshop" which shows other things I'm toying with. Please pass along to anyone you think might find these useful. Cross-posting this in Entertainment as well. One note...sending license keys is a manual process and may take me up to 24 hours to get them out between sleep and work.

Looking at other tools, even ones that are part of the VectorWorks software, it looks like this is normal. Seems like that could lead to something messy if a helpful person came along as changed them. Looks like ones written in the SDK aren't like this, but ones in VectorScript are. Is there any way to prevent that in a VectorScript plug-in?