Jump to content

Amorphous - Julian

Member
  • Posts

    409
  • Joined

  • Last visited

Posts posted by Amorphous - Julian

  1. To share an anecdote (one hour from my post above).

     

    A member of staff just reported she lost a whole day of work....

     

    She spent a whole day working on a 'working file' (the 'child' folder that lives on your terminal), and cannot sync what she has done for the past 9 hours*** back to the 'project file' (the 'parent' file on the server). Vectorworks just crashes every time we try a 'refresh' or 'save and commit' operation with her working file.

     

    ***Most of us in the office do not 'save and commit' as regularly as we should, preferring to 'save only' on our local working files until the end of day. We do this because of the excruciatingly slow sync process as described in the post above (see link in above post), and also, when you sync, others can't work on the model AT ALL, because permission requests cannot be sent to a file that is currently occupied with a 'sync operation'.

     

    I just hope this really important issue of project sharing gets more attention from Vectorworks. We feel like we are battling with the software everyday.

     

     

    • Like 3
  2. We have other issues with this tool as well. 

    (1)

    Some of our beams just sudden become 'transparent' out of nowhere. 

    In other words, the lose their solid information, and only their wireframes are left. 

    And in OpenGL or in section view, you don't see the beam.

    We tried everything- turning on all classes, checking the object has a fill, checking the class has a fill etc etc.

    In the end we had to re-build these beams with the Structural member tool (or better still, just extrude or use walls)

    (2)

    This second issue is a little ridiculous it is almost laughable. 

    Beams cannot connect with walls or slab with the same hatch.

    We have tried everything to make beams made with 'Structural Members' to merge with adjacent objects with the same hatch (eg wall, slab). 

    But we cannot get rid of the line between the beam and these adjacent objects. 

    We ended up re-making all of the structural beams, which we have diligently created with the Structural Member tool, as either walls or extruded objects.

    We find this laughable because this structural objects- purportedly there to make modelling structure easier- does exactly the opposite. And along the process wasted a lot of our time. 

  3. Hi Tom. 

     

    We use project sharing in all of our projects in the office, and we can report good success (except for slow syncing process- see end of post).

     

    Up to four or five of us will share the project at the same time. One of the current model we are currently working with is 1GB in size, and has 300 sheets of drawings. 

     

    Initially, we did experience the issues you speak of- not all information would be seen when saved and committed. We found that more of a problem when a file has a lot of 2D information, or if the 2D information is very far from the origin.

     

    Our BIM models with very little 2D information do not suffer from the same loss of information. 

     

    As our model grow it size, we do have issues with permissions (like you mentioned) and very long 'Save and Commit' times. You can see the issues we experience in the post below.

     

    We do hope to see a massive improvement in the speed at which we can collaborate in an office. 

     

    • Like 1
  4. ISSUES & SUGGESTIONS 

    (1)
    Currently, when creating a new viewport, you have to enter a 'drawing title' as well as a 'viewport name'

     

    This shouldn't be done twice over. 

     

    The 'Viewport Name' should simply be automatically populated by

    [sheet #/drawing #/drawing name] 

    And this ought to be Dynamically Updated.

     

    (2)

    Currently, to toggle 'visibilities', you enter a list of checkmarks against 'Viewport Names'.


    Because they are not automated, and are not dynamically updated against anything, we are basically presented with a list of useless garble. 

     

    Unless we get someone in the office to rename every single viewport in a drawing set, (now, no right minded person would do this) we can't make out what these ‘Viewport Names' refers to.

     

    Hence the importance of point (1).

     

    Our suggested method of organising Sheet #/Drawing #/Drawing Name (as seen the enclosed mockup) can make controlling visibilities so much easier. 

     

     

    Current Vectorworks Viewport Organisation.png

    Proposed Vectorworks Viewport Organisation.png

    • Like 3
    • Love 1
  5. 11 hours ago, zoomer said:

     

    Real Sections most time come with a speed penalty.

    So I would still vote for a faster simpler "fake" solution for a DL Modeling

    assistant like Clip Cube.

     

     

    @zoomer We agree. Really need urgent speeding up of section viewports. It is really dragging back our productivity. 

     

    (as we speak, on a Saturday morning here, one of our colleagues is complaining a simple viewport we are rendering has now taken close to 5 minutes)

     

    I created a post about the need to greatly improve sectioning speeds (among other things for productivity). 

     

    I know the request is not new, but to us is very important .

     

     

  6. Would be even nicer to be able to ‘right click’ on these voids, and see a contextual menu saying ‘resolve junction...’

    which then you can select:

    ’- trim to floor’

    ’- trim to slab’ .... etc

    And Vectorworks automatically does the geometrical resolution for you.

    (instead of having to switch back to plan view, double click into slab, and then modify vertex, which is a multi step manual process you have to do yourself)

  7. In the past, the 'stop process' keystrokes will end all processes immediately.

     

    IN VW 2018, following are the processes that we often need to abort, but cannot do so with the 'stop process' [ ⌘ + . ] shortcut keys (or 'ESC')

     

    - Hidden line processing in Design Layer View

    - Abort 'publishing' of a hidden line render in a sheet

    - Abort a 'Renderworks' process

    - Too many others.

     

    This is an important feature to bring back as the alternative (force quit and wait for VW to restart) hinders productivity. 

    • Like 1
  8. One of the annoyances we find with the Titleblock Border object is that, in a multi-user situation, only one person can work on ANY titleblock.

     

    It would be ideal if different 'parts' of the titleblock can be checked out by different people.

     

    For example:

     

    • I ask STAFF A to work on making sure 'Current Plot Date' - 'Auto - Short' is turned on for all sheets (more on this issue later**)
       
    • And, I ask STAFF B to apply the latest 'Revision number' to ONLY the sheets we are issuing (more on this later too##)

     

    Because Titleblock Border is one linked object across all sheets, I can't have STAFF A and STAFF B doing the above tasks simultaneously. 

     

    Would be nice if the Titleblock Border is somehow broken into parts so different people can do different things on different sheets at the same time.

     

    -----------------------------------------------------------------------------------

    ** Problem with Automatically applying Current Plot Dates to sheets upon placement.

     

    Even though showing 'Current Plot Date' is set to show as 'Auto-Short Form' in my 'Titleblock Style', upon placing the titleblock on our sheet, the 'Current Plot Date' doesn't show up, and we have click into the PIO dialogue and manually turn that on for each titleblock we place in. This is very time consuming. 

     

    -----------------------------------------------------------------------------------

    ## Problem with applying the SAME information to MULTIPLE, SPECIFIC sheets

     

    Currently, we can only apply desired information such as 'Revision' to only 'ALL' or 'ACTIVE' sheets. 

     

    I would be much better for us to be able to apply information to a list of drawings from a form that shows all drawing. 

     

    Finally, I really don't understand why navigation of the 'Title Block Manager' is sequential (via the 'next button), instead of with a drop-down list.

     

    And why does clicking on the 'Titleblock manager' take you back to the first sheet, and not the current sheet you are working on.

     

     

     

    @Markus Barrera-Kolb fantastic worksheet. We have spent hours trying to figure out how to pull out these kind of data from the Titleblock border but in the end settled with only showing the 'current plot date' and 'current revision'. 

     

     

  9. We do use separate classes for each finish (GL01, GL02 classes for different types of glass... TL01, TL02 classes for different types of tiles). 

    In fact, the above elevations were generated by the 'walls components' picking-up up on the different 'renderworks texture surface hatches' of the relevant 'class renderworks texture' (a long, round-about way of achieving 'wall surface hatch by class')

     

    Yes- we can use unstyled walls with two 'finishes components' on either side of the wall, but it doesn't resolve the issues of the 'start and stop' and having still to define two different 'finishes components' on either side of the 'core wall'. It becomes the same multiple small, short walls as described. 

  10. Hi Diogo, all those issues you have raised are valid but can be resolved by planning the model differently (as Christian as pointed out)

    1) If the first floor has a wall, and the second floor also have a wall, then just draw them as two different walls

    2) You can overcome this by doing an extra 2D layer with Dotted lines that you can turn on and off. But I agree that this is very frustrating!

    3) You can show the wall components in Section, but it takes a long while you get all the wall components set up correctly.

    And Christian, I agree with you on that may key elements is missing from Vectorworks. As an ARCHITECTURAL tool, some important tools that Diogo pointed out sorely missing.

    Furthermore, working on a model as a team presents a nightmare.

    ArchiCAD has many good points, but it has a bad interface for 2D drafting, and is more expensive.

    Revit does't run on macs.

    So Vectorworks, rather being the best choice, is the product that happens to fill in a particular void in the market. We'd love to see it being developed as a more meaningful collaborative tool.

  11. Hey guys... just wondering whether this post should get further updates... or just let it died? I think it is an important conversation.

    Blimey- has your office resolved the speed problems by switching back to design layer referencing?

    Jeffery- I second Blime's point about 'workflow'. If you have more than one person working on a project, the task of modelling has to be spread between different people in the team.

    In any case, modelling+drafting are intertwined processes. It is not like when you finish modelling, you start drafting. These two processes are very much interactive and iterative.

    All the other CAD packages on the market now have much better teamwork interfaces (look at ArchiCAD, Revit etc), they also have a teamwork structure that keeps the model in one file to maintain its BIM integrity.

    Vectorwork's ability to link one file to another a really antiquated way of teamwork. Is Nemetschek planning a better, and different way of teamwork for Vectorworks?

×
×
  • Create New...