Jump to content

AlHanson

Member
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

6 Neutral

About AlHanson

  • Rank
    Greenhorn

Personal Information

  • Occupation
    Entertainment Designer
  • Location
    Minneapolis, MN
  1. I second all these points (the integer restriction on the parameters is super annoying!!) and have more to add: -The Focus Point hasn't been terribly useful for me (Didn't even seem to work for me the times I tried it in 2020?) as this appears to automatically snap focus to the 3D center of the object the framing isn't always great. Would possibly work better if you could independently lock the Pan or Tilt to the Focus point so the pan always looks to the object but the tilt can be adjusted as needed? Or vice versa depending on the scenario. -The Tripod needs to be parametric. There's been many times that I'm trying to line up a shot and its too low with the 48" stand, but too high with the 62". Sometimes I can get away with just cheating this on the Z height but I generally am showing camera position in my renders, not just the shot framing and cant just have cameras floating in the air or poking through the floor, or go to the effort to make custom tripods for various heights. -The 2D Field of View line line are definitely way too short in most instances and should be configurable. Just make the line length a parameter and we're set. -Need text options! I can give a camera a name and position but I have no means to insert that text by the camera for identification? Simple Text Options like the ones included with the Television tool would work just fine here. -Need a PERMANENT link to viewports. This has been a frustration of mine with Vectorworks forever. It's not enough to convert a camera to a viewport, I need to have a viewport that is always connected to this camera object and updated automatically with changes. I do a lot of projects that show camera shots and story boards so if a camera position or focus changes I need to update it in multiple sheets and this is irritating. -It would be great if there was some kind of saved view preset option here because I'll often need to show multiple shots from the same camera but it can only ever have one focus at a time. I generally just solve this with multiple layers/objects but its frustrating to be talking about camera shots with a client and have to hop out of one camera and into another to show a different shot. This could tie into the permanent viewport too, with the viewport referencing a specific camera and a specific focus configuration -This would probably need to be another tool but it would be great to have a configurable Jib option as a stand type -This is probably getting too overkill for one tool but it would also be great to have the Camera Path tool baked in in some fashion to more directly create jib motion and dolly shots -a minor annoyance: Why are is the VariCam 35 Body white? I'm not doing anything that requires the exact camera bodies that are going into production so I tend to just wind up with this as the default, but it's white and sticks out like a sore thumb and I have to change it in classes or the symbol or change the body. White versions of this don't seem to exist in any half assed Google image searches I do. ūüėĄ I also have a heap of bugs I've been needing to file a proper report for but was waiting to see if 2021 magically fixed any of these.... They hit a couple, but I still have some doozies here if they're of any worth to anybody else to jump on. -I'm still encountering Symbol ghosting when using the tool. Example, insert any symbol (a chair symbol for example), switch to the video camera and it will show the outline of the previously used symbol as if you're inserting the symbol. Click and it will insert the camera but it will also leave behind the symbol outline which does not register as an actual object, cannot be interacted with and will only go away when you close and reload the file. (see image) -Layer Height isn't being factored into tool at all and having a camera on a layer set to anything other than 0 will make viewing anything through this camera completely wrong. -Mirroring a camera will break the Aim function because the object is mirrored. I end up with this whenever I'm quickly trying to mirror cameras across a center line if I don't remember to correct the flip. -The Aim function is helpful in getting started but doesn't seem to give me a usable tilt in any attempt I make. In 2D it always sets tilt to -20 and 3D seems to always go to +20. -The tool just does not play nice with the Multi View Panes and Mutli View Panes are made for this tool to see everything in 2D but have your camera views in other panes. I try to use this with a 2D view and a 3D camera view via the Activate Camera button and it will work fine at first but making changes can mess up the view panes. Like activating a camera in 3D and then trying to use aim in the 2D pane will completely break the view of the 2D pane and put it into 3D mode with a weird configuration. -Field of View has some general wonkiness. Again with Multi View Panes. The 2D FOV will not get drawn if the 3D is active. I generally only use 2D Show Field of View and it will not show when a 3D view is active which is very unhelpful when considering sightlines. -I just encountered this a few times in my 2021 tests, but haven't nailed down an exact cause to replicate it- Sometimes the drawn FOV breaks free of the plug in object and I had both 2D and 3D versions getting drawn as just individual line objects on the design layer not even lined up to their intended camera positions. These were entirely separate objects that I was able to delete so there's that at least. Old issues that were MAYBE fixed from 2020 to 2021 since I can't seem to replicate them with my limited tests: -The 3D Geometry of some of the camera lenses will end up in renders and block the shots. That was a super frustrating 2 hours of troubleshooting until I realized my renders were coming out solid cyan because it was rendering the camera lens. Looks like this might have been fixed or I just haven't hit the right settings to trigger the problem again. I was able to fix this by just turning off the camera classes in the viewport but sometimes I need to see other cameras in the shots to show when things aren't well hidden and this can get deceptive -The imported camera symbols were Purgable and made a mess of your cameras if you purged the symbols out of the drawing. This one looks to FINALLY fixed in 2021.
  2. I stumbled on the solution to this! Seems obvious it hindsight, but I didn't think the Name node would work on items in the Resource Library, only items in the drawing. Using the Name node and referencing the texture resource name will produce the handle you need for the Get Texture Size node to work. This is a bit clunky for scripting (at least as I'm trying to use it) but I made one minor tweak to the Get Texture Size node to pull the handle by name and the whole thing works the way it seems like it should now. I've attached a file with the modified node if it's of any use to anybody else. Enjoy! Get Texture Size v2.vwx
  3. I tried removing the first lines as you suggested and it doesn't make any difference for me- the new node doesn't function without plugging in an existing group handle. Removing those lines *shouldn't* affect anything- they're both comments that are unrelated to the execution of the script as you say. The first #COMMAND... is only to flag the script as read only. The only thing removing it should accomplish is allowing you to save any changes made. So if that's making the node function on your end that is quite bizarre... but seems to be par for the course for my experience with Marionette so far.
  4. I've noticed the Group node not functioning correctly lately as well and just assumed it had do to the usual marionette quirks and found other work-arounds. This post prompted me to open up the script and take a look. The node was updated in April and added 2 lines to the script to perform a conditional check before running the existing group script. Unfortunately my python is very limited and I'm not entirely sure what this code is meant to accomplish. The April 2020 Node will only function correctly when an existing group handle is provided. So it appears that the If statement is checking that the variable 'original' is a group Handle, and if so will run the rest of the script. With no group provided, 'original' returns 0, therefore isn't recognized as a handle and the code in the If portion does not execute and does no grouping. I think there should be an Else statement here with some slightly different code to create a new group when the If portion fails, but I don't follow why this would be necessary when the 2019 code worked fine without the change. Basically, this appears to just be a bug that should be reported as best I can tell. Maybe somebody with better python/vectorscript knowledge can shine some light on this and explain things if I'm wrong.
  5. Thanks Pat. I'm still confused- what you described is exactly what I was trying and I'm still coming up with a 0 float value on the Texture Size via both the Get Texture Reference and Get Texture nodes. The iTexRef value both nodes provide the index location for the texture (at least I'm assuming that's what this integer value represents?), which presumably should function as the handle here? The texture is currently set for 1" in the resource, so something is not quite right here. I've attached a test file for reference. TextureScaling.vwx
  6. I'm attempting to retrieve the size of a texture and the 'Get Texture Size' node seems to fit the bill, but I'm not able to figure out what input the node wants. I've tried the Get Texture node with both the string name and the integer id from this but neither seems to be what the vs.GetTextureSize() command in the node wants. The description and web info for this vectorscipt command are lacking. How do you interact with this node, or if not this node, how can i go about getting the size of a texture resource?
  7. ...Or using 159 does in fact work. Not sure what I did incorrectly the first time, but it's working now after another attempt. Love it when I solve problems by opening and closing the program...
  8. Not sure how much of this will be the same for 2016 as I know a lot of things were renamed and added later. You're looking for the Popup node. You'll have to Edit it with some minor changes to customize it though. 1-Remove the line at the very top "#COMMAND;READONLYREFFILE;[VWLibDef]/Input\PopupWidget.py;" (This is basically here to lock the node as read only) 2-Change the existing choice list. Keep everything in single quotes to establish strings and you can add more entries by separating them with a comma. This node only gives you Integer values for the item you select from the pop up. @MRoth has provided an excellent modified Pop up node that also provides the string text here:
  9. Continuing to mess around with this- I did find that using int 159 is actually the better usage for the Get function to retrieve just the Title without the Number. Doesnt seem to do anything to help the Setting problem.
  10. I'm attempting to make some nodes for interacting with a Sheet Layer's Sheet Title. I've been able to make the Get Title function work correctly (Although this does also grab the Sheet Number- any way to avoid this outside of scripting its removal?) but I can't seem to get the the Set function to work. I've also tried to just replacing the variable I've created with a string value without success. Here's the code as I've cobbled together and VWX is attached. Sheet Layer Marionette.vwx @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( 'Set Sheet Layer Title' ) this.SetDescription( 'Retrieves the sheet title from a sheet layer' ) #Input Ports obj = Marionette.PortIn(vs.Handle(0), 'hLayer') obj.SetDescription( "The input layer object") string = Marionette.PortIn( '[Sheet Title]', 'sTitle' ) string.SetDescription( 'The sheet layer title' ) #OIP Controls #Output Ports layer = Marionette.PortOut('hLayer') layer.SetDescription( "The handle for the layer" ) #BEHAVIOR def RunNode(self): #inputs x = self.Params.obj.value title = self.Params.string.value vs.SetObjectVariableString(x, 162,title) #script #outputs self.Params.layer.value=x
  11. Bah, of course it's that easy. Too busy staring at the field names on the fixtures and not thinking about what the record name is actually using. At least it a simple fix. Thanks!
  12. I'm using the Get Record Node to pull information from Spotlight Lighting Fixtures, and I'm getting everything I try just fine with the exception of Instrument Type which just returns a blank string. Anybody know what would cause this? Image and test file attached. MarionetteLightRecords.vwx
  13. I've been using the Ordered List along with the Concatenate Node to combine strings for my tools for a while now and have never had any issue with it. Recently, I've been having trouble getting this to function correctly as it has started giving me a list style string. In this example I'm just trying to create a simple #/# value display- just a simple / between two string values. I should be getting 1/23 from this however I'm getting ['1', '/', '23']. I've generally been working with the ComputerWorks Easy Text node, so I checked this against the stock Text node and the problem exists here too. The weird thing is that if I go back to my tools that have used this exact same method to generate text and copy/paste the Ordered List & Concat nodes into the file they work just fine and produce the previously expected results. Checking the script in the newly inserted nodes versus the copied node shows no difference- they match up exactly. Example file attached. Very confused with this and looking for some help or guidance on a better method for building strings? TextConcat.vwx
  14. The Set OIP node does not appear to function when the OIP Name has a space in it. Is there any trick to using Field Names with space to get the space to process? EDIT: Figured it out- just a simple underscore will replace the spaces just fine. Great node btw!
  15. It would be great to see the face counts of Mesh objects in the OIP for the mesh rather than having to go edit the mesh or find this number in the Simplify Mesh command.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

√ó
√ó
  • Create New...