Andy Broomell

  • Content count

  • Joined

  • Last visited

Community Reputation

232 Spectacular


About Andy Broomell

  • Rank
    500 Club

Personal Information

  • Homepage
  • Location
    Los Angeles

Recent Profile Visitors

1,568 profile views
  1. Bump. Would love to see this in 2019!
  2. Yes! An example of current shortcomings:
  3. The main reason I think this suggestion would be useful is that sometimes with a complex file a view undo takes some time to redraw, and if I know I have to go back about 5 steps I don't want to have to wait for every step to redraw.
  4. Interesting. How so?
  5. Agreed that there should never be an instance where you can't stop a render. It's gotten better over the years, but it still happens. But to double check, if you're doing a lot of rendering, have you tried rendering with sheet layer viewports?
  6. Now what I do is immediately hit Cmd+X to "Cut," then click where I want and Cmd+V to Paste.
  7. The first few times I ever tried making an Image Prop I thought it just "didn't work". Then I later found all the image props I had made just sitting at 0,0.
  8. You might also try using the Model<Create Image Prop function.
  9. For now, the one thing you can do (if they are layers, not classes) and if you're working with sheet layer viewports, is to click your viewport, click the Layers button, click Edit for a layer, and reduce the opacity slider. (This is similar to Viewport Class Overrides.) But yes, it'd be nice to have further control over the display of greyed classes/layers.
  10. Interesting idea! It would be nice to have the ability to lock entire layers. In the meantime (and you may already know this) you can "Lock" individual objects which makes them uneditable, but still visible and switchable with classes. But there is no password protection, so any user can simply unlock the objects if they want to edit something. But at least it's a deterrent, and many users might not know how to unlock things in the first place. So in your case for now you'd select all the objects on a layer, and go to Modify<Lock.
  11. Can you attach your working file where you're experiencing the issue? It'd be easier to trouble shoot with that file, rather than the resource file from which you pulled the symbols. As you probably know, once you insert an instrument from a resource file into your drawing, it actually imports the symbol definition directly into your file, and is no longer related to the symbol definition in the resource file (unless you're referencing symbols which I assume not). So the resource file is in some ways irrelevant. In the Resource Browser if you click the Home icon you'll see the symbols that exist within your file, and that's where you want to make sure the symbol's name matches the OIP Symbol Name precisely. Perhaps you've already checked this and you're actually experiencing a bug, but it's good to run down through all the steps of what might be causing your issue
  12. Edit.... Sorry, I misinterpreted the question. Perhaps select the Viewport and see if the Attributes Palette has Drop Shadows turned on for the entire Viewport object?
  13. If you're creating renderings with Renderworks (as opposed to just working in OpenGL), I'd also recommend turning on Indirect Lighting. The number of bounces varies depending on your VW version. Indirect Lighting will emulate the lighting bouncing off the stage floor and hitting other surfaces in the room, slightly illuminating other objects in the space (but more subtle and realistic than the "Ambient Lighting" which is too smooth and fake looking).
  14. Are you able to attach the file so we can take a closer look at what might be happening?
  15. What menu is this? Does it exist on Macs?