Jump to content

rseybert

Member
  • Content Count

    81
  • Joined

  • Last visited

Everything posted by rseybert

  1. @Sam Jones Hmm. Maybe it's time for a reinstall of VW. It has been acting quick in the last few days with stuff that it's not had issues with before. I try to lock in settings as much as possible to help with consistency. Most of the Vectorworks object out of the box bring in some less than ideal classing structures. Not that it's a bad thing, they just don't work with our work flow. If I can make a red symbol out of it, I will:) Thanks for looking into it.
  2. I've created some multicable red symbols to help preserve custom settings and classing. Works great except when I try to move around (pressing the click-wheel on mouse) while the tool is active it stops the tool and sorta gets stuck between the pan tool and the multicable tool. It also grays out all menu bar options. The standard multicable tool seems to work properly. Closing the file will not stop the issue but a close and restart of Vectorworks will until I use the tool again. I've attached a screen recording as well as the file. Screen Recording 2020-02-15 at 5.35.14 PM.mov Multicable Bug.vwx
  3. @jcogdell Thanks! Much appreciated!
  4. @SCParker I have indeed looked into the Autoplot capabilities. If it were just me I would have purchased all the third party plus-ins available but that's not the case. I can't take the idea of purchasing/subscribing to a plethora of third-party plug-ins that would increase the financial footprint of a piece of software just help cover its shortfalls to the money people. And multiply that across the multiple users that need access to the plug-in. I do appreciate everything that the third party community is doing as its really driving the software developers see what its users need.
  5. @jcogdell And of course as soon as I posted that last post I found the "change trim height of system" button. Disregard my last post. Perhaps that button can be one of the first lines at the top of the object in the OIP. Thanks!
  6. @jcogdell Something else that seems to be an issue (at least for me) is that if I want to change the trim height of a truss system, I have to select all the truss in the system. Selecting one truss object and changing the "z" value does not change the "z" value of all connected truss objects.
  7. Sounds like it got knocked out of your workspace. You can add it back in by editing your workspace with the workspace editor.
  8. @Luis M Ruiz I've checked that a few times. I did notice that the fill color displays as set by class but the fill type displays as solid. When I try to change it to "by class" it snaps back to solid. Probably not related but perhaps worth mentioning. This is issue does only happen in viewports when the class has an override. Seems to work properly in design space.
  9. @jcogdell That would be greatly appreciated. Having that ability will allow me to really commit to using the cable tools. Also, If you have the ability to submit this one as well: - link jumper cable length and type to lighting device parameters - link data cable length and type to lighting device parameters Thanks!
  10. I found the preference dialogue box but when "lighting Device" is selected "Combine Cable ID and Break Out Number" is disabled. Can you only add this data to a record? None of the available lighting device related records have any circuit fields.
  11. @JBenghiat Thanks. I was able to get the texture sorted through the class settings. Of course, I set out to make a screen recording of the issue I was having and it decided to behave for the most part. I put some lekos on a pipe from top/plan view and they snapped fine. I then added some LED pars to the same pipe the same way and they were in the ground. However, the pipe did not change elevation when I chawed the elevation of the fixtures. I then changed the elevation of the pipe and the lekos track but the pars did not. I selected the pars and attached them to the pipe via the right-click menu "attach to rigging object" with no immediate change. Then I changed the elevation of the pipe and all four fixtures tracked with the change. Go figure. I'm gonna say this was a case of operator error. I know the rigging objects have been changing a little here and there and I'm sure this is some growing pains on my part. I'll keep an eye out and post if it happens again. Thanks again for the help.
  12. Hi All, Noticing a few issues with the Lighting Pipe tool: Lighting Pipes do not change texture or color fill in any render mode/view other than top/plan. All other render modes yield a white lighting pipe. Changing trim heights seems to be a bit tedious. If I draw a lighting pipe, set it's "Z" value, and then populate it with fixtures it tends to change its height on its own. Usually, it'll pop back to 0'-0" once the lighting fixtures have been added. If I change the "Z" value of the fixtures, either through the OIP or physically dragging to the pipe, the pipe will track with the movement and now be double the original height. If I then change the "Z" value of the pipe, the fixtures will be in the ground. Usually, after a few rounds of those steps, everything will cooperate and I can move on to the next position and do the same song and dance. I've noticed this in a few drawings now. Any insight would be greatly appreciated. Thanks.
  13. @markdd Do you see your workflow working without the AutoPlot tool set? My challenge is that I manage a few users and making sure everyone has this plug-in installed, up to date, and tracking with the various updates of the VW software is another step in the process. I would like to keep as much of our workflow within the confines of VW as much as possible and refrain from using third party plug-ins as much as possible. We utilize Project Sharing with our workflow and have had issues in the past with third party plug-ins. This is also the main reason why we cannot utilize Lightwright for paperwork purposes and instead rely on worksheets that I've created within VW. Thanks.
  14. @Daniel Dickman I feel like my previous post might have led you astray. Since then I, alongside a few others, have been testing the feature ad nauseam to see if we can figure out its kinks. Here is a list of what I have discovered with this feature, some of which will be useful to you. Schematic views do not like "Hanging Positions". It will react better to simple rigging objects like a "Lighting Pipe" or a "Lighting Pipe Ladder". I believe this was touched on in an earlier post in this thread or another. Not converting to a "Hanging Position" will yield a proper 2D Schematic View complete with accessories and Label Legends when "Top" is selected. Converting to a "Hanging Position" will yield an almost identical 2D version of the source geometry when "Top" is selected. When "Front" is selected, it will yield a "Hidden Line" version of the position with no accessory or label legend information attached. When label legends are populated by Schematic Views, classes that are associated with a label legend do control the Schematic Views display to a point. Allitems need to be classed appropriately. This means that containers need to have an appropriate class assigned to them not only at the label legend level but also within the symbol. This will be problematic if you're utilizing the same container symbol for more than one field. Schematic Views do not show "Modify Lighting Instrument Color" based on color field when selected in the Spotlight Preferences. Accessories will display in a schematic view, however, they're placed at the top of the Schematic View, not with the fixture they're assigned to. The spotlight numbering tool does work directly on the "Lighting Device In Schematic View" objects and the input is reflected appropriately. I hope this helps a little more. There is a pretty active thread on the subject matter. Here is the link:
  15. @markdd I'm actually talking about another webinar that was a recording of a Design Summit session last year. Did you touch on something similar in your webinar? I'll have to go back and rewatch.
  16. @markdd I'm not surprised at all that you responded to this. Ha ha. You are correct. I'm trying to change the color of a light object by altering its class settings in a viewport which was the workflow discussed in the webinar. I'm trying to leave actual lighting devices out of the workflow for now.
  17. Hi All, I recently watched a Vectorworks webinar that discussed some rendering workflows for the Entertainment industry. One of them was to use a renderworks light embedded in a generic 2d/3d symbol instead of an actual Lighting device to skirt around having to create a bunch of focus points all the work load that comes with that. I agree. The way the presenter controlled the color of the lists was through classing overrides in the various viewports, giving them enough flexibility to quickly make different lighting looks. they did this with the lens of fixture as well, allowing for a more realistic representation of a theatrical light. Whats was achieved by setting the texture assigned to the lens as color fill by object... which is set to class style. I'm trying to replicate this workflow and I cannot seem to get the render lights to behave correctly according to the webinar. Is it possible to control the lights in this fashion or is this another case of VW changing something between 2019 and 2020? The lens texture works just fine. I can see the light in the visualization palette but cannot edit its properties there as its buried inside a symbol definition. Thanks!
  18. @Daniel B. Chapman What happens if you recreate the schematic view after the addition of the accessories?
  19. @TomWhiteLight Thanks. We look forward to their advisement. I reviewed your file. Looks like you're creating a top schematic view of each ladder rung of a position (converted to a hanging position) as opposed to the position as a whole. I'm assuming you then recreated the whole position in an elevation view rung by rung, which works but seems time consuming when dealing with a large number of these type of positions. I posted my test file in the shared dropbox folder for you see. Perhaps you can send that off to the Dev team as well.
  20. @markdd @TomWhiteLight Hello all, Some really good responses in this thread. I feel like we're really getting after it here. I noodled around with it some more last night and this afternoon and discovered some interesting results. See attached screen capture. Schematic views do not like "Hanging Positions". It will react better to simple rigging objects like a "Lighting Pipe" or a "Lighting Pipe Ladder". I believe this was touched on in an earlier post in this thread or another. Not converting to a "Hanging Position" will yield a proper 2D Schematic View complete with accessories and Label Legends when "Top" is selected. Converting to a "Hanging Position" will yield an almost identical 2D version of the source geometry when "Top" is selected. When "Front" is selected, it will yield a "Hidden Line" version of the position with no accessory or label legend information attached. When label legends are populated by Schematic Views, classes that are associated with a label legend do control the Schematic Views display to a point. All items need to be classed appropriately. This means that containers need to have an appropriate class assigned to them not only at the label legend level but also within the symbol. This will be problematic if you're utilizing the same container symbol for more than one field. Schematic Views do not show "Modify Lighting Instrument Color" based on color field when selected in the Spotlight Preferences. Accessories will display in a schematic view, however, they're placed at the top of the Schematic View, not with the fixture they're assigned to. The spotlight numbering tool does work directly on the "Lighting Device In Schematic View" objects and the input is reflected appropriately. Clearly, not converting the rigging devices to hanging positions is the way to go with schematic views, however, this does create some issues in itself. Not converting means you lose the ability for auto numbering or proper "Z" values. Take the ladder tool for example. The hight of the object is is controlling the center, center,center of the object, not the very bottom. With a hanging position, its default is the bottom most bit of geometry is the base "Z" value. Even then, you can edit the position afterwards and move the objects around until you're happy with where the "Z" base is located. Another issue that I see is if you have bespoke symbols for hanging positions that are not rigging objects you have no choice but to convert them to hanging positions to make full use of the data that populates as schematic views do not populate without a rigging object or hanging position being selected. It's been said many times now that we (the users of the software) need some proper direction from the dev team on how this tool is to be utilized and what steps are needed to create the correct outcomes we're expecting. At the very least, reinstating the traditional methods until the tool is at full speed. I'm very excited to see the full potential of the tool but until it comes to fruition we're left with no recourse.
  21. @TomWhiteLight Can you please provide a link to the webinar you've been speaking of? The only content on the Vectorworks website related to Schematic Views is the original marketing videos. Thanks.
  22. @the.dreamer Probably not what you're looking for but maybe this will work: - Create a custom "lighting device" symbol representing a frame in the color scroll. Could be a simple rectangle. - Assign the geometry within the symbol to a class, something like "Lighting-Notes-Gel Color". - Navigate to Document Settings>Spotlight Preferences> classes and color. Enable "modify lighting instrument color". Select "color field" and "use color field for the fill color". Next to the "modify only geometry in the class:" select the class you wish to modify... in this example it would be Lighting-Notes-Gel Color. - Once you save those settings you should be able to input the color field at the symbol and the fill will change to represent that color. - Take it a step further and add a label legend that only displays the color field. Again, might not be exactly what you're trying to accomplish but it's at least a way to graphically represent the gel string.
  23. @Daniel Dickman Schematic views are huge work in progress. Currently, the Schematic Views function simply creates a plug-in object that is essentially a 2D "Hidden Line" representation of a fixture or hanging position from the view that you specify. You can interact with the lighting fixtures at the schematic view level by selecting the fixture and the clicking on Lighting Device Properties. This will open up the "Lighting Device Properties" that looks similar to what would be displayed in the OIP. I've had some success using the Spotlight Numbering Tool on the Schematic View objects. Unfortunately, none of this information can be displayed graphically at the schematic view level so trying to keep track of what fixtures are what is pretty difficult when you're working with a large volume of fixtures. There are few posts in the forum discussing the inadequacies of this new feature at length. It seems like its on the dev teams radar to make it more functional but who knows when they're going to roll out the fixes. I've been beating my head up against this feature over the last week trying to draw vertical positions with no luck.
  24. @TomWhiteLight I would appreciate a shard file. Hopefully, it will shed some light on how this is used in other applications other than my own unique workflow and I'm all for learning. I too understand that it's still in its infancy, however, disrupting workflow because of it is less than ideal. Top view schematic views are fine. What I'm having issues with are the vertical positions and displaying the data correctly without having to create additional steps in the workflow to obtain that data... even though it could just be temporary until VW releases a full functioning iteration of the tool. I'm also seeing that 3D label legends do not display in a schematic view. Photo attached for reference. Furthermore, not arguing the practicality of drawing the elements in 3D where they actually live within the space. Speaking as part of a team that produces large scale bespoke corporate events and theatrical productions, we strive for as much accuracy as possible in the pre-production phase... some would venture to say too much. Time wasted on-site translates to wasted money and the number crunchers get really itchy when that happens. I do utilize Vision as my pre-viz solution when time/budget allows for it, so I can appreciate Vectorworks strides toward making the transition between the two programs more streamlined. My argument is how that data is displayed once its created/drawn for the practicality of creating shop build drawings and installation drawings. Something I'm going to noodle around with is taking the varied levels of detail (Low, Medium, High) that you can apply to symbols and see if I can get Schematic Views to spit them out as well. Perhaps that would be a temporary solution until this gets fine tuned. @Sebastiaan I completely agree that 3D first is a valid argument. See above. I'm generally not the first person to interact with a design before I'm tasked with detailing it out. I am tasked, however, with making sure that those above me starting the design have the tools they need to initiate said design. If they need to draw something up real quick but don't necessarily possess the skills (or patience) needed to draw in 3D first they will draw in 2D first and deal with the 3D later... but that is an argument saved for a different forum. The other concern I have is that the graphical representation and the details within that comes with the 2D symbols are lost, especially when traditional fixtures come into play that are represented graphically. Things like gel color representation in color fill, lensing, lamp wattage, and fixture orientation to name a few. In my experience, these are details that are best represented graphically for quick reference, clarity and to save space on the drawing.

 

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...