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
Well, I have an idea:
https://microstation.ideas.aha.io/ideas/MSR-I-803
Tuan Le said:Well, I have an idea:
I guess there is no reason for new idea (which should be "how to add something new" section), when it is confirmed issue with bug number assigned.
Regards,
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Jan,
I've been doing some work with some point clouds of various sizes up to 40Gb and am not experiencing any issues in 16.1. Weird...
Mark
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
Hi Mark,
thanks for sharing your experience.
Yes, it is weird, because originally this issue was discovered not by me, but by one from my customers (and confirmed as bug introduced in recent versions by Bentley later). And I was able to replicate the issue on two different PCs (notebook and desktop).
Maybe there is some tiny difference (HW configuration, or how points clouds are used or whatever else ;-) that causes the issue does not exist always.
I am experiencing this issue also with U16.1, and also with OBD U8.