Jump to content


  • Posts

  • Joined

  • Last visited


46 Great


Personal Information

  • Occupation
  • Location

Recent Profile Visitors

1,774 profile views
  1. @Tom W. thanks for your reply - useful to know that ideal offer this. However it still involves a lot of extra steps for very early stage design, where really I would expect generic details which comply with the standards to be pretty much a tickbox exercise on the door symbol itself. i.e. an option for default door symbol of 'Doc M compliant' which then gives you all these items without having to hunt for them or load them in yourself.. Bare in mind we use these in literally every project we do (outside of small scale standard residential projects) so it comes up quite often!
  2. Thanks @zoomer that fits with what I've read elsewhere, I think we'll stick with radeon/ geforce then! It would be great if Vectorworks could issue some official guidance on this, covering futureproofing as well (presumably there are things on the roadmap for Vectorworks that we don't know about which may affect hardware requirements going forwards..)
  3. Any chance of an update to this list and a bit more info, based on the latest hardware/ vwx software combo's? Would also be good to get an idea of.. 1) How the more modern integrated graphics (i.e. from the current gen ryzen 7 and intel core i7 chips) perform in comparison to discreet gpu's as well. 2) Whether quadro's / firepro cards are worth paying extra for, or if better off with run of the mill radeon / geforce cards.
  4. Yes unfortunately how we also have to do things, but it is a pain and results in a lot of uneccessary duplication of viewports. Thus the wishlist!
  5. I also sometimes use the layer referencing method for this exact reason - but generally the viewport referencing method is better. So would like to have this same flexibility.. I've tried with the checkboxes both ticked and unticked, doesn't seem to make a difference to the visibility of classes in referenced viewports; either I'm missing something obvious, or the overrides don't work for this particular scenario! Its quite easy to replicate, simply make a file with a few lines on different classes, then reference into a new file. Create a design layer reference viewport, then create a sheet layer with a viewport containing the referenced viewport. The visibilities of the sheet viewport won't affect the objects in the reference viewport. See screenshots from test file below. I am aiming for the pink line to have disapeared in both boxes, but as you can see it is still present on the right hand box. In order to get it not to display, it has to be turned off in the reference viewport on the design layer. But of course if I am referencing this information in more than one sheet, I may want it turned on in some cases but not others.
  6. Hi All, It is a constant frustration that when using viewports on sheets, which in turn show content from reference viewports in the modelspace/design layer, you cannot override the visiblity of the reference viewport. i.e. I have a section referenced in from another file. The reference viewport displays some information which is useful for my working process (room data tags or levels, say), but I want these turned off on the sheet output. Unless I have missed something, there is no way to override the visibility of classes in the sheet viewport; instead you have to turn off information in the design layer (reference) viewport. P.S. If there is already a way to do this, please someone let me know!
  7. Great to hear! Any chance of a seminar / video on this now that its all operational?
  8. Has there been any development on this in the last couple of vwx releases? Having a similar (although much less severe) version of this issue now and was hoping for a quick fix..
  9. Thanks - when I follow your example seems to work fine! I wonder what I was doing previously then... perhaps I didn't have the first vertex mode selected. I 'll see if i can repeat the issue and follow up if I run into trouble again..
  10. Hi All, This ones been bugging me for years and I'm sure its very simple, but never worked it out. How do I edit handles for an existing curve? i.e. see screenshots attached, the handles only appear when the point is selected, so I can't select them. Thanks, A
  11. Great to hear! Still using 2019 at the moment, looking forwards to moving to 2020 when starting a new project.
  12. Well a promise is a promise! On a more practical side, here is a consolidated list of suggestions for anyone looking in the future (shout me if I missed any). Selection Tool (X) Double Click Paste in Place Escape (x2) to exit text editing etc. Move by Points Undo / Redo Open GL (and other render mode options) cmd-[ and cmd-] (previous and next layers etc.) Activate class Flyover mode Camera (top down plan, perspectives, etc.) Zoom to Objects / page area Toggle mode (left, right) Duplicate Array Select Similar Find and modify
  13. Good evening all - as promised! Thanks to you all for your tips (or pointers should I say), on using my mouse in a more effective way. I've tried them all out, there were quite a few, from move-by-points to flyover, activate and redo. Its hard to pick a winner, I'd like to use them all, I wish I had a bigger mouse, now it seems a bit too small. But It is @Taproots top tip, about group modes hencewith, that I'll be picking to keep when I'm through. Cycling selection types, wall junctions, polygons and end caps, Theres a lot you can do changing modes forth and back. You've saved my arm from making some unnecessary movements, thanks once again for your suggested improvements. A
  14. So I've just got around to reviewing the latest couple of posts on here. I must admit I am impressed with the breadth of ideas people have come up with. This is going to be trickier than I thought! Judgement delayed once more so I can test a couple of the newest suggestions..
  15. Hi All, Will give this a couple more days until Monday, but have been testing a couple of these today and possibly have a winner in mind 😉
  • Create New...