Ongoing Project Sharing Issues: A record from one issue to another.

[Amorphous - Julian]

We have getting a chronic project sharing problem . Model objects, viewports and sheets regularly disappear from our shared project file. 

 

No matter the size and complexity of the file, we get this problem.

 

This happens between 1-2 times a week across different projects. 

 

Anyone else getting this issue? Is this something Vectorworks can fix in upcoming releases?

 

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

 

Some background:

- Our shared server runs Mac OS Server 5.2 on Mac OS 10.11.6 El Capitan, with 'SMB Sharing only' turned on in File Sharing.  

- We tried upgrading our server to Mac OS 10.13 and Mac OS 10.14, but permission issues were even more severe (in both SMB and AFP).
- We then downgraded back to Mac OS 10.11

- Previously, when we ran File Sharing on AFP in Mac OS 10.11, this 'disappearing model' issue didn't seem to occur. 

- Due to other services we have to run, we had to switch File Sharing over to SMB from AFP

- Sharing files in Mac OS with both 'AFP and SMB' turned on doesn't work, and not recommended by our Vectorworks distributor.

 

 

Edited October 29, 2019 by Amorphous - Julian
Changed the title to reflect the evolving project sharing issues.

[Amorphous - Julian]

12 minutes ago, Tolu said:

This looks like classes are turned off in that specific Working File.

 

This is taken from a VIEWPORT. 

 

All my walls that are masonry are on THE SAME CLASS.

 

No, the classes were not turned off. Here's another screenshot viewport of another viewport I didn't post up. 

 

 

Sure, I didn't know about the 'filters'. But me and my team know something as simple and checking if our classes are turned on before we spend time making a post.

[Guest Tolu]

You said the Walls are missing in the Viewports. Are the Walls also missing in the model space? 

[Amorphous - Julian]

Another viewport with another wall just disappeared (let me be clear, it is a viewport. We don't change our classes here)

As you can see, we tagged a wall here previously. The wall has now disappeared.

We are now copying the walls back from a previous version. We are not imagining this. 

10:44pm now here and I was intending to issue this drawing set. But we will no longer meet this deadline. 

 

[Amorphous - Julian]

52 minutes ago, Tolu said:

You said the Walls are missing in the Viewports. Are the Walls also missing in the model space? 

 

Yes, missing in the Viewports and also Model space. Otherwise we won't be doing 'copy-and-paste' from a previous version back into here 😆

 

This is another wall that went missing. Our team member tagged this door (door 20, type G) just a couple of hours ago tonight. After a few rounds of S&C the wall is gone. 

He's given up and will continue tomorrow. 

[Amorphous - Julian]

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

[Amorphous - Julian]

[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!!!!

[Amorphous - Julian]

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

Edited March 13, 2020 by Amorphous - Julian

[Amorphous - Julian]

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

 

 

 

[Amorphous - Julian]

[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!!!!

[Amorphous - Julian]

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

[Amorphous - Julian]

[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?

 

 

[Amorphous - Julian]

After what my team has been through today. I may just answer my own questions. 

 

On 3/12/2020 at 5:23 PM, Amorphous - Julian said:

Lately, with all the issues we go through, I can't stop asking myself....

(1) If I didn't run this practice, and haven't already invested/committed so much time and resources into Vectorworks, would I work in an office that uses Vectorworks?

 

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. 

 

On 3/12/2020 at 5:23 PM, Amorphous - Julian said:

(2) Weighing everything up, does Vectorworks aid, or hinder, my work?

 

For my team's work today, it has without-doubt been more hinderance than aid. 

 

On 3/12/2020 at 5:23 PM, Amorphous - Julian said:

(3) Is it unrealistic to expect Vectorworks to become a snappy, responsive, efficient & stable program? When may that happen?

 

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.

[Amorphous - Julian]

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. 

[Amorphous - Julian]

[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!!!

 

[Amorphous - Julian]

[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!
 

 

[Amorphous - Julian]

[UPDATE 3 - 19/03/2020]

 

Second 'This File is Corrupt' in ONE day. Absolute insanity. 

 

Hope Vectorworks can show some empathy and fix this issue ASAP.

Just to recoup this is the IDENTICAL issue I reported on 19th August 2019. 

It would be, to understate it, be extremely disappointing if on 19th August, 2020, I'd still be updating this post talking about the same issue. 

 

Changing the way Project Sharing works is the way forward. 
  

[Amorphous - Julian]

[UPDATE 4 - 18/03/2020]

 

Saved a new version (we're now up to version v343)...

 

.... and now this error message.... 

 

 

Did I mention our office spend half our workdays wrangling with VW project sharing? .... or maybe it's blatantly obvious....

 

[Amorphous - Julian]

I've just had a chance to calm down...

So I do apologise for my tone, especially to @Tolu

None of this was meant to take aim at any one persons. I was merely venting frustrations, as I am not meeting project deadlines. 

I hope everyone at Vectorworks can understand where my frustrations stem from.

My team and I spend no less than 8 hours each day with Vectorworks, and being frustrated by flaws that materially affects our work -especially over such a long period of time- is somewhat inevitable. 

[Silje Jessica]

Hello, I am Silje from Julian's team.

 

Just wanted to share an example of what is happening... because it happened to me this morning. 

 

Yesterday I had a detail that looks like this. 

 

 

 

This morning, I come in, open up my computer, and it looks like this... Annotations, hatches, drawing title all gone from the viewport. Which means an extra 20/30 minutes of redrawing and longer if I need to comb through the file just to check that all my viewport annotations I worked on yesterday are still there. 

 

[elepp]

I am really amazed by your patience and consistency in posting here. My office gave project sharing a couple of tries but after a few issues, that are not even close to yours, abandoned it mostly. We use it from time to time as means of providing a source file for our ressources, that is than referenced into our drawings.

When they talk about the other BIM software from Nemetschek and its collaboration capabilties they get dreamy eyed.

 

So I am also waiting for an improvement and better consistency, because I believe that it's going to be more and more essential in a BIM-focused World to have this possibility.

 

All the best!

[cberg]

Amorphous - Julian, 

 

I appreciate your thorough documentation of the issues you have experienced with project sharing. 

 

While we have experienced many (if not all) of the problems you describe, we have been able to work for long periods of time in project sharing mode without the severity of problems you describe. A couple of questions. 

 

How many people are typically sharing a project? We try to limit shared projects to two or three users max. Whenever possible we convert shared projects back to regular vw files. Especially when a project file starts to misbehave. 

 

Do you encourage staff to check out layers before any making changes in the model? Checking out layers seems to make the process run smoother. I have started to never make changes to a model without first checking out the sheet or layer in which I am working. If a dialogue box asks me to check out an object, I say no until I check out the layer. Minimizing the communication back to the project file seems to result in fewer problems. 

 

Do you save working files before committing to the model?  We do this to make sure that whatever we have worked on is saved at least locally.

 

Do you coordinate saves and commits with all users? We use instant messaging as a means of communicating when changes to the project file happen.

 

Recently I've begun deselecting dialogue boxes to reset worksheets and plug in objects while printing, especially for check sets/test prints. Final prints should be made by one individual with all design and sheet layers checked out. 

 

None of this negates the need for improvements to this tool that you argue for. 

 

Cb

 

 

 

 

 

 

 

 

 

 

[JMR]

5 hours ago, cberg said:

Do you encourage staff to check out layers before any making changes in the model? Checking out layers seems to make the process run smoother. I have started to never make changes to a model without first checking out the sheet or layer in which I am working. If a dialogue box asks me to check out an object, I say no until I check out the layer. Minimizing the communication back to the project file seems to result in fewer problems. 

 

 

This is interesting - for us, the process goes much smoother and more reliably if we don't check out complete DL's. Somehow checking out DL's was too much for the system to handle. Changing to checking out individual objects on the fly removed most of the speed and reliability issues. This was with 2018 and 2019, don't know about 2020 yet. The project was a 2000sqm 4-storey residential project. Title blocks never learned to behave, though, and there were intermittent issues with shifting and disappearing walls, and opening wall joins. Since then we haven't used PS much, I've waited for it to mature to a professional reliability level.

 

It seems PS behavior can vary greatly from office to office and from project to project, which implies the technological setup is not as robust as it should be.

 

A disappearing sheet layer annotation set is a horrible bug - as Julian mentioned, everything we send out from our offices creates a legal responsibility to us, regarding the content of the documents. The documents are contract documents before the building starts, and afterwards they are construction documents that must be 100% correct. All damages resulting from drawing errors, missing information or misleading information can, in principle, be charged from us, at least from the commission. Usually the financial responsibility is not limited to commission alone, but at least some damages to 3rd parties are included.

 

 

Edited March 19, 2020 by JMR

[Amorphous - Julian]

Hey just letting you guys know, @Tolu have been working with me in the background on this issue, they are aware of it and now working on solutions

[cberg]

Do you have a sense as to what is causing the problem?