Jump to content

scottmoore

Member
  • Content Count

    509
  • Joined

  • Last visited

Everything posted by scottmoore

  1. Unfortunately, I cannot open the file as there seems to be some concern about how the VW license was obtained. Is this a simple piece of geometry or did you actually utilize the line light tool (I am not even sure if there is a line light tool anymore). Assuming it is a piece of geometry, have you applied a glow texture to your line light? You appear to have a light source in the file, so that shouldn't be the issue. Do you have any refections enabled?
  2. A couple of Stream Deck questions for you power users: 1- When Jim mentioned where to find suitable graphic icons, he mentioned the "(Show Package Contents on 2019 app)" I am not sure I know how to do that. 2- Any wisdom on how to fire scripts with the Stream Deck. Thus far I am finding it to be a game changer. I am using it for features that either don't have a hot key assigned, or for functions like duplicate array and Label legend manager that require 4 keys to access.
  3. I am on 2020 and run into a lot of unusual behavior with regards to rendering. When I am in the drawing process, I do a lot of rendering directly on the drawing layer to see how my modeling is coming along. Quite often I will set my OpenGL settings to not include color or texture so that I can get a really quick version of a hidden line render that I can use to check modeling details. When I opt to render in Final Quality (which is plenty fast when just viewing one or two detail items) there are no texture present. If I change the setting in OpenGL (and typically change my view angle) then the textures come back in RenderWorks. Since when do OpenGL settings impact RenderWorks settings? I don’t believe this was ever the case before as I’ve been working like this for years.
  4. Correct. The LED tool is not designed to do irregular shapes. It just takes a few minutes to create the 3D geometry and map it though.
  5. Time to brush up on some VW skills I think!
  6. Pretty awful. We’ve lost all of our rental income and pretty much all of our event work. Not too optimistic on the three events left on the books in the next two months.
  7. Thank you for the update. I appreciate it.
  8. Hopefully. My complaint is this: calculating X, Y coordinates is really the first order of business for a rig point tool. 3D implementation, load calculations, and everything else are icing on the cake. If it can’t do that one simple thing without a workaround, that is a fundamental failure and should be job 1 as it were.
  9. As Spotlight endeavors to turn a Great CAD program into a plug and play solution, these kinds of details are, frankly, infuriating.
  10. Copy that. Ugh. All these tools that “sort of” work. It’s quite tedious and can certainly cause errors. Imagine the actual cost in labor and time if someone moved the origin, didn’t remember or even know they needed to refresh all the hoists, printed a coordinate sheet and hung an 80 point show completely wrong. Certainly within the realm of possibility.
  11. Thanks guys. I’ll look at the first piece of advice from Andy and see if that sorts out labeling. I am pretty sure the second issue is indeed a bug. The XY fields did not calculate initially until I toggled the relative dimensions on and off. Likewise, when I moved the origin I had to toggle the relative dimensions back on and off to get the correct data.
  12. I am trying out the Spotlight hoist tool for the first time and have some questions: 1.) Trying to use the Spotlight numbering tool. Selecting the “Hoist Number” field, setting the prefix to “L-“ and the start to “1”. When selecting hoists, the tool displays L-1, L-2, etc as one would expect. Once completed, all hoists still display “0” on both the hoist and OIP. The only way I can change the hoist number is to do it manually in the OIP. Also, it does not allow a prefix at all. 2.) I figured out how to remove the X,Y arrows so I am pretty thrilled about that. Now I am displaying the X, Y values from fields which I seriously prefer. The issue I now have is that the only way I can get the rigging point to display their actual XY location is to turn on “relative X,Y on plot” in the OIP and then turn it back off. otherwise I just get a value of 0. Any thoughts?
  13. My apologies. I am returning the same results as you. Class overrides impact the lens, but not the light source. Adjusting the actual class attributes will change the light source, but not in a viewport override.
  14. Attached is a test file. My assumption is you may still be relying on some bit of Spotlight functionality for lens and lamp coloration. This particular symbol is created from scratch and created on the specific classes that will line up with my design template. Basically, they are designed to be used specifically for rendering purposes. test.vwx
  15. If I am following you correctly, yes I can adjust the color of the instrument lens and light in a viewport by class, independently of the actual class setting. I have duplicated two viewports on a sheet layer. In one, I have a set of wash fixtures I have manually set to yellow by editing the class of the viewport. In the other, I have set them to green. On the design layer, the class in question is still blue. So, I am assuming that is what you are hoping to achieve,
  16. Actually no, I've not tried Class overrides. If I can keep VW from crashing every five minutes, I will give that a shot.
  17. Here are some screen grabs. I avoid anything to do with Spotlight symbols so all of mine are custom geometry. Very simple to draw but how they are drawn and textured makes all the difference. In the instance of this gobo fixture, I create the body as a hollow object and a generic texture, not using a translucent texture. The lens is translucent and by building it this way, I can place the lighting object where I want to optimize the beam spread across the lens. Any additional spill is captured by the shell of the fixture body.
  18. 2020. Mine are purpose built symbols NOT Spotlight symbols.
  19. I build my own symbols for rendering purposes and create them in individual classes per type of light and it’s orientation (floor or suspended). The lenses and lighting objects all receive their color by being assigned to “color by class”. Works like a charm. The 2D element also changes fill color to make it easier to track changes.
  20. I ran into a similar situation except directly on the design layer in 2020. If OpenGL is set to not display textures or colors, then Renderworks would not display them either. That does not make sense to me as I’ve always understood the OpenGL and Renderworks engine to be independent of one another but it was absolutely the case.
  21. Make sure you are on at least SP2. Either SP1 or SP2 fixed most of these issues. I am still seeing the occasional oddity, but for the most part, this texture issue is resolved. I have noticed changes to reflectivity setting in textures. I have some lacquer finishes that had a reflection percentage of 25% that now need to be dialed back to 5%-10% to look correct. Not necessarily a bad thing as that gives us more latitude with reflection settings, but it is definitely different. Agreed with your beta tester comment!
  22. This is all quite interesting to me. Seems like schematic view has a lot of potential. It is always disappointing when features are released before they are completely functional but that seems to be the case with many things. I don’t necessarily agree that drawing an item in 3D is “better” as that can often involve changing working planes but that may simply be a personal preference. After reading this I tested focus positions in DLVPs and sure enough, that no longer works. Rather disappointing.
  23. An image prop is probably the quickest way to create a facsimile of an Edison lamp unless you need a close-up.

 

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