We are attempting to switch over to CE.
I spent time customizing menus.
CE crashes on the simplest tasks.
After all of these years, I still feel like CE is a beta version.
Why on earth would I be inclined to make the switch
If you find that MicroStation CONNECT Edition is crashing with the use of your customized menus, then it must be something within these that is affecting the operation of the software. For this to be investigated you would need to provide details of what is being performed, what customizations you have introduced with example files, workspaces etc. Otherwise, it is difficult to identify what your issue is relating to.
It is also a good idea to identify whether the crash is occurring with the general operation of a clean installation, before using customizations. This also weeds out any issues with customizations you've performed.
You might like to also produce dump logs for the investigation.
Generate Type 7 Minidump files
Generate crash logs with ADPlus
I would suggest raising a new Service Request and providing further details, examples, crash logs etc so our support teams can investigate what your issue is regarding.
RegardsAndrew BellTechnical SupportBentley Systems
Just reported another random crash(silent exit) when working with Reality meshes which appeared in 17.1 and now in 17.2 version so stick to U17 if working with meshes.Defect Report 1072805
Here is the macro which was able to trigger the crash while Reality mesh is attached:
The stress test macro is just sending three key-in commands in a loop so it is as much close as to user input as possible. This causes memory leak and crash after a 5min.
Key-ins:rotate view relative 1,10;selview 1zoom in center;selview 1
zoom out center;selview 1
rotate-relative-loop.mvba
That's pitiful.
It's a good thing MicroStation doesn't often lose data when it crashes
Kirk
I Wish Cadland was Reality
Yes, been a long time since I actually lost anything with crash.
When I first migrated, I had to remove certain bits which were migrated over from v8i. Wish I could remember exactly what, but some configuration variables, paths, old softwares, things of that sort. Eventually I got it to be stable. Still after some 20 or so revisions, it's still buggy as a month old piece of fruit. Seems Bentley is not putting in much effort, rather using us as beta testers.
Do keep a copy of v8i around, I predict they'll need to continue v8i support of some kind for a very long time.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Yes luckily didn't lose any data but at least 2-3 crashes in a day is norm if working with same file all day. Bad that most crashes are more or less random and on some machines it is more stable so very hard to prove to Bentley and minimum effort is applied to troubleshoot that. V8i SS10 also is not stable as it was in v8i SS4 which is weird as only licensing was changed.
Same story for LumenRT nothing has improved comparing it 4 years ago it also crashing so fits really well in the MS line. Descartes crashing on 3sm generation for years and so on. Don't get me wrong Microstation is great product but it should be production ready before pushing to market like sliced bread. That is sad part to see that knowing how it worked flawlessly in v8i only after 4 updates not 17. Of course overall migration to 64bit is great achievement but we need for production not only for show-off.