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
we have sometimes trouble with AECOsim CONNECT U2 and U3 in large 3D Model after setting a Clip Volume and using DisplayStyle illustration for the Clip settings. Sometimes AECOsim U2/U3 stops working. And you can't reopen the file with U2/U3.
To open the file with AECOsim V8i or with MicroStation CE is no problem. After deleting the Clip Volume with V8i you can reopen the file with AECOsim CE U2 or U3.
SR 7000785278 is filed and is under investigation from Bentley Support.
Regards,
Christian
Hi Christian
Seems like this could be simular to what we experience.
I hope this is something they can track down, I would like th uninstall the old V8i and keep just working on the Connect.
It could have something to do with the project being transformed from V8i to CE, since after using the files a while in CE, this problem hasn't occured anymore.