I noticed in Connect (I've got U2 but noticed it in previous versions too).
When opening a file (mostly the 'harder' to generate ones, with a DV attached), Connect gives me an error and makes me exit. Once this happens to a file, it just keeps happening when you retry to open it. It's like it's corrupt and won't open again. However, when you just open it in the older V8i version and save it, you can open it without a problem in Connect Edition again.
Anyone else noticed this?
Hi Stefan,
Can you please share a sample file with us?
Warm Regards,
Subhamoy Kundu
HI,
I don't have one file or project in particular, but I noticed this happened quite often when using U2. When using U3 it seems to appear rarely, but it can happen. I was wondering if anyone else noticed this too.
In the previous version (V8i), when it failed to load a file and AECOsim stopped working, it just opened in a new session without a problem. With Connect, it often won't open anymore and only opens again when we open it in V8i first.
It happens with files in which you have a DV reference, so this makes it difficult to send you just 1 file when an error accurs. When I would have an easy file with not that much nesting, I can send it when the error would accur again.
Windows 10 pro
OpenBuildings Designer Connect Edition 2023 | 23.00.00.114
For us this was cells that were corrupted.
Ustn since 1988SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64bEric D. MilbergerArchitect + Master Planner + BIMSenior Master Planner NASA - Marshall Space Flight CenterThe Milberger Architectural Group, llc
So maybe compress the file and removing unused cells could help?
These are huge models and to complicated. I spend hours removing and reading cells to find the culprit. On one job you could not determine the bad cells and sometimes they worked and sometimes they didnt' It took support and I 6 months to find the culprit as I cannot afford time to hunt this stuff down all the time.