Jump to content

Jonah Bobilin

  • Posts

  • Joined

  • Last visited


2 Neutral

Personal Information

  • Occupation
    Lighting Designer and Stage Electrician
  • Homepage
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Version 1.0.0


    This is a scenic design tool I created for set designers to help simulate sightlines quickly for those situations where scenery is moving around a lot during a show and you're trying to check for blind spots in arrangements, communicate with the director, or are designing something complicated in the round. While this program requires a 3D model to work it will only give you a 2D groundplan simulation. Because I'm modeling the blind spots using a lighting device to create the shadow projection there will be some slight error and the tool will be less effective on a multi-level set or significantly raked stage. Directions for use are given in the file along with a series of buttons to run the program. In essence, you run a network to generate a sight line object and name it (e.g. House Right Seat), move the object to the location and adjust the sight line bounds, and then run another network to create a shadow projection simulation of what a person can see from that seat. Finally, you switch to fast renderworks to see the shadows and, if necessary, adjust the Bot-Z depending on where the z=0 point is in relation to the playing space. I'm using a object naming system that takes user input and names objects with concatenation as they're are created, releases them to the user for manual modification, and then regains control in a separate network. This is still a little buggy and sometimes leads to VWX crashing (particularly the user clicks "cancel" after prompted to input a name), so save your file before running any of the networks here. I'm still new to marionette so I appreciate any feedback.
  2. Hi. I'm trying to get my license renewed. I haven't been using Vectorworks as much recently due to the COVID situation so I didn't notice that my student license was about to expire. I put in a request on Friday and am wondering how long it will take to get approved, I'm supposed to be working on a project right now. Mahalo.
  3. Version 1.0.0


    Converts a string to a "name" (object handle). I found myself using concatenated strings to name objects (e.g. a series of squares named: sq1, sq2, sq3) after which a manual operation was performed and then another marionette network was run to pull new information from individual adjusted objects. I wanted the wrap the network and set it receive input via the string dialogue node (i.e. you click and type the name of the object you want to modify) but I needed a node to turn the strings into an "object name" and use that to get the object handle. This node is pretty simple, but I think it's pretty useful if you are creating a two-step system with human modification in the middle and want to regain control of a bunch of objects named by concatenation.
  4. Wonderful to hear. Thank you for looking into the issue @mstratiev.
  5. Please find attached two files where I noticed the issue, and my saved preferences set. Still in the middle of drafting so the files may not be super clean. My guess is the issue has something to do with the way VW is reading the LightingDeviceParamsSavedSets file. Doesn't seem to be file specific. Mahalo. UHMS2020-SueñoLightPlot v2020.vwx MVTDesperateMeasures-LightPlot.vwx LightingDeviceParamsSavedSets.xml
  6. I've noticed that since I've updated to VW2020 there seems to be an issue in the OIP sometimes where all the data fields for my lighting device parameters get jumbled. I've attached a screenshot for clarity. I am working from older vectorworks files so I'm not sure if that has contributed to the issue. I believe that the crux of the problem is that I have a custom organization to the layout of my OIP for lighting devices which seems to be confusing the program. I've tried to recreate my settings within VW2020 rather than using my imported settings from VW2019, but the issue persists, which makes me think it might be an issue within the VW2020 spotlight preferences itself, rather than old file issue (especially because it's occurring across multiple files). The problem seems to surface when opening up files and when switching between two or more open files. My workaround right now is: 1. Open the file and if the OIP is messed up... 2. File > Document Settings > Spotlight Preferences > Lighting Device Parameters 3. Set lighting device parameter set to Default 4. Refresh lighting instruments (command+/) 5. File > Document Settings > Spotlight Preferences > Lighting Device Parameters 6. Set lighting device parameter set back to my custom settings *see second screenshot, for fixed The workaround isn't terrible (although took a while to figure out initially) so if I was just doing this on startup I'd be fine, however I regularly switch back and forth between multiple open files and sometimes this issue occurs when switching between files, which interrupts my workflow. Thanks.
  7. Loving the new schematic view in VW2020 and modification to the ladder tool. Been waiting for this functionality for years so great job to the developers. However I'm having trouble setting a trim height for my lighting ladders. Of course it is possible to move the 3d object to the correct height, but the Z parameter (height) given in the OIP is at the center of the 3d object and not where it would be clamped to a batten (top of the ladder + offset due to clamp), and there doesn't seem to be a way to set a custom origin for the object since it's a plug-in. Since the ladder is not lighting position object I am unable to edit the geometry or like a truss object "change trim height of system." I can always annotate my paperwork, but I'd prefer to just be able to click on the object and be able to read a correct height in the OIP. It'd also be nice to be able to connect my ladder objects to existing hanging positions, so for example if I change the trim of my 2nd electric, the ladder attached automatically changes height as well. That is possible with trusses and other lighting positions and I'd love to see it as a possibility here. It seems that the key issue is that the schematic view isn't compatible with the convert to lighting position command. If there is a workaround I'd love to hear it. I tried converting the ladder to a symbol, but that messes with the schematic view functionality same as converting to lighting position. Perhaps this can be built in to the next update or a workaround can be discussed in a future webinar. Thanks for reading.
  • Create New...