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
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.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
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.
While I agree with this i also recall many updates in XM and V8 when it was flat broken and we skipped the update and had to wait. Fawning over v8i at the end of it's life cycle is a bit of a rose colored view given it was as polished as it was ever going to get. New features were not being added and it was effectively stagnant but super well polished. We all wish CE was as polished as v8i and its not even a debate that it was WAY to many updates before it was stable enough to be a functional product. Like U10+ but after around 13.1 it's been over-all as good as XM or V8 where at release before all the bug fixes. That said it's still not perfect and the launch was awful but it's not really fair to compare v8i-SS10 or SS3 to CE at this stage of it's life cycle. Had we gotten what was effectively U10 at launch i think the reaction to CE would be far less extreme.
Grant Wood said: but it's not really fair to compare v8i-SS10 or SS3 to CE at this stage of it's life cycle.
We're on Update 17-2, which means a whole lot more updates than just 17, and we still have multiple bugs which affect daily 2d sketch-work. Microstation should be better than this at the current stage in life.
v8i never had the number of issues that Connect brings us. Not even close.
Hi,
I haven't used Update 17-2 very much--been working on non-drafting projects for a little bit. But I now have a new crash that is a regression from Update 17-1. I'm still in the process of trying to figure out what causes this crash, but it is definitely repeating and is definitely new! That's what happens without proper testing!