Jump to content

Sam Jones

Member
  • Posts

    783
  • Joined

  • Last visited

Everything posted by Sam Jones

  1. I don't see a way to do that. That command doesn't seem to show up in the workspace editor. However, you can do that with the AutoPlot command "Sel Truss System Elements". :-)
  2. Charlot, Always remember, your English is better than our French.
  3. Unfortunately, this is not enough of an improvement. There is already a parameter that describes the cable type. If part lengths are going to be reported in a single field, it should read like this: 100ft,10ft,10ft,10ft. Adding the S19 provides no useful information and limits the ability to export the field in comma delimited format. It is likely that for export the field will need to be massaged with a character filter, but even admitting that, the "S19-" makes the field terribly hard to read, and provides no useful information. There is going to have to be another field that has the cable type of "Soca-19" in it. What does "S19-" mean without another field describing the cable type as "Soca-19". The field containing part lengths should only have part lengths. Are you really imagining a cable run being a mix of HAN and Soca cable parts?
  4. When I try and retrieve a value that is shown in the OIP for a BrxHoist object, VW hangs with beach ball of death. The command that it hangs on is: ok := GetLocalizedPluginParameter('BrxHoist', 'Load Trim', localName); The BrxObject parameter list is empty in the plug-in manager, seeming to indicate that it is an SDK object, but the OIP lists a "Load trim" parameter that has an edit field. If I cannot get the localized name is there a way to check of an object has a parameter list? The following code hangs: PROCEDURE GetLocalName; VAR localName1 : STRING; localName2 : STRING; ok : BOOLEAN; BEGIN ok := GetLocalizedPluginName('BrxHoist', localName1); AlrtDialog(concat('localName1 = ', localName1)); ok := GetLocalizedPluginParameter('BrxHoist', 'Load Trim', localName2); {Hangs on this call} AlrtDialog(concat('localName2 = ', localName2)); END; RUN(GetLocalName);
  5. You cannot create your own version of a cable break; it must be a 3D Locus, or a sphere. You have no control over the size of sphere. Both the locus and the sphere are too small at most plot scales. Control over the size of the sphere is desperately needed, better yet the option to use a user chosen symbol to use to represent cable breaks. The current report of the cable objects provides an unreadable list of parts, for example: S19100ft S1910ft S1910ft S1910ft It may be possible for 3rd parties to generate better reports. It will depend on what access is granted to VS to access cable object data. The preview tools have some interesting and fun 3D implementations, but cable object part control is currently, terrible and must be done using the split tool. I won't go into the problems here, but when you play with the new preview cables pay attention to how cable parts are computed and how the split tool is used to specify cable breaks.
  6. Forget I asked. R1 and Index1 are unneeded VARs. Routine works wonderfully. Thanks.
  7. inNurbCurveHandle to the NURBS curve. I know what this is. inPercentOfLengthSpecify location on curve as percent of total length. (0 - 1) I understand this. I thing HLength yields inches but I will check pPoint of specified location. Cool, this is the needed coordinate outParamParametric parameter of location. What is this (R1) and where do I get it from outIndex0-based index of piece for piecewise NURBS curve. What is this (Index1) and where do I get it from
  8. Thank you to Patrick Stanford and Raymond Mullins for answering my question about getting a point along a 3D Poly. I have just ran into the need (that I was hoping to avoid) of needing to find the 3D coordinates of a point that lies a specified distance along a NURBS curve. Given a specified distance, can I get the location, X,Y,Z, of a point a specified distance along a NURBS curve? Also, how does VS get the length of a NURBS curve. The length in listed in the OIP does not seem to be accessible. As so often in the past TIA, Sam
  9. Unfortunately, I need to find the coordinates of the point on the 3D poly that is usually between vertices. Stepping through the vertices is something I do all the time, but doing the vector math to find the coordinate between vertices is new to me. My presumptions upon Raymond have been embarrassingly often. Your turn? You allude to UnitVec() being what I need. So, I get the location and distance of the 2 - 3D vertices that book end the desired distance along the poly. how do I get the coordinates of the point some specified distance between Julian, I will be looking at the NURBS functions, but I have some UI concerns with converting paths to NURBS. The create, compute, delete method that Pat mentions might work, but I have some similar UI concerns. Will see. I need yet another vector math lesson regardless. The language of vectors, use it or lose it. A shout out to Raymond Mullins who has provided me with numerous solutions and examples, and every time I come up with another obvious vector problem I am embarrassed that I cannot coax the answer I need out of one of them. His Reshaper tool does wonderful things manipulating text not just geometric objects.
  10. Is there a function or an algorithm that will yield the coordinates of a point along a 3D polyline at a specified distance from the start? Something like the PointAlongPoly() function. That function does not seem to yield a location even though a vector is one of its parameters.
  11. Actually, the Message command is still working, badly. Typically, it will fail to deploy if there are any alerts or dialogs in the command that you are running. It is not reliable to code. That is if you have no alerts or dialogs the message window may still not deploy; however, if you see it deploy when running a command, it will be consistent for that command (unless you edit and change it). I have several commands that use the message window to show options to use while a command is running, but I have to check them with every new version of VW.
  12. Boh is correct. You need to add it with the Workspace Editor. Either of the top 2 commands will give you access to the workspace editor.
  13. 82. Beam Console This macro allow you to make a channel list of Lighting Devices whose beams you wish to turn on. There is also a “Rem Dim” check box. Alternatively, you can specify a Focus Point name that can be used to choose the fixtures whose beams you wish to turn on. AutoPlot Tools for SpotLight 2020.pdf
  14. Yes yes yes. please please please. There are few functionalities more useful. I wish I had discovered it sooner, and now it's gone!
  15. SetRField(H1, YourRecord, YourField); Should be SetRField(H1, YourRecord, YourField, YourValue);
  16. WOW ! Thank you for this Pat. I'm in the middle of crafting a large command and pref command for it, but I look forward to investigating this later on. Creating desired but complex worksheet databases has always been near the top of data collection desires. Expect to hear more questions down the road on this, but this is a fabulous start. Thanks again. PS, I hope the old worksheet engine is up to the task.
  17. 3D is also a boon to figuring out site lines. Cables are notorious for hiding their impact on site lines in a 2D drawing. 3D is intriguing if the editing problems can be solved. I think they can be solved, but the problems are not trivial when one is depending on the tool to control and render cable breaks and editing and keeping track of extra cable needed for rig moves and swag. That being said, much of what the MEs use AP cable tools for is most easily (for now) accomplished with 2D paths and vertical parameters. They need shop orders, build lists (both for single runs and looms), the ability to specify extra cable for rig moves, to share data with fixtures about both circuit values and jumpers. If the actual route is complex, a simple 3D poly as an example of route can be drawn. I find it interesting that you feel the need to extrude along the path, but that's cool. I doubt that you would want to create 3D objects for 30 cables that go out to the cable bridges and catwalks to the FOH and it 3 or 4 trusses, but I can certainly see the desirability of describing the 3D path(s). The new tools are a large and interesting step toward a 3D solution, but they currently don't get enough of the job done. Like Mark, one can become fond of styles as they combine attributes and parameter values into a single conceptualization of the object(s) needed, but many MEs are going to become frustrated investing the time to realign their workflow when classes and attributes can handle the functionality and making changes along the way is easier. If one puts in the effort (as I think one should), to develop the comprehensive style library needed, then making ad hoc changes will be made much easier by styles. While styles are an intriguing solution to showing the collective result of graphic needs for an object (good), they have a tendency to hide their modifying source (bad). Like Mark, I will pay more attention to styles for all the objects that implement them, but I'm not sure I would want to receive the tech support calls that are going to be coming in from MEs. Looking forward to the next generation of the new cable tools.
  18. I just discovered it as a Worksheet function, not a VS function. In VW Help, search for "Databasebyscript". I am just investigating that documentation now. Good Luck to both of us.
  19. Sam Jones

    Tool Set

    If you can afford the time to ask a question, ask it here. Nobody expects you to read the manual, cover to cover. Wait... What? Manual? Seriously, ask it here. Some of us play a game of can we beat Pat to answering the question. We usually lose. Michael scores one.
  20. Perhaps. The 3D snapping is greatly improved, and the different jumper cable path routing options are cool. Integration with Braceworks is an obvious desirability. However... Have you tried to lay out a show with it? Controlling part ends (cable breaks) is difficult. Graphic indications of cable breaks are almost invisible. One can only control cable breaks with the split tool. This seems cool, but creates separate cable objects which prevents construction of cable build lists. Even without the use of the split tool, cable parts are buried in a dialog which cripples interactive adjustments. The cable path tool is cool engineering and kind of fun, but I don't see any advantages, and I do see some drawbacks when comparing its use to just duplicating cables and converting them to the needed type. Still, the duplicate and convert workflow is available to the new tools, so the user can pick. How one adjust cables to provide for different swag amounts among different cable runs I cannot determine. In fact, I cannot figure out how the "Cable Swag (%)" value is applied by the user or how it is incorporated in the graphic display or in the computation of length. Also, the addition of parts or extra length to provide for different parts of the rig to move doesn't seem possible. If it is, the method is opaque to me. 3D is cool, but the path is rarely displayed in build documents, and when it is those documents are in top plan view. As for extracting data from the cable drawing, I see no way to make a list of build list of each of the cable runs, i.e. a list of each cable run, each of which has a list of the parts in the order they are placed. To make these essential build lists requires hand copying the information from the dialogs, or so it seems. There seems to be no way to create loom build lists, looms that are made up of different parts of different cable runs. There is no way of making box packing lists. Understanding the distributor -> cable run -> distributor work flow will take some investment of time. There needs to be a much better description/example of cable types, their creation and use, since these control all the aspects of the graphic display of cables and the creation of elements of the cable inventory. There is no provision for different cable inventories. Have you ever used more than one vendor on a show, or had to change vendors on a show. There has been no improvement or expansion of assigning data between fixtures and cables. Only cable name and cable number are given to the instrument. No jumper information is given to the instrument. No jumper information is given to the breakout. I could not find anyway to assign unit number or channel to the breakout circuits. There must be a way (I really hope so), but I could not find it. There is no way to assign jumper information to the breakout. If you have solved these issues, please, let's have a Zoom meeting and give me a lesson. As far as I'm concerned, there is no way to use the new cable tools on a real show, compared to other options. This does not mean that these problems cannot be fixed. I have not seen the task document for this feature, but a much more comprehensive task document than the one I am imagining exists will be required. The users I have talked to in the last 2 weeks will definitely resist adopting this new workflow. I imagine there will be others that don't know of any other option than this new way and will struggle to make it work.
  21. I think it's Y1-Y2, but I'm just about to check.
  22. Everything is going well. I can't set the printer page size, but I can deal with that limitation. Is it possible for VS to get the delta Y of a viewport. It's in the OIP, but I'm not finding a hook. Ever so grateful.
  23. How do I specify what is in the Viewport when I run the "CreateVP" command. I want to create a bunch of objects on a design layer, the created objects are the only things on the design layer. I then want to create a design layer viewport and assign it to a sheet layer. So how does that work?
×
×
  • Create New...