When the version naming of Microstation changed from CONNECT to 2023, what does it means to the future? Or say, Microstation 2023 is a special memories version? In view of the long duration of infrastructure projects, it makes sense for the product line of Microstation last for 10 years (and become more stable). So i am confused with this new naming policy, but i found no useful information related to that in Wiki nor in Announcement forum.
clever_anthony said:When the version naming of Microstation changed from CONNECT to 2023, what does it means to the future?
I think it does not mean anything, just naming:
First personal impressions is it look a bit faster, so probably some internal optimizations and enhancements implemented.
Mark Shamoun said:Hopefully they also simplify that - a simple OpenRoads Designer 2023 and then 2023.1, 2023.2 is all we need.
I agree. The naming of civil products is confusing marketing chaos on drugs, nothing else. Impossible for normal user to understand what products are the same (minor updates based on the same civil schemas) and what product upgrade requires standards and DGN updates.
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Jan,
Nice run down on the changes. Looks like the 'Phase 2' iTwin engine or local iModels have not been included... yet?
"Phase 2 of our journey involves improving our existing desktop products using the same iTwin engine. Users of our MicroStation and engineering design and analysis applications will next gain new features that can make their projects more efficient, more connected, and the results more valuable. We can do that by augmenting, not replacing, their existing tools, workflows, file formats, and deliverables. The iTwin engine will run on the same desktop ‘in process’ with the design applications, synchronizing a local iModel and connecting to cloud services when and as necessary.”
Maybe this will be tied into the next version after ProjectWise 2023 rolls out?
Curious to see how this would work.
dominic SEAH said:Looks like the 'Phase 2' iTwin engine or local iModels have not been included... yet?
At least BIM (local static file) file now can be referenced, which is tiny, but appreciated (at least by me ;-), step towards integration MicroStation with iTwin / iModel world.
Yea, good to see support for the .bim format. But, it is a 'foreign' format which I understand is based on meshes. Less precision.
OTOH, game engines and cloud-based apps seem to love meshes. Next gen BIM apps seem to be all cloud and mesh based which allows some very large models.
Maybe one way dual saving to a local iModel would allow Mstn to switch between BREP and solids to meshes when needed in a more transparent and useful way?
dominic SEAH said:Yea, good to see support for the .bim format.
If I understand it correctly (maybe I am wrong), it is not BIM format, but BIM file ... confusing naming :-(
Because "Attach BIM" is paired with "Attach iTwin", I guess it's local static snapshot of iTwin data. There is no difference in content or precision, only it is static and cannot be updated.
Snapshot can be created e.g. from .dgn using iTwin snapshot tool, but technically any application, because on iTwin.js API, is able to create this format (even without connection to iModel Hub / cloud services).
dominic SEAH said: But, it is a 'foreign' format which I understand is based on meshes.
Not in his case.
dominic SEAH said:Maybe one way dual saving to a local iModel would allow Mstn to switch between BREP and solids to meshes when needed in a more transparent and useful way?
When local briefcase is created, it is created using geometry, supported by iTwin.
With regards,
Yes, very confusing.
But I hope you are right.
Otherwise, 2023 looks quite modest in scope.