Jump to content

Amorphous - Julian

Member
  • Posts

    420
  • Joined

  • Last visited

Everything posted by Amorphous - Julian

  1. Teamwork was file-based collaboration. BIMserver and BIMcloud are server-managed. Being able to do simultaneous syncing (saves time) and cut out data losses (saves even more time) is very important to us right now. As it is, Project Sharing is slow, and is prone to data loss (we lose data through Project Sharing on a weekly basis). As for 'bad assumptions', I do feel that when using Vectorworks as a 'Documentation Tool' (ie using it to create contract drawings), it feels like the people creating Vectorworks don't have much idea of how this process works, or have themselves been documenters. These are some of our major gripes with documenting in Vectorworks: - Elevation and Section viewports are SLOW (hinders documentation efficiency) - Basic documentation tools like titleblock is SLOW (hinders document issuing time) - Advanced Text Editing functionalities is LACKING (we would like to do all specifications in Vectorworks) - Ability to add images to 'record formats' is LACKING (we would like to do all schedules in Vectorworks) - Understanding of how a drawing should look is LACKING (take for example any 3D objects, and how it appears as wireframe in Top/Plan view) - Understanding of construction concepts is LACKING (take for example wall, skirting boards, and floor styles) We throw resource (people) at documentation phase to mitigate the above problems. And therefore Project Sharing is important to us. So, back to the issue of Project Sharing: With Project Sharing performing so poorly, it compounds the inefficiencies of Vectorworks as a documentation tool. We, too, don't need online collaboration, we just need Vectorworks Project Sharing to not cause us constant data loss. Hence, we ask for a more efficient and stable way to conduct Project Sharing, something like BIMserver.
  2. With @Boh's worksheet above (thanks boh!) we were able to turn off 'This Titleblock is Active' very quickly But @Nikolay Zhelyazkov we are still not getting speed improvements. If Vectorworks is only designed for projects with 50 or less pages of drawings , then please let me know because this would definitely NOT be the software my company should grow with. If Vectorworks is intended for any scale of projects, with the ability to handle hundreds of pages of drawing, then @Nikolay Zhelyazkov please improve your Titleblock PIO so it can handle that amount of Titleblock data efficiently. This needs to happen quite soon for us (we have lots of drawings) So, unfortunately I need a better answer than this. Thanks.
  3. [Update 2 19/03/2020] So, we needed to find out what the above 'corruption' means for us. And it has left me very upset. 🤬🤬🤬🤬This is a ridiculous, bad practical joke. It is wasting our Professional time!!! 🤬🤬🤬🤬 PROJECT SHARING DATA LOSS IS A SEVERE ISSUE!!!! KINDLY SOME FROM VECTORWORKS ACKNOWLEDGE THIS This is what happened after the latest 'This File is Corrupt' (as above post) and after all users 'S&C': (1) All Titleblocks from the file has disappeared from Computer Terminal 2 (CT2) and Computer Terminal 3 (CT3) (2) Computer Terminal 1 (CT1) doesn't get the changes to viewports committed by CT2 and CT3 (3) New viewports created by CT2 and CT3 do not show up on CT1 (4) Annotations in certain viewports (annotations created well before today) disappeared from the viewports when viewed on CT1 (5) Annotations that has disappeared when viewed on CT1 is still present on CT2, but not on CT3 (6) Annotations that has disappeared when viewed on CT2 is still present on CT1, but not on CT3 ... etc IN OTHER WORDS, PROJECT SHARING DATA LOSS IS A DAMED MESS! This is what we have to do to untangle this mess (and not the first time we've gone through this process): (A) Conduct data loss forensics (as above) to see who has lost what (B) Create a 'new version' based on the file with least data loss, or with data loss that can be more easily replaced by 'copy and paste' operation, with data from older file. (C) In this case, the file with the most intact titleblock is the one we choose to base the new version on, as it is an almost impossible task to copy over 300 sheets worth of titleblocks from one file to another for the working files that have lost their titleblocks. (D) We had to re-create a lot of the viewports that was done this morning. As these new viewports did not show up on the CT1 version, which the new version was based on. (E) We have to copy-and-paste viewport information that has been lost from older files. (F) Right now, we do not have the time to check through every sheet and every viewport to see what was lost, so, we may end up with some data losses in viewport that later causes us legal issues. (remember, drawings are legal documentation, if we issue drawings that has omissions, we are legally responsible- and guess who caused that?) @Julian Carr @Biplab @Tolu This is beyond ridiculous. I am an architect, NOT a data forensic person. I shouldn't have to do this on a weekly basis. This is happening way too often! File-based project sharing doesn't work. Other softwares have gone down this path and proven it. When will this change? I am left asking myself: - What is the economic loss from all my issues since September 2019 (and earlier) caused by Project Sharing issue? I can tell you based on our charge-out rates it is pretty hefty - How would it feel when I receive my 2021 VSS subscription invoice, given everything I have gone through and documented here.
  4. [Update 18/03/2020] And yet again today. RIDICULOUS! Seriously. Project Sharing is broken. It is not working. THIS FOLLOWING ISSUE REALLY NEEDS TO BE LOOKED AT! DO NOT LEAVE IT AND HOPE IT WILL GO AWAY!
  5. We import most of our non-BIM publicly available 3D objects from sketchup warehouse. You can have a look there
  6. [Update 17/03/2020] And again today.... For heaven's sake! Why am I wasting my time to fix damaged files and checking for data loss constantly!!!
  7. We have 37 space objects in one of the files we are working on. We use spaces to report location of items (eg, furniture, fittings, etc) When modelling, we tend to switch spaces items off as they get in the way. If we change the dimensions of the room, we have to manually adjust the boundaries of the spaces. Adjusting the boundaries can be very time consuming, for us, there is a lag of 2+ seconds each time we drag a vertex.
  8. @klvanov @Luka Stefanovic thanks for the update. However, for our situation, there is a bug for Project Sharing 'Save and Commit' that is only fixed in VW2019_SP6. This bug is still present in VW2020_SP2. So, choosing between 'S&C' bug, or 'Data Tag' bug, I have to make the unfortunate choice of avoiding the 'S&C' bug until VW2020_SP3. A confirmed date for the Australian version of VW2020_SP3 would therefore be much appreciated
  9. Hi @Luka Stefanovic hope you had a good weekend. I'd like to check back to see if the engineers had given you a timeframe of when it will be fixed. Disappearing Data tags is driving us crazy. We shouldn't have to go back to re-do work we have already done (and do it over and over and over again)
  10. Agree @Taproot not only does the Vectorworks 'classes' system break down- when there are too many classes, it breaks the computer too. This weekend I was trying to use 'purge' to get rid of unwanted class from importing consultant's drawings (there are about 600 classes). After 12 hours of churning, this action finally broke my computer- the RAM required Vectorworks blew out to over 140GB!
  11. Yup- hopefully we will get a fix! Btw, editing geometry in the reference frame is a real pain too! You have to press ‘next vertex’ at every point, select the ‘type of curve’ and type in the radius. Since this tool is not snappy / responsive (few seconds wait after each click), retrospectively giving rounded corners to a rectangular callout frame can take 5 minutes. Argh!!
  12. Way back in 1997, ArchiCAD introduced Teamwork, a file-based project sharing method, like how we have it in Vectorworks today. In 2009, ArchiCAD ditched Teamwork and introduced BIMserver, a server-side project sharing management tool, allowing fast and simultaneous syncing. In 2014, ArchiCAD introduced BIMcloud, which allows remote collaboration. In 2019, ArchiCAD retired BIMserver, supporting only BIMcloud. In contrast for us, it is year 2020, Vectorworks still ’project shares’ with the technology of Teamwork, Archicad ditched this method 11 years ago because of its problems. Problems with file-based Project Sharing: Entire file needs to be synced (takes a long time, processing); Other team members are locked out during the sync process (waste of staff time); Constant file corruption and information loss (waste of time and soul destroying). This has been my experience, and I also verified this with someone who professionally maintains ArchiCAD systems for architects and saw through its ‘file-based project sharing’ era. As both ArchiCAD and Vectorworks are Nemetschek brands, surely Vectorworks engineers can learn from the experiences of ArchiCAD engineers and implement BIMserver into Vectoworks quickly? @Tolu @Julian Carr @JuanP @Biplab please close this 23-year technology gap with ArchiCAD on Project Sharing. We need to end project delivery disruptions due to the current method of Project Sharing. Below is a video on ArchiCAD BIMserver and BIMcloud. Note time code 5:45 in the video: ‘BIMserver’s mulitherading architecture allows any number of clients to simultaneous sync....’ That’s really music my ears. With this feature, it would make Vectorworks scaleable for any offices and project size. Following is my post documenting our office’s struggles with Vectorworks file-based Project sharing that began 6 months ago. The disruption caused by Project Sharing to our office has became unacceptable, and must change fast. Thank you for your attention to this.
  13. 11:00pm. We are trying to untangle the myriad of working files after the crash. Some bits appear on one file and not another... other pieces appear on another one. Some have titleblocks, some don't, some have tiled floors, others don't. This is making our work impossible. I'm exhausted and just want to publish drawings and go to rest. If we never went with the route of project sharing we'd never be mired in this mess. Please either swiftly fix PS once and for all, or release it when it's truly ready and reliable.
  14. After what my team has been through today. I may just answer my own questions. I have worked in an ArchiCAD office before, and at no time have I ever experienced chronic, ongoing project sharing issues like this. For the purpose of project sharing, I would prefer to work in an ArchiCAD office if the choice was my own. For my team's work today, it has without-doubt been more hinderance than aid. I just wish for Vectorworks to throw all resources it has at its disposal to make it robust, efficient and stable. It can't happen quickly enough.
  15. [Update 6 - 13/03/2020] Just as we are going to 'publish what we have', we find that in sheets after sheet our data tags are disassociated (we are publishing 30 sheets today). I have just been told by another VW employee that if I don't check out both the tag, and the object it tags, then the disassociation is certain. We were given a workaround that is simply infeasible. So are we meant to re-do the work we have done over and and over and over again everytime we save and commit?
  16. [Update 5 - 13/03/2020] I forced my Vectorworks to quit, it didn't 'lock up' the project file like it often does when you force quit in the middle of a save and commit. The other team members are able to commit their changes to the project file, but my working file now wouldn't open. My last save and commit was at 4:30pm, 3.5 hours ago. So I am losing 3.5 hours of work. Not happy.
  17. Hi @Luka Stefanovic thanks for passing this on. I'm on version 2019 SP6, Australian Version.
  18. [Update 4 13/03/2020] Just to top off a terrible Vectorworks Project Sharing workday, my S&C is stuck on 'Updating Story Bounded Objects' It has been stuck here for 10 minutes now. No one else can work on ANYTHING in the meantime. I have a few options: - Force Quit now- and everyone loses ONE HOUR of work - If we Force Quit, the Project File remains in the LOCKED state, and no one else can connect back into it. - Wait for this to be over- and don't know when this will end FRIGGIN LOSING HOURS OF WORK AGAIN...ARRGGGGHHHHH!!!!
  19. @Luka Stefanovic this is a ridiculous. Sorry.... but this is unacceptable. Version 2019 is now at SP6, version 2020 is now at SP2. How can such a fundamental problem not be fixed by now? Do you know what it's like to look at the work you and your team do disappear in front of your eyes? Do you have a sense of the economic costs of this? This is real, we pay wages. Lots of wages. We can't waste our resources like that. As for the workaround, when we tag an entire floor of walls, doors, windows, and we have a few people working as a team, it is simply not feasible to use that workaround suggested. When would the fix be available?
  20. [Update 3 13/03/2020] More wall disappearances. These are viewports, so there are not confusion about 'turning on classes' The existing wall (indicated in RED) and the new wall (indicated in GREEN) just disappeared from viewport and model.
  21. @Luka Stefanovic this is the part I'm confused about. What does 'definition of a symbol' refer to? Also, after save and commit, we lose all data in all tags. This is incredibly frustrating for a Friday. I have posted the above S&C causing data tags to reset values in the post below. Really need this to be fixed (it's not the first time I have posted about this data tag loss issue).
  22. WE HAVE REPEATED THE ABOVE STEP FOUR TIMES BETWEEN YESTERDAY AND TODAY BECAUSE OF THE S&C DISAPPEARANCE! FOR FRIGGS SAKE! WHY CAN'T THIS WORK LIKE A NORMAL PROGRAM SO OUR DRAWING ISSUES NOT DELAYED? Very very very very annoyed. It is Friday night and my team just wants to leave!!!
  23. [UPDATE 13/03/2020] !!!!!!!! WHAT A FRIGGIN WASTE OF TIME THIS IS !!!!!!!!! After a S&C, all tags in a viewport just went. Just disappeared. HOURS AND HOURS OF FRIGGIN WORK!!!! I've really had it. SOMEONE NEED TO FRIGGIN FIX THIS. I can't have Vectoworks waste my project time like this!!!!
  24. I made the following post, and just realised this issue has been raised before by @clint29 and @Kevin McAllister. If these issue still concerns you gentlemen, please do vote it up.
  25. [UPDATE 13/03/2020] The following issue has been bugging our file for over a year now. None' class will erratically - after save & commit- turn its default line colour to green. It is always this same green. We can go months without this issue, but it suddenly came back again recently. It is quite difficult in PS situation to change the settings of a class like 'none'. Because it is commonly used by many others on the file and causes a permission issue. So this becomes one of those 'weekend file admin' things I come back to the office to do.
×
×
  • Create New...