AC 29.1.0 (4006): More Teamwork Warnings

[Patrick M]

 Starting a new thread. Upgraded to 29.1. This user has only been working on doors and windows today. Had not edited layers or other view settings. Has not edited attributes. Total file size on the BIMcloud is just over 1GB.
the project does have a problematic library; they added libpacks AND lcf, so there are quite a few unplaced duplicates. I will be cleaning that up, but they are SOL unable to s/r...
Regardless; this hopefully reinforces that we STILL need Graphisoft to get bimcloud/teamwork/archicad in better working order. If bad library practices is all it takes to lose 4 hours of work, then archicad doesn't work. We need a better and more reliable tool.
I hear revit sucks too... can you imagine the market edge graphisoft would have if archicad didn't suck?!

[MSDC]

Hi Patrick, did you reshare the project after the latest update?

We're hoping this will fix the teamwork issue too as we're getting it with all our 29 files - a bit concerning the update doesn't seem to have worked

Also is this a migrated file from an older version or was the file started in 29?

[Laszlo Nagy]

@Patrick M,

Can you also report back whether fixing the duplicate issues in the project file helps with the issue or the issue still exists even after all library error messages are handled?

[Patrick M]

Laszlo, this particular designer left the file open overnight and was able to send/receive successfully the following morning. After talking with GSNA, we are thinking this may have been a legitimate communication issue; due to slow internet or latency, possibly caused by a vpn bottleneck... While I'd like to think archicad could send and receive even with <20/20 internet speeds, I do have to acknowledge our file sizes are a bit insane; so I can't expect everything.

...
the libraries are cleaned now, but do not think that was a factor, as I didn't get to that until after she had sent the next morning.

[Patrick M]

@MSDC , I did not reshare the file from a saved pln; I have the crazy notion that a software fix should fix the files in that software... maybe I expect too much.

in any case, last week was a breath of fresh air; after 90% of the office updated to 29.1, this is the only warning that came across my desk. The 2-3 teams that didn't upgrade sent me their warnings, but I filed those under "we'll wait and see"...
hoping this week is as good as last week, and that we continue to see fewer and fewer teamwork issues and lost work headaches!

[Patrick M]

looks like maybe I forgot to knock on wood?

   

[Laszlo Nagy]

@Patrick M, 

As discussed previously in the other long Teamwork-related thread and asked by @Gordana Radonic, please keep one error message type per thread, so it can be discussed and possibly resolved. Therefore, I have removed your other two screenshots.

Please start separate threads for both, if you wish to discuss them or ask for help about them. This way, we can hopefully handle individual issues more effectively.

[Patrick M]

we're gonna have 30 threads

[Laszlo Nagy]

Each error message should have its own thread. Even the title of the thread can contain the error message for better disctinction. Then, people encountering that specific error message can have a discussion about handling/fixes. That will be more productive than having a single thread with many different error messages.