Jump to content

Andy Broomell

Member
  • Content Count

    1,434
  • Joined

  • Last visited

Everything posted by Andy Broomell

  1. BTW it seems this script has to be run every time the file is re-opened.
  2. And keep in mind this goes hand-in-hand with the literal size of your viewport. The number of pixels rendered is a product of the viewport size and the raster DPI.
  3. @Judy Cosgrove Unfortunately no; I'll be in a VR class at LAAFA tomorrow. But tell everyone at the meeting to upvote this topic - I'm sure that'd make @Kevin McAllister happy 😉 (I sadly can't make the October meeting either as I'll be in an airplane over the Atlantic Ocean that day. Hopefully November!)
  4. I want to bump this topic, because these days a gumball-style interface is a fundamental thing that users expect a 3D modeling program to have, and somehow Vectorworks still doesn't have it despite touting its 3D-modeling capabilities. I'm obviously a fan of Vectorworks, and have generally loved 2020 so far, but this particular missing element is pretty alarming. I teach Vectorworks to a lot of students who have prior experience in SketchUp or other design programs. When we jump into 3D working environments I actually feel a little embarrassed about how difficult/unintuitive it can be to simply move something in a 3D view along a particular axis, or to rotate something interactively in 3D. I have to apologize for the program not having these fundamental abilities (that is, without an advanced knowledge of working planes, snapping idiosyncrasies, etc.). We're doing basic 3D modeling and students are already tripping up... It puts a lot of people off from Vectorworks; I've seen it first hand. Moving, rotating, and scaling in 3D should be easy. If you want to attract and retain new users, a gumball dagger needs to be at the top of the priority list. It's useful across all industries that work in 3D. The gumball has existed within Subdivision editing for a couple years now. There's obviously some level of coding already done, now it just needs to be expanded. While this honestly should have been implemented in 2020, I'll continue holding out hope for 2021.
  5. Thank you for the workaround, Juan! I have no comprehension of what it's doing, but it works 🙌
  6. It does appear that Interior Elevation markers that are linked to viewports are indeed stuck to the layer plane. Not sure why. The Interior Elevation Marker tool in the Dims/Notes toolset does let you insert a marker that you can move upward on the Z axis, but this would be unrelated to your current marker and is a workaround since it wouldn't be connected to your elevations.
  7. Thank you thank you thank you thank you thank you thank you!
  8. Agreed. Scrolling isn't difficult.
  9. This just screwed me over on a project. This bug still persists in 2020. 😕
  10. I actually kind of like the change after playing around with it. In the past I'd usually avoid these two modes because I'd often accidentally engage a selection marquee when just trying to click something. This helps make it more reliable (i.e. it marquees only when intentional) and consistent, though it does take a moment to get used to if accustomed to the previous way.
  11. By the way, I placed an instance of this worksheet INSIDE my TBB so it automatically comes in with my title blocks and becomes a small printed sheet list on every page. Works like a charm 🙂
  12. Interesting. We think along similar lines. My workspace uses: W: wand (select similar) R: rotate T: trim O: offset S: scissors (trim) F: fillet K: knife (split) L: connect/combine (looks like an L) M: mirror etc... It's amazing how much faster my drafting process became once I set up hotkeys that are actually usable. Most of the defaults are too complex, which is a result of half the keyboard usually being eaten up by the mode group and snapping hotkeys, which I seldom use. At some point I might clean up my workspace a bit and post it on the forum - it'd be interesting to see other people's. Already getting too off topic here, haha.
  13. What key did you assign to suspend snapping, since I believe that's tilde be default?
  14. Thanks Pat! Didn't see this till now somehow. Does there happen to be a call for selected objects that are on layers that are both visible and currently editable? (Or if not, perhaps on the Active Layer only?) I run into issues when I have Layer Options set to "Show/Snap" others: I can technically have objects on the non-active layer selected, but the OIP only tells me what I have selected on the active layer. What happens is I don't realize that a script might be acting on objects that are on a visible (but not active or editable) layer since the OIP is not telling me I have them selected. As an example... the lovely "Rotate Randomly" script that you wrote for me a while back (and that I use all the time) has occasionally left me parts of the entire venue rotated since there were objects selected on the non-active layer. Just trying to fool-proof against myself 🙂
  15. I use Perspective Distance all the time in Vectorworks to change the amount of perspective in my view. I understand its function, but it just occurred to me that I don't understand what the value actually is. Does it relate to something in a physical camera? For RW Cameras there's the "Field of View" parameter which alters the exact same thing, but in that case it's easier to understand what the number is referencing. Just curious 🙂
  16. Loving this. Both of these are the same file, top is 2020: I wonder if this adds a couple seconds opening and closing files, in order to compress/decompress? Regardless, it's worth it.
  17. @Pat Stanford Once again, you are BRILLIANT. Thank you thank you! I copied my new Worksheet into a blank file, below, in case anyone else would like to utilize it. It relies on a Title Block Border object being on each sheet. I also set the criteria to exclude sheets with TBBs that have "This Title Block is Active" unchecked. Sheet List Linked to TBB v2020.vwx Sheet List Linked to TBB v2019.vwx
  18. The more I use VW2020 the less I like these new icons. Readability is very poor on many of them, and readability should be the number one important factor for any icon, above all else. vs the new: Some are fine, such as the tools within the 3D Modeling toolset for example. But otherwise this concept of white linework with thin black outlines does NOT work on a light interface. Can't we just have simple solid lines / silhouettes? Clean, simple, readable, modern?
  19. Ever since Title Blocks were revamped a couple years ago, I've been unable to create a simple Drawing Schedule (list of sheets) as a worksheet that's linked to my Sheet Layers / Title Blocks. It used to be as simple as pulling record fields from the Title Blocks, but that doesn't seem to work anymore, so I'm obviously missing something. Note that I DO NOT want to use Tools < Reports < Create Sheet List, as this creates an unlinked worksheet (an idea with I completely loathe). In my workflow I constantly re-name and re-number sheets throughout a project, so I need a worksheet that is always up to date without having to manually do anything. I see that it's possible to pull some data from TBBs, as seen in the screenshot of my test below: All I really need is 'Sheet Data'.'Sheet Title' but that doesn't seem to work? For my first column I just used =L in the column header which works fine to pull the sheet layer number. Here's an image of my simple goal, which I had in VW2017: @Nikolay Zhelyazkov @Pat Stanford
  20. Update: OpenGL viewports seem to randomly switch between rendering with color and without every few times I update them... And not even consistently across a sheet. Very frustrating.
  21. I'm still on High Sierra: I'm finding that once a Viewport is created, toggling either "Use Textures" or "Use Colors" under OpenGL Background Render settings seems to have no effect; the viewport just keeps rendering with the settings it had when it was created. If I want a white model viewport I have to make sure it's set that way before making the viewport... This is the first substantial bug I've seen in 2020 that severely interrupts workflow.
  22. History-based modeling didn't exist at all (sans ungrouping) for certain object types, such as 3D fillets, chamfers, and shells. Having this is HUGE in my book. It brings these tools in line with other 3D tools that already had history-based modeling.
  23. The OpenGL speed improvements that were discussed in a Teaser Tuesday are immediately noticeable. I was able to load a complex model in OpenGL and navigate much more quickly than in previous versions, which is a welcomed improvement! All of the icons in the program were redrawn. Some for the better, some will take some getting used to. Looking forward to that full UI redesign some day!

 

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