Currently I am creating company/domain specific content to be used across the company in Microstation SS4. All of these content will be created using generic seed file of Microstation SS4 and will be saved as a .dgn.
I have seen the AECOsim SS6 content incompatibility issues with AECOsim connect versions. The family/parts naming and the levels naming convention is completely different when I compare AECOsim SS6 to AECOsim Connect version(now OpenBuildings)
I'm unable to get my hands on Microstation Connect version at the moment. Could you please advise
1. if SS4 content is fit to use across all versions of upcoming Microstation/AECOsim releases OR Should the ss4 content be restricted to be used for SS4 and best way to move forward and migrate to Connect series is to create new versions of content within Connect series/3D environments?
2. If it is fit to be used, then are there any specific steps/cautionary measures to be taken to make these SS4 content compatible with the latest Microstation/Openbuildings software versions?
Please advise the best way to move forward.
Rohini Kulkarni said:I'm unable to get my hands on Microstation Connect version at the moment
MicroStation CONNECT was released commercially in 2015. It is available from Bentley System's software download site. I believe that you must be the registered administrator, or someone approved by the registered administrator, to gain access to that site in order to download software. Or are you asking something else?
Regards, Jon Summers LA Solutions
Hi Jon,
My query was more related to compatibility of files/ 3D content created in SS4/SS6 that is intended to be used with MicroStation Connect Edition, at a later date, when v8i is no longer available.
What would be the risks? Is there anything we can do now, in SS4/SS6 while creating the content(3D models) so that they can be used very easily in the connect edition of both Microstatio nand AECOsim?
Thanks
Hi Rohini,
there are two aspects. One is the geometry. and CE and V8 useses the same DGN Format, so there will be no risk.
The other aspect is the Building-designer Dataset. The default Dataset has changed, lets call it "modernized" but this has the effect, that some Elements change information.
To prevent this, create your own V8-Dataset (maybe just a copy of default) and migrate it to CE later.
But as Bob Rayner said. this is a question of time. How long will your V8 live?
Mit freundlichen Grüßen / Best regards Volker Hüfner
| AB_DATE Engineering Software | ab-date.de |