Jump to content

Diamond

Member
  • Content Count

    716
  • Joined

  • Last visited

Posts posted by Diamond


  1. 5 hours ago, Christiaan said:

    Couple of things to bear in mind if you split sections off into a file separate from the model file is that you'll lose the ability to use Section in Place. And in my experience  Section Viewports in referenced files are notoriously buggy.

    Yup. And section reference markers. Depending on the project and skill level of the team, we use a hybrid 2D/3D process, so these feature aren't always important.

     

    5 hours ago, Christiaan said:

    Section Viewports in referenced files are notoriously buggy

    I find using layer referencing as apposed to viewport referencing achieves better results for sections and elevations in a referenced file. But then it does bring in all of the resources of the referenced file, and I find stairs linked between storeys can bug out.

     

    On the flip-side splitting a project up into multiple files provides some redundancy if a file is corrupted.

     

    No one said managing large projects was easy 😉.

     

    Hopefully project sharing in 2019 is more robust. We have been having huge challenges with project permissions and changes not being submitted. It can get cray-cray when you have more than ~3 people on the same file. @Christiaan, @zoomer Any suggestions how you manage this?

     


  2. Yes, large projects can be a challenge to manage. Beyond the software, I find the team is the most challenging part (requiring each team member to put on their big boy/girl pants 😉). Team members will often begrudgingly only use unfamiliar workflows unless forced – but that is all part of going to the next level in their skill level.

     

    On 2/26/2019 at 7:44 AM, zoomer said:

    Maybe there is some improvement potential in how the geometry is generated.

    (E.g. more use of Symbols, deleting Object History, ....)

    1. As per Zoomer's comment, invest in your libraries by making sure you are using symbols as much as possible. If you have purely 3D symbol's, convert them to hybrid symbols (or auto-hyrid objects if appropriate0 as much a possible. 3D geometry can slow down redraw times dramatically in Top/Plan views.

     

    2. Use saved views to switch between levels and working states. Using the Navigation Palette, and viewport visibility settings is okay for basic switching on smaller projects. But saved view will really switch up your navigation between levels and drawing states (that is, general arrangement plans, RCP's, Floor Finishes, Slab Setout, and so on).  

     

    3. Echoing points 1 and 2, as much as you can, turn off 3D geometry, or complex 2D (such as site survey's, and so on).

     

    4. Objects need to be classed correctly. One renegade team member can really throw a spanner in the works by using objects assigned to the wrong class.

     

    5. Work on your templates and standards. Keep them simple enough for small projects, but be able to import classes and layers from your standard files.

     

    On 2/28/2019 at 11:17 AM, Chad Hamilton HAarchs said:

    I'm not a fan of separating models by floor, because then coordination between floors becomes more difficult.

    I concur.

     

    On 2/26/2019 at 10:39 PM, Christiaan said:

    We tend to break up large projects into model file + sheet layer file.

    Once again, I concur. Although this is an option I would generally only recommend for rendered 3D views, as Saved Viewport Cache can dramatically increase file size.

    Alternatively, we tend to break up files into

    • Survey, site, + terrain
    • Model + plans
    • Sections, elevations, + details

     

    HTH.


  3. Markdd,

     

    Nailed it! I cannot believe I have not seen that before! For the last couple of years, this tool has been giving me no end of grief. I am meant to know this stuff. Now I feel like a goose. Thanks for the fresh eyes.

     

    Time to serve up some humble pie. But doesn't it taste good? ! ;) 

     

    Thanks again.


  4. These bugs are still present in Vw 2018 SP3. We do a lot of masterplanning using the space tool. It used to work, but in the last few of versions of Vw it has been broken. I really don't want to have to recommend we move back to Vw 2015 just to make this work.

     

    1. When I adjust the gross height, the space object gets moved down to 0 height.

    This is an annoyance. I can work around this. The next bugs I can't.

    image.thumb.png.c54644ca255fa9e1efd8973825b47d49.png

     

     

    2. The class transparency attributes on the 2D boundary class are still not adopted.

    The 2D outline of the Space should take on the line style, fill and opacity settings of the 2D boundary class. It does take on the line style and fill, just not the transparency settings

    image.thumb.png.940d038766c5dd15f5f770c689f73a5b.png

     

     

    3. When I attempt to apply classes with textures to the 3D boundary class, no texture appears.

    Textures will render, but only in Renderworks. Renderworks won’t render colour, and OpenGL won’t render colour or texture of space objects.

    image.thumb.png.80999e485d88f587e94b3e05cca18f13.png

     

     

    4. Vw Example File

    The Space Tool used to do all of this in Vw 2015. I need – :

    • The Space Name and the 2D Boundary outline to be opaque,
    • The 2D Boundary fill to be transparent,
    • And the 3D Boundary to render textures and colours correctly in OpenGL and Renderworks.

     

    I want to place the objects in a 'Space-Main' class, with the 2D and 3D boundaries to be assigned to transparent filled 'Zone' classes.  The example on the left shows this. You will notice the 2D boundary fill displayed opaque even though the class fill is set to 40%.

     

     The right example shows the overall object assigned to class 'Space-Zone-A' transparent because the Zone classes' fill is set to 40%. But doing this then sets the object's outline and text to 40% transparency (which I don't want).

     

    At the moment my only solution is to use text, and slabs or 2D polygons and 3D extrudes to get the same result. I would love to know if I I am doing something wrong.

    Thanks.  
     

     

     

     

    Space Tool Bugs.vwx


  5. Nice work gents. Great thread. Off line I have kept pulling to see how far it would go…

     

    @Alan Woodwell To clarify @Markvlcomments, to use the ID Label tool with walls, you need to have wall styles applied.

    Regarding wall style/type schedules, the information attached to the wall styles can be used in a worksheet whether you chose to use the ID Label tool or not. But if you had gone to the trouble of creating wall styles and named them to your studio standard (in the mark field), why wouldn't you use the ID Label tool?

     

    @MarkvlThe marker symbols appear to be coming from this file. Whilst you may not be able to rename the symbol (I am checking on that) you should be able to reformat them. The only issue with that is you need to update (or check the file has not been updated) for each new Vectorworks install or service pack (Swapping out default base files is not for the faint of heart ;).

    5a3043bef1d6d_ScreenShot2017-12-13at8_00_06am.thumb.png.ab728be4083b96ffd669465909ac983d.png

     

    PS You can set the ID marker style defaults in the options dialogue of the ID/Specification prompt.

    5a3052dc5672a_ScreenShot2017-12-13at9_05_06am.thumb.png.ab643978be81599be40f063731637ce8.png

     

    Cheers.


  6. Hi Kevin,

     

    1 hour ago, Kevin McAllister said:

    The current method of incremental steps seems to be making random interface choices without an overall plan. Someone needs to make an overall plan..... at least the marketing material of the last two years has that.

    Yes, the last couple of years of marketing material does show a considered and consistent UI message.

     

    On this topic in other threads, people (including myself) have asked for dramatic overhaul of the UI. We saw how well that went down for Apple with the Final Cut Pro 7 to X change over. Vectorworks Inc only has one baby.  My new thinking is that changing too much, too quickly would not be good for the tool.

     

    What I didn't make clear when I mentioned incremental change, is that I believe it needs to happen within a masterplan. Focusing on one or or two UI areas each year would overhaul almost all troublesome UI in about three years. In that timeframe, each software release would make these changes easily digestible.

     


  7. 8 hours ago, zoomer said:

    Of course VW would need a GUI.

     

    I like the functional look of the "stylized" Palettes that are always shown instead of VW

    palettes in the Teaser Videos when a new VW version gets released.

     

    I think those look pretty, but they may may not work from a functional point of view. Maybe this type of styling could be the long term goal. With annual releases and subscriptions, incremental steps is the key. For now legibility and usability should be the main goal. Good presentation should be a by-product of this.

     

    With our own work, we can get too close to it. Sometimes we need to stand back and see the bigger picture. If there is something in the current Vectorworks code that doesn't support this quality of legibility and usability, now is the time for Vectorworks to assign the resources to start the journey.

     

    Am I being fair in my appraisal?


  8. Hi all,

     

    Interface seems to be one of my favourite forum topics. This is a conversation I am having with my local distributor.

     

    I would consider myself a master user of the app, and I am by no means asking for a dumbing down of the software. What I am asking VWI for is to start reviewing the usability and legibility of the tool. I love the new features that are added from year to year, but I feel that features are being added without proper consideration to layout and interface design.

     

    Some examples of what I believe  poor interface/usability are - :

    • The new titleblock tool (too many front facing options),
    • The slab tool (editing is no where near a s simple as the Floor command object),
    • Rr the structural member tool (confusing in layout and how it relates to Framing Member and Columns Tools).

     

    I may go into these at a later date, but for now a perfect example is the Pilaster object's preferences dialogue window (See my attached markup below comparing the pilaster object with an app that I believe uses better design technique in this area).

     

    I would suggest with some input from a inclusive design consultant, and applying simple graphic / UI design techniques Vectorworks could bring more order (and approachability/usability) to an app that year by year becomes more laden with long lists of parameters in dialogue and palettes. Yes, with the complexity of modern architecture, we need more settings. But the settings should be as simple as possible to comprehend quickly. Deeper settings can be nested and revealed as required. And with the use of styles, the more complex settings are often not required to be seen most of the time.

     

    What do you think?

     

    Cheers.

     

    5a1f4250b4fcb_VectorworksInterfaceComments20171130.thumb.jpg.c0a65aece48459b36b48b1b71eeed907.jpg

     


  9. Yes, to get around this we will take a screen shots (and sometimes use saved views – which can save clip cube settings), but that doesn't get around the availability of other render styles (or at least I don't think so because I haven't tested anything other than OpenGL with Clip Cube). 


  10. On 30/06/2017 at 11:47 AM, Matt Overton said:

    I think there is a stack of interesting things you could do with both ARKit and Vision-ML for the cad world.

     

    I agree. I think Microsofts Hololens has been the leader in this area. The real issue is having hardware that can access it. For Apple's implementation, any iPhone that is 6S or newer with run ARkit, which, when iOS 11 is released in September, makes it automatically the biggest AR platform by far.

     

    With the announcement of ARkit, I suspect Apple put a number companies out of business overnight.


  11. And so…

     

    Whilst we are always searching for team members with the right fit, at the moment we are looking for candidates with solid Vectorworks experience in our Sydney and Melbourne studios. 

     

    Specifically, we are looking for –:

    • Strong Project Architect/Leaders (Vectorworks experience is preferable, but role does would not require a high Vectorworks proficiency. Must be willing to learn the basics of Vectorworks).
    • Architects/Graduates (High Vectorworks proficiency is preferred, but exceptions might be made depending on fit. Must be willing to learn Vectorworks to a high degree of proficiency).
    • Interior Designers (High Vectorworks proficiency is preferred, but exceptions might be made depending on fit. Must be willing to learn Vectorworks to a high degree of proficiency).

    Some information about us…

    We are a medium sized design firm.

    We work across three key disciplines: Architecture. Interior Design. Masterplanning.

    We focus on the following market sectors, bringing diverse expertise and experience:

      • Consumer: Retail, leisure, hospitality, entertainment.

      • Community: Education, residential, community, leisure, retirement.

      • Commercial: Workplace, commercial.

     

    If you are interested, please contact me via private message (hover over my user name and select message).

     

    Warm regards,

    Troy

     

    • Like 1

  12. 14 hours ago, JimW said:

    I personally would be quite pleased with users finding/offering work opportunities through the board, go right ahead. If it becomes a frequent occurrence I'll look into creating a subforum dedicated to it.

     

    Thanks for that Jim. I'll take that as a green light.


  13. Hi Guys,

     

    Have been looking at the import attributes dialog (select Viewport > OIP > Classes… > Import…). What is the purpose of the Viewport Class Properties > Import Attributes dialog?

    There are some features of this dialog that make sense. These are – :

    • Importing attributes from referenced Viewports.
    • Maybe having referenced viewports take on the attributes of their residing document?
    • Transferring Class overrides between Viewports.
    • Any others you can think of?

     

    But what I am trying to get my head is, "Why would want to import Class attributes from the document Class attributes? Isn't this the same function as the Revert button? Any clues as to it's purpose?"

     

    Thanks.

     

    From Vw Help

    Opens the Import Attributes dialog box, to import the class attribute settings from the file. The attributes can be imported for the classes selected in the Viewport Class Properties dialog box, from corresponding classes, or from a specified class in the file or a specified viewport.

    Click OK to import the class attributes into the selected viewport. (The Eyedropper tool can also transfer class override attributes between viewports.)

     

    Screen Shot 2017-01-17 at 5.55.44 pm.pngScreen Shot 2017-01-17 at 5.23.28 pm.png

     


  14. On 13/01/2017 at 8:40 PM, Christiaan said:

    I've finally had it, I've given up on thinking Apple will ever fix Preview.app.

    Yup. They have had a roasting on this recently. Trying to unify the core code of their OSes. Released way before it was ready.

     

    I use occasionally use PDF Pen for OCR and markup. Great for working with text. Can convert PDF to Word for editing and back to PDF. Both on Mac and iOS.

     

    But for detail sketching, marking up drawings, site measure, note taking and document signing – by far my favourite is Notability. Great on both iPad and Mac. Can also record meeting audio.

     

    See image below of a old detail sketch for a structural engineer.

     

    Balustrade Details.jpg

     

    • Like 1

 

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