Jump to content

Amorphous

Member
  • Content Count

    64
  • Joined

  • Last visited

Community Reputation

54 Excellent

1 Follower

About Amorphous

  • Rank
    Apprentice

Personal Information

  • Occupation
    Architect
  • Location
    Sydney

Recent Profile Visitors

314 profile views
  1. Fantastic! Thanks @Boh for the tip and the solution!
  2. An important feature we use a lot in our documentation process has been removed in VW2019. In VW 2018, when you place a Section Marker, you can choose where this is linked to. This is useful when you have multiple instance linking to the same detail. In VW2019, this can still happen before you place a Section Marker. But once place, it cannot be changed in 'Object Info' palette. See screen shots below. Can this be brought back to the 'Object Info Palette' VW2019 SP3 ??? The removal of selectable viewport affects our workflow severely.
  3. Amorphous

    exporting elevation sheets in a dwg

    Hi @Andrew Mac we always have to do the same thing too- to export elevations generated from our Vectorworks model to DWG. However, with VW2019, our consultants are simply unable to use the DWGs we export to them (file too large, unable to zoom in and out, crashes upon opening). Have you had any success on this? You may be interested in the following post too, where users are discussing this issue:
  4. Amorphous

    Best settings to export 3D (vwx) to 2D (dwg)

    Hi @drelARCH we also use Vectorworks in 3D and have problems getting our exported DWGs to our consultants. You may wan to share your experience in this post, which is relevant to the issue of exporting to DWG from vectorworks:
  5. Thanks for the suggestion @erminio @Art V, they are indeed good ‘workarounds’ for this severe Vectorworks shortcoming. I will try them out. But the important issue here is that exporting from Vectorworks to our consultants/ contractors in DWG format is a frequently-occurring process in our industry. To reiterate: it is something that EVERY architect needs to do regularly in their workflow. SO WHY IS THIS SIMPLE PROCESS MADE SO DIFFICULT IN VECTORWORKS? Vectorworks should- ‘out-of-the-box’ - be able to export to these industry-standard documents (ie DWG) without users wasting valuable time and multiple steps to find work-arounds. If we tally the wasted charge-out time we all put into to ‘trial and error’ to find a workaround, we’d probably be a lot more profitable. I have put a senior VW architect onto the case of finding a solution to this problem and he spent two days on various combinations of settings and methods. We have nothing replicable, easy and efficient. It is up to Vectorworks to give us a solution. @Jim Wilson to recap- we cannot export our 3D Vectorworks model to usable 2D DWG files (by usable, we mean DWG files of a reasonable size that doesn’t crash upon opening). In any given project, there are multiple sheets we need to export, so the best way to achieve them is with the ‘publish’ tool and select DWG. This is broken and needs urgent attention.
  6. What a great solution @Jim Smith and @Kevin McAllister. But then again, I agree with @Patrick Fritsch - tools released in a program needs to be considered, tested and works. Some VW tools do not reflect how users would use them in real life. We waste a lot of time as VW users finding 'workarounds' to the lack of consideration/limitations of VW tools. Enclosed is a screen shot of how we end up doing our 3D grids, by rotating them in 3D. But as with all the 'workaround' solutions presented, the limitation of this solution is that the 'section depth' of a viewport limits the display of this grid. If anyone in Vectorworks is listening, this 3D grid issue cannot linger for another few years to eventually get a solution.
  7. Thanks @erminio for raising this important issue and thanks @Art V for offering a possible solution. Fact is, this process should just be a simple, straightforward process and does not require VW users to come up with 'workarounds' to make it work. We use Vectorworks in 3D, and there is NO POSSIBLE WAY to get our models into a usable DWG file to our consultants, collaborators and consultants. We have spend many hours in our office trying to resolve this issue, and in the end the only possible way to create a usable, small-sized DWG file from our 3D model is to 'save as' a PDF, reimport the PDF to VW, and explode the PDF just to get the lines. Not ideal at all but no other options we have found so far.
  8. Over dinner with industry friends last night, I was reliably informed by a senior partner of an international firm that if our firms don't 'adopt the new ways of generating fast high-quality renders for our clients', we'd be left behind. The packages that are widely used now are ENScape, Twinmotion, Lumion and Vray. For a VW company like ours, who uses Vectorworks on Mac, these are the limitations: (1) ENScape >> Works with ArchiCAD, Revit and Sketchup, but NOT Vectorworks (2) Twinmotion >> Works with Vectorworks, but NO direct synchronisation like it does for Revit and ArchiCAD (3) Lumion >> Does not support Mac (4) Vray >> Works with Revit, ArchiCAD and Sketchup, but not work Vectorworks. (5) Vectorworks (Renderworks): Quality of render simply is nowhere like the packages above In conclusion, if I was to apply the conversation about being 'left behind by the industry' based on speed and quality of visualisations, Vectorworks (and to a lesser degree, Mac) is becoming a hinderance for us to compete against the companies that uses Revit, ArchiCAD or even the basic sketchup program. Our industry is quickly evolving, and as operators, we don't have time to wait for Vectorworks to take years to implement integrations (when others have working integrations already). Swift action is required from Vectorworks to help Vectorworks-based companies, and the Vectorworks package itself, to stay competitive. Following is a link from August last year, and I wonder if anyone can provide some update on conversations with Chaosgroup? Or if the engineering department has made progresses and inroads for integration with other rendering packages? When can VW get direct Synchronisation with TwinMotion? Would Vectorworks get integration with ENScape? How quickly can all this happen?
  9. As busy Architects/Designers, we spend a lot of non-billable hours doing the following for Vectorworks: - Identify Bugs - Making suggestions for features - Posting on this forum for above issue and respond to further requests for information - Creating 'example projects' for bug identification We don't ask for payment. We are simply doing this to improve the Vectorworks product. I think it would be nice if there was a bit more gratitude for our contribution, and have this gratitude shown when staff engages with us. And I'm putting this in the Wishlist as a feature request.
  10. Amorphous

    Project Sharing - Does this really work in the wild?

    @Tolu for completeness, this post wasn't only about Tom Klaber's use of Google Drive. For completeness, read every post. For completeness, everyone on this post already agreed and established Google Drive (Google Backup and Sync/Google File Stream) doesn't work for VW PS. The various posts here demonstrates that various people are having problems with project sharing, and these problems should not be overlooked. Also for completeness, I have spoken to other users on this forum, and the feedback is that you ( @Tolu ) tend to dismiss issues raised by users. As a final point on completeness. Have you worked a day in an Architectural Firm? How often to you actually use Project Sharing in real-life situations creating models and drawings that output to actual clients and construction sites? People with daily encounters and experience here are offering a complete view of this project sharing issue, and deserve to be listened to.
  11. I actually wonder whether VW should be updated every two years, and not annually. It seems crazy that we spend one year to reach SP4 or SP5 for each version, which admittedly is stable but still not ‘complete and perfect’. Then we abandon this ‘last stable’ version as quickly as we reach it, and jump into a world of chaos and insanity because of ‘new features’ in the next version. If SP4 and SP5 are genrally stable, then shouldn’t we extend its use for an extra year, and continue to improve productivity and fix all the remaining bugs well into, say, SP10? I image once we reach stability at SP4, we can focus on productivity improvements in the subsequent SPs. Productivity improvements currently seem lower on the VW list than new features. Perhaps productivity is not sexy for marketing purposes, but new features are? Of course VW needs annual income to balance its sheets, and this is how I think it can work. Currently: If current VSS is, say, US$1000 per licence (for designer series), then it is $2000 over two years. Alternatively: VSS is split into (a) SP releases for the next two years (US$1000 for two years’ worth of SP releases) (b) Upgrade to the next SP0 version (US$1000 paid every two years) VW will end up with the same subscription amount, but have more time for much better feature release and product improvements (broader in scope, better in quality) But that means if one buy the next SP0 version without the upgrade options, that person will end up with a buggy software. This bi-annual cycle would only be feasible if VW does indeed commit to releasing software every two years that looks and feel like there was two years worth of thinking and development in it- not just giving us the same thing we used to get on a yearly basis. Hard to quantify and qualify I know. Perhaps one way to quantify and qualify it is to say, every two year, 200 items in Wishlist feature request is granted (compared to say 20 in annual releases). May not work for everyone. But this would work for my office.
  12. @Tolu please also check out this troubleshoot post for other users with PS issues:
  13. Hi Tolu thanks for your reponse. I’ve sent you the file via a PM, but to summarise: Everytime we have a permission issue. We ‘save a new version’. I am up to ‘Version 175’ for one project and ‘Version 59’ for another. We don’t make a record of which version had which type of permission problem, so I can’t send you that PF and WF ‘in that state’ until it next happens. What I can tell you is that the most common permission issue is: - a user (‘User X’) checks out ‘an item’ in WF - VW crashes on the computer terminal of ‘User X’ - the ‘item’ checked out by ‘User X’ at the time of the crash presents permission issues - When anyone (including ‘User X’) tries to edit that said ‘item’ in the file, it says ‘User X’ has the item checked out and thus can’t be edited - we have to save a new version to get around this permission issue - In ArchiCAD, the BIM admin can ‘force’ a user out of the file to resolve permission issues. Would be great to have the same in VW.
  14. Amorphous

    Changing Titleblocks : ONE MINUTE per sheet

    Hi Nikolay. Thanks for looking into this. I was surprised that you couldn't replicate the problem so I wondered if it was a 2018 vs 2019 issue (we are still on 2018 due to our fear of bugs) I did a test on 2019 and indeed the problem was no-more. But I am presented with another problem- upon changing back to another titleblock VW crashes. NB I'm on 2019 SP0 because SP1 is not available for my region yet. Crash.mov
  15. Amorphous

    Changing Titleblocks : ONE MINUTE per sheet

    Sent 🙂 Many thanks

 

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.

×