Jump to content


  • Posts

  • Joined

  • Last visited


0 Neutral

Personal Information

  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello again, all, and I apologize for not responding sooner, it's been a busy start to my week. Well, I will be honest, because this seems like a very candid group, and I appreciate that. Plus, I can't hold back, because I honestly really, really want to love this program. So if I don't come correct with my inquiries, , I'll never know, and I will hold back on purchasing. So beyond my foisting these comments and questions upon you all, perhaps someone else can use this info in the future, and in that, I won't feel so selfish. So I'm just going to go down a list of thoughts and concerns that seem to linger: First: One person I read from in another forum stated his biggest regret with VW is that he felt as though, coming from whatever he had used before, he had traded 'simplicity', for "a forest of dialog boxes". So I can understand that at first, of course we have to get set up, but do these prompts follow us around, even after we've got a template set up? For instance, I noticed in the latest architectural online seminar (last week and the 2020 recording), it seemed the presenters use a generic wall type, to lay out there design, and then swapped those out for a library type further into the process. Similarly, I did not, after following them throughout the seminars, perceive a way to set the wall type, before I started designing. It seemed like vital info, but I missed it, or it wasn't there...(so this sounds like such a dumb q, but if I don't ask)...so can I set my wall types before I begin? A simply y/n works, I don't want to drag you all through things easily found. Now speaking of wall types, and getting my bim house in order, I must confess, in "R", I do hybrid bim, or lazy bim, all the time, and use generic wall types, then tag as "whatever" in the notes on the c/d. I suspect this may be a similar use case for many here? (also, in a related question, does Vectorworks have the capability to do material take-off, stud counts, etc., provided I set correct parameters)? And all of this leads to a very high desire of mine, to begin using VW as a true BIM is meant to be used. That is, all things BIM, all the time. But is this realistic, in a production setting, and especially, as most of us are very busy, right now? Second, because this issue still has me on edge; Revit is very, very much dependent upon levels (what appere to be stories, in VW). And that's where I'm still glazing over. I constantly, very much use levels, as a deeply ingrained part of my workflow, and in that, as an integral part of controlling everything from wall/beam heights, to window head-outs, etc. But mostly, levels simply control walls, and floorplate thickness/heights. So in that, one simply sets up their "story pole" using levels at the beginning of a new project, or forever in the template, and then forget about them until they are called upon for use. So before my first use, I honestly expected to see something obvious, like this, in VW, but I'm afraid, I'm still very much conflicted, because it feels like it's an implied rule break, that so many shun stories, while one here has said they use them, and VW is pushing the feature. So to be tactless, is this a flat earth issue, that in reality, is tied to comfort, or even speed VS., pedantic's? Or does it just not matter? And recall, most, I'm not saying I want to use stories, but imagine a bim manager having this discussion, in a large shop setting, even if they only ever did residential, and he/she didn't want his droogs breaking convention for convenience? So I'd also like to know if anyone actually loves stories, and if they see something different. (counterpoint). But most of all, I think VW would do well to address this issue, because from a traditional standards gal, I must admit I'm still fuzzed. So in your workflows, comparing VW to R, which "component" replaces "stories", or is it purely a workflow pref? (I'm going to go read the thread on stories now, I promise 🙂 ) And whichever route I end up in, can both be graphically represented in the condocs? (I know stories can) via level heads? Why: My condocs are typically very graphic/info rich, simply because my mentor beat it into my mind that one must show all downstream readers, of my docs, everything, (no guessing/no regrets). And so a very fascinating related aside, to me, is in last year's e-seminar the presenter alluded to the fact one can "break" story bound walls, for use in non story bound situations and workflows, and even went so far as to show us exactly how to do this. This year, not a peep about that (and I'm good with either, but is VW factory pushing us toward more story integrated workflows?). So once again, it just felt like more potential cognitive dissonance because of perceived mixed messaging, (although I do kind of like the idea of breaking rules, : ) ). My only concern would be then, once broken, does that wall then become non-intelligent/non-bim element? Third; one poster I read in on, mentioned, as of +- VW 2019, or so, there was no "reference plane" type of element. That would be a line that permeates all views, so that one may line up elements between floors, or to insure elements line up between split views, and so on. It seems to me that grid lines could be used as such hack, but if not, the poster mentioned he felt very insecure (at the time of his post), because without such a feature, building coordination between obscured elements could become eminately more error prone. And I have to agree. Ref planes inspire complete surety in element placement, regardless of how minimal, or costly. Which brings up one last final question, related to construction aids; is it possible to stack views, and make one transparent, as in onion skin overlaying views, for coordinating and cross checking? Up or down? So in closing, I'm not looking for answers to disqualify, or kill the deal. It would simply be very nice to understand where these features stand, if at all, so before I take the big bite out of the apple, I know exactly what I'm getting into. For instance, I do not 'love' Revit's MEP suite, but I'm hoping VW's is stupid enough, a 5 year old like myself could wade through it, without too much trouble. Or I just keep sending my docs out to the consultants. Anyway, I've said allot, and like I said, I am extremely intrigued by VW, because it feels more artistic, then Revit (could be the freeform and vector based tools, as well as the push pull bar). So I do want to start that relationship, with this guy, I just don't want, when the honeymoon is over, to feel like I made a bad choice. Thank you all so much, and I hope your workflows are flowing well, this week. Best, Moni
  2. To All: Thank you so much for your detailed, thoughtful responses. It is reassuring to understand such helpful individuals are contributing, to the benefit of others. I sincerely appreciate. Moni
  3. Hello all, I may be crazy, but I'm very seriously considering migrating to Vectorworks after almost 18 years in the "R" ecosystem (the new is now old). Where I've become almost immediately lost, however, is in the layer/story/level maze of options. One reason is the panoply of advise, from the tutorials I've seen, so far, to the stickies in this forum, that seem to be singing from different sheets of music. Use: I'm primarily involved in high end custom residential, and so I do not exceed 3 stories in height, although I do often have multiple plate lines, roof heights, as well as differing floor levels, often within a single, or 2 story home. To make things more complicated, although I get (presume?) that design levels are equivalent to revit levels, and sheet layers are equiv. to revit sheet views, it's just that their seems to be so many interconnections, that thicken the learning curve, and more, that it seems some users here are extolling the virtues of not using stories all together, while others seem to say the opposite (what does VW Architecture recommend, if anything?). So my first question assumes all of this is great (complexity), because it makes the system flexible, but I'm truly lost, and have no idea how to set up a template, that isn't going to bite me in the rear in 6-12 month, because of the seemingly subjective feeling on how this should happen. So I don't mean to spark another endless debate about something that's been covered endlessly, but can anyone make a recommendation to get me up to speed quickly? Or, a template/best practice workflow recommendation for my use case? Or, is it possible to find a simplified set of docs or a blog, that tells it to me like I'm 5? The bottom line is that I need to stay creative, and there are times when complexity kills creativity. Last, I can't find a good, current book on VW for architecture, so is anyone aware of a legacy publication that could serve as a foundation? In fact, I almost get the feeling learning the old, then progressing, could be a way forward. And you have my permission to call me old fashion, but I am very disappointed there seems to be a void of written word, in that, in a book I can hold in my hand (is anyone aware of when the last Vectorworks Architect manual was published?) Anyway, I've said allot, but I do have to confess if I wasn't intrigued, and if Vectorworks didn't look like a great platform, I wouldn't be here. It looks like a great suite of programs So I really look forward to diving in, and making this work, so I sure do appreciate any assistance. Best, Mo.
  • Create New...