Jump to content

Sam Jones

  • Posts

  • Joined

  • Last visited


413 Spectacular

Personal Information

  • Occupation
    Technical Director
  • Homepage
  • Location
    Los Angeles

Contact Info

  • Skype

Recent Profile Visitors

8,231 profile views
  1. @Jonathan Pickup Jonathan, Do you know if a hyperlink will export to the PDF if linked to a Sheet Layer as opposed to a saved view, which you said will not work?
  2. If the goal is to create several hyperlinks and place them at known locations on a known sheet layer, based on discoverable data in the file, then having a script do the harvesting of data and placing the links. The goal is to create a sheet layer that contains several hyperlinks to other sheet layers laid out in a nice known array with the links appropriately named. May not sound like it is worth the scripting hassle, but I have a need, and, at the very least, playing around with this application will probably teach me stuff I can use down the road.
  3. Thanks Pat! That looks very very promising. I just got slammed, so I won't be able to play with it for a couple of days, but why wouldn't it work. Cool.
  4. I would like to create a script that creates a hyperlink object on a sheet layer that points to another sheets layer. Can I do that? How? Using vectorscript, can I create a hyperlink anywhere in the drawing pointing to anything. How? Yet again, TIA
  5. However true this may be, VW's response is usually that if you can script it or you can acquire a script for it, they will leave that as the solution for now while they point their engineering team at tasks that require their special knowledge, expertise, and ability to dig into the guts of the program. I know this may seem frustrating, but many times they will get around to it, eventually. Video Screen, Blended Screen, LED Screen, and the Speaker tools come to mind, but there are others. I bet it's going to take some time for Michael's marvelous tool to be incorporated, if ever, but you have it now. Should you ever be in the same place, MIchael's bar tab belongs to you.
  6. I believe he is talking about the Instrument Summary tool that is part of the Lighting Toolkit in Spotlight However, that is still not enough information. Raj, are you changing the value of the "Weight" field in the Light Info Record after having placed the Lighting Device? Lighting Devices that are placed before the change of the "Weight" field will not reflect the new value you have placed in that field if you placed in the symbol definition, nor would any symbol instance if it was placed with the symbol insertion tool. When you change a value of a field in the symbol definition it will be ignored by every instance of that symbol that has already been placed. Only the Lighting Devices and symbols placed after any changes you make will be use/show the new value. It will also be the case that you will have instances of the same symbol having different weight values. To make every Lighting Device of a given Instrument Type value have the same weight value you must select every instance of that type and then change the value of the "Weight" field in the Object Info Palette (OIP). Both VW and AutoPlot have a tool to select all the Lighting Device instances of the same type as the currently selected one. Having done that you will still need select the "Refresh" button at the bottom of the OIP of the Instrument Summary Instance, or just make a new one and delete the old one. If you have done all that and still do not see the correct weight underneath the Instrument Type name in the Instrument Summary post the file here. HTH, Sam sjones@autoplotvw.com
  7. Place just one Instrument Summary (IS) on a design layer and then place viewports of it on all the sheet layers. When you update the IS on the design layer it will update in all the viewports. If you make a totally new IS, make within the crop area of the old IS.
  8. The attached command should do what you want. Add it to the Plug-Ins folder in the 2023 User Folder and then add it to your workspace. Unfortunately, as it is part of AutoPlot Tools for Spotlight, it will only work for 2 months from its first use. There is also a "Beam Console" command that will let you turn on beams by channel number, focus points, or selection. Email me with any comments, questions, or problems. Sam sjones@autoplotvw.com All Beams Off.vsm
  9. Here is a menu command that does much of what has been discussed here. Placing it in the Plug-Ins folder of the 2023 user folder and then adding the command to your workspace should make it available to you. It will be a part of the next version upload of AutoPlot Tools for Spotlight, so it will stop being functional 2 months after its first use, but it should be fully functional until then. Let me know if you have any coments, questions, or problems. Sam sjones@autoplotvw.com Beam Console New.vsm
  10. This is super cool. I love putting the RunScript command into the database row header.
  11. @Jesse Cogswell Thank you. Dealing with emitters is in my near future.
  12. @fuberator or anyone else. I'm starting to implement a menu command that will execute the result of the dialog below. Feel free to comment before it gets written in stone.
  13. @Jesse Cogswell Thank you Jesse! Setting the object variable seems to have the same efficiency as the SetLightInfo procedure, but looks a little cleaner to me. I would use your code, but when I found the asdfasd procedure I added adjusting the brightness to the functionality, but I have other uses for that object variable. I am constantly and presently surprised by the hooks avalable to scripts in the object variable list. I just wish I could decipher its organization in a manner that would let me find the hooks I need more easily.
  14. @fuberator First, you can go to the Default light by going to Top Plan view. I don't know what conditions might change this, but it is working for me. Perhaps this only works if the lights in the scene are only contained in Lighting Devices. Second, I'm working on enhancing a command that I have already made to do much of what wish for. Currently it only turns the beams on in the OIP, but turning the light objects on and off for rendering looks very doable. See image of the current command dialog below; it will need to be expanded. For your own programming investigations, you should know that while the programming isn't rocket science, but it does involve getting the profile group of each Lighting Device, polling the objects in that group and finding the lights, then turning them on and off with procedures specific to Light objects. I'll keep you informed of my progress.
  15. Got it for now, but I have only experimented with ETC Source 4 conventionals shiipping with the program. Entering the profile group and adjusting the light object with SetLightInfo() procedure seems to do the trick. I'll see what happens when I find a Lighting Device that uses an emitter.
  • Create New...