make teamwork warnings stop

[Patrick M]

these warnings are still happening prolifically. weekly for some people. 
This particular instance, the users bimcloud activity shows that they are receiving & reserving, but no send has been reported. This means they have to save a pln, discard their local data, and redo half a days work or tediously copy it in from a saved pln.
Honestly, if graphisoft did nothing more than make bimcloud stable, reliable, and consistent; I'd be happy with any features or lack of in future releases. I can't tell you how demoralizing and stressful it is to talk designers down off the ledge after they lose 4-8 hours of work due to teamwork malfunction.
and NO, I will no longer be accepting the "what did they do wrong?" or "it has to be something in the file" excuses. BIMCLOUD simply does not work reliably. If there are supposed to be parameters for files to work on BIMcloud, then those need to be outlined in black and white. The "do not cross" thresholds, if it REALLY is a problem with files or user error, need to be laid bare for everyone to understand those limitations. 
If it really is libraries, and attributes, and polygon count, and session reports, and library loading reports, and file size, and... that is causing this, then archicad simply does not work. Architects and designers do not have the band width to manage files to a pristine level where teamwork errors may pop up on a hair trigger. 
Make BIMcloud work. Make Archicad work. Its getting harder and harder, borderline impossible, to argue in favor of graphisoft, when warnings like this are a daily reality for firms pushing the limits of design.

[2D]

Halleluja!

[Patrick M]

current conversations/recommendations to the half dozen queries I get about this exact warning per week:
-save a .pln back up

-try to force quit and recover (recovery file has reconnected once or twice, worth a try)

-try to continue to send/receive until you give up or it crashes on you (repeated s/r has reconnected once or twice, worth a try)

-wait it out and hope for the best... (file has reconnected on its own once, worth a try)

...

when you realize that 6 people WAITING for archicad to reconnect only to lose their work anyway is costing the firm potentially 48 billable hours per week, you jump to the only reliable solution:

1. review team members connected to the file (if no one else is in the file, skip to the last step)

2. have everyone send changes and fully leave the teamwork file

3. have the affected user receive only (this is usually possible, if not they will lose their work, and have to copy some/most/any of it from the pln)

4. the affected user can then save a .pln of his file that includes his work and the other team members.

5. upload that pln as a new teamwork project.

...

This has to be taken seriously. We can't genuinely be expected to dump 6 figures a year on software licenses for a tool that has us slamming our heads against the wall, making assessments for retooling and training for a switch to Revit, evaluating our billable time loss due to software malfunctions on a weekly basis... It is absurd.

I know I'm not the only one getting these warnings. Across multiple firms, I get this exact warning several times a week. Walker Warner alone sent these three screen shots in the last 2 days. And one of them put the project on hold between 2:00 yesterday and 10:00 this morning until I could get looped in to help them salvage the project with the least amount of loss. Thats 3 people not working on a project for 5 business hours... 

I used to be frustrated/angry by the volume of teamwork malfunction and errors I see daily. At this point, it's more a sense of Fremdschämen...

  

[Brandon-W_DWa]

I am sorry this is happening to you. We feel these issues too, for what that is worth. Just today some users are having issues with a Teamwork project that is only 220mb. S/R either crashes AC entirely, or throws a series of error messages that a support package needs to be created. We've also just discovered that some S/R functions weren't actually working, i.e. after a troubleshooting attempt via force leave, a user discovered their changes weren't actually being sent to the BIMcloud. So there goes 3 hours of changes. We've had the same discussions about switching to Revit, too. *Edited for grammar.

[Patrick M]

@Brandon-W_DWa , if you are on AC29, make sure you are updated to the latest build. There is a bug in AC29 that had s/r appear to go through, even shows in the activity on the bimcloud manager. but when people close and rejoin the next day,  it's a crap shoot as to wether their work ACTUALLY saved. And even worse than that, we saw some people s/r, only to have their local data instantly be overwritten by old/outdated server data, esentially reverting back to the status of the file since their last actually successful s/r.
since the most recent update, in which graphisoft pinpointed a layer bug triggering this, I have not heard of this happening.

[Patrick M]

the hits keep coming! 

[Brandon-W_DWa]

@Patrick M - We are actually in AC28, so it seems to be unrelated to a known bug in AC29?

[Patrick M]

and another one...