Hello allI switched from Bentley view V8 to the Bentley view Connect Edition v12. This version does not handle many dwg's anymore. Even older files that worked without problems with the V8 version can no longer be opened with the V12 version. Only if I create a small file with few elements, I can view it with V12. Does anyone have an idea what to do?
Thanks for help
Claus
Hello Claus,
I just have tested with both files, trying to open them with Bentley View Update 12, and I don't see any problem.Both files open fine, without the warning "Unable to open design file"Are these files already edited; exploded the AdvancedSteele elements?
Regards,
René R. van den BrinkTechnical SupportBentley Systems Incorporated
Hello René,
yes, the AdvanceSteel elements are exploded. But the file can not be opened with me anyway.I get these two messages:
We've seen similar things due to various Object Enablers "taking over" DWG file handling in Microstation CE from the inbuilt Real DWG one, e.g. Civil 3D.
Keep an eye on the Message Centre when you first attach a DWG.
Mark
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
I loaded a file that worked. Then I opened the Message Center und tried to load a problem file.
This is, what the in den Window of the Message Center appears:
I have no idea what it means.
That's telling me you have a Autodesk AutoCAD 2018 Object Enabler that is handling the DWGs in View. Maybe try uninstalling the enabler and see what happens?
The Object enabler 's in the control panel were Autodesk Civil3d 2019 and other third party object enablers. I deinstalled the Autodesk Object Enabler but the problem was not yet solved.
Then I renamed the file ASDemandloader.dbx which came perhaps from AdvanceSteel.
Now Bentleyview works as expected. Thanks very much!
I hope that no other program will miss this file.
Great to hear, we're also seeing some issues with the Object Enablers and DWGs. Hopefully a variable or something can be added to allow for enabling/disabling of OEs or some more work on compatibility with them as this never was an issue in v8i.