Hi,
after long time, based on a discussion with another user, I tried to use point clouds in MicroStation CE Update 16.1. And it is disaster, especially in a context that one from "the release theme" is performance optimization.
When even simple POD file with just a few millions of points is attached, MicroStation response randomly (especially when element selection is used or a view should be rotated) drops down, for a few seconds MicroStation does nothing, GUI is redrawn and blinking. So, U16.1 is not usable for any project, where point clouds are used.
I have no original Update 16 installed, but when I tried Update 14 on my notebook (which is 10x slower, because only old mobile Nvidia card is used), it's not perfect, but acceptable, and without halted MicroStation moments.
I tried to search for similar issue, and I found only this discussion, and I also received information that (probably) bug #672552 is logged for this issue.
Can somebody from Bentley confirms it is known problem and for what release the fix is scheduled? It's important to warn users, using point clouds, to do not update from U14 or U15.
With regards,
Jan
Hi Jan,
As you already know, we have filed Bug 672552-> Handling of Point Clouds in Update 16 slow performances, unresponsive.
When wanting to rotate a view, it takes up to 2 minutes of processing to be able to use the function, MicroStation becomes unresponsive for a while. This also applies to all View related functions besides zoom when working with Point Clouds.
This Bug is not fixed yet and in theory it has been scheduled for MicroStation Update 2023. MicroStation Update 2023 will not be released in 2023 but in 2022.
Bug 672552 is scheduled to be resolved in Q2 2022
Issue is not reproducible in MicroStation CONNECT Update 15 or SS10.
Regards
Maria
Maria Garcia
Hi Marcia,
Maria Garcia said:As you already know, we have filed Bug 672552
Thanks for the confirmation, because I did not find the bug mentioned in a discussion, so I was not sure.
Maria Garcia said:is this what you are referring to?
Yes and no. I experienced the same problem with view rotation, but there is also problem with element selection, e.g. when there is a simple element (like slab or sphere) in the same view as view, to select element (A) does not work at all or (B) MicroStation hands for seconds or even minutes. And it is not problem with Element selection tool only, but with any selection like Copy element or Move element ... so in reality, nearly no tool can be used when working in a view where point clouds are displayed.
Maria Garcia said:This Bug is not fixed yet and in theory it has been scheduled for update 2023.
Ok, the message for users is: Prefer Autodesk. I cannot imagine the users will wait more than a year to be able to use point clouds in MicroStation. It's about to pay SELECT fee for this period and not be able to use the product for any serious work?
And I guess it's not only about MicroStation, but the same problem exists in ORD (ok, let's move to Civil3D) and OBD (final push to migrate to Revit).
Maria Garcia said:Issue is not reproducible in MicroStation CONNECT Update 15 or SS10.
Yes, that's probably correct (I have no U15 installed, but U14 is fine).
Regards,
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan Šlegr said:I cannot imagine the users will wait more than a year to be able to use point clouds in MicroStation.
Everyone says that their bug is more important to be fixed, wait in a line, if it is issue in 16.1 then in U18 it could be fixed.
Oto said:Everyone says that their bug is more important to be fixed
Yes, we all do it :-)
On the other hand, it is not newly discovered bug, but something that was broken by Bentley dev team itself.
Oto said:if it is issue in 16.1
No, it was reported (view rotation delay) and confirmed as bug for U16, so it is not new.
Oto said:then in U18 it could be fixed
Unfortunately you are probably right.
A crazy thing is that as developer I know the analysis can be quick, because when you know the version when it worked (U15) and when it was reported as broken (U16.0), you can you commits bisect mechanism to quickly find a commit that broke the feature.
Something else when new bug is reported, when analysis can be lengthy and complicated.