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
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.
AMEN
Oto said: That is sad part to see that knowing how it worked flawlessly in v8i only after 4 updates not 17
IMHO you can not compare this you have to look at the V8i 8-digiit relaease numbers and count them!
But indeed
Oto said:Of course overall migration to 64bit is great achievement but we need for production not only for show-off.
The thing "CE" is now almost about ten years old :-)
Regards
Frank
since 1985: GIS, CAD, Engineering (Civil) Senior Consultant : [Autodesk Civil 3D , Esri ArcGIS, VertiGIS: in previous days : Bentley MS V4 - V8i, GeoGraphics, Bentley Map V8i, InRoads, HHK Geograf, IBr DAVID] : Dev: [C, C++, .NET, Java, SQL, FORTRAN, UML][direct quote by: http://en.wikipedia.org/wiki/Helmut_Schmidt]: "Wer Kritik übel nimmt, hat etwas zu verbergen"Wer Grammatik- und/oder Rechtschreibfehler findet, der darf sie behalten :-)
Frank Klein said:The thing "CE" is now almost about ten years old :-)
And it was based on SS3
Frank Klein said:IMHO you can not compare this you have to look at the V8i 8-digiit relaease numbers and count them!
True but at least it had some clear milestones. I do not get these now popular large release numbers when there then is again decimals like 17.1 and 17.2. Thought that the sole reason was to avoid such confusion.
What has been improved?
parametrics ..yeah so so
Very little improvement to anything. They seem more focused on new features as bleeds over to the iTwin platform. Connect is potentially a bit faster, but suffers from so many bugs it may take you longer to do certain tasks.
Hi Oto,
Oto said:And it was based on SS3
One of the problems is that CE is NOT based on SS3. They started too much coding from scratch when they switched to 64-bit architecture. In doing that, they abandoned the years of bug/issue fixing that led up to version 8 and to release SS3. Then on top of reprogramming a lot from scratch, they decided to throw in the ribbon interface, introducing a whole new set of problems. It was too much abandonment, too much change for changes sake (instead of for productivity) and not enough quality in testing the "old" tools.
Oto said:I do not get these now popular large release numbers
Don't worry now! Bentley announced that it's going to change their numbering system to be year based--so it looses even more information.
--Robert
RobertArnold said:to be year based
Oh like released Openroads 2021 in 2022 while most companies already release 2023 versions in 2022. That will make sense. Never before have seen such marketing to release expired year based versions, very innovative.Marketing lives in their own wonderland.
RobertArnold said:much coding from scratch when they switched to 64-bit architecture
I think that is the heart of the problem. That, and Bentley went public (Oct. 2020), seems they got rid of a lot of good people to show more short term profit.
Bottom line- v8i worked Good, Connect does not work very good.