RealDWG 2015 libraries

Hi Michael,

RealDWG 2015 libraries will be included in a next version of MicroStation, which is now available for testing as AEP (Early Access Preview).

As usual (not in Bentley case only ;-), there is not announced fixed release date for this version.

With regards,

 Jan

Thanks, once again, Jan.

Thanks Don.

It sounds like you have things covered as of this moment.

If a situation arises where the RealDWG 2015 may be required, I'll come back to this thread.

I appreciate your reply and your depth of information.

Bye for now,

Michael

Hi Don,

I may have just found the need.

Autodesk have published Civil 3D Object Enablers for both 2015 and 2016 Civil 3D versions.
When I try to install the 2015 Civil 3D 32 bit Object Enabler onto a machine that has the realDWG 2014 libraries installed, I get a message:

Setup was unable to detect any target applications for Autodesk AutoCAD Civil 3D 2015 32 Bit Object Enabler.

Typically, the Object Enabler install would be targeting the realDWG libaray - right? ... which doesn't exist.

I have not attempted to installed the 2016 C3D Object enablers, but would expect the same issue; Missing realDWG 2016.

I have not tested viewing C3D 2015 or 2016 data in MicroStation SS3 as yet. My task is to investigate the integration of all things Bentley (well, PW and MicroStation mainly) with Civil 3D and I'm just begining that testing with the newer Civil 3D (2015/16) versions.


Your thoughts?

Michael

You're right on that, Michael - C3D OE 2015 won't install on RealDWG 2014 or any release other than RealDWG 2015. Is there any particular reason why you need C3D OE 2015? Like Chuck has previously pointed out, in recent years Autodesk has made C3D object versions forward/backward compatible therefore there may not be a real need of a version specific object enabler. In theory I'd expect a DWG file created from C3D R2015 to be displayed fine in RealDWG 2014 and causes no problems to C3D R2015 even if the file is saved in RealDWG 2014. I'd be interested in learning issues caused by mismatching versions of C3D objects using RealDWG 2014 or 2016.

That said, we plan to release an update of MicroStation V8i by the end of the year and it will have RealDWG R2016. If you are not ready to upgrade to CONNECT, perhaps you can wait and get the V8i update so you will be able to use C3D OE R2016.

They need to release enablers for their core software. So when AutoCAD 2016 is released, they need 2016 enablers if someone is to open a file needing enablers due to content from one of their vertical products.
In the past, an enabler would actually update the objects to the current version, even if the file was being saved to an earlier release. So not only was it necessary to keep enablers up to date, but you had to make sure no one opened a file in a newer version that was in use of a project. And that meant even if you were in 2007, or 2008 versions of a vertical product, just opening a file and saving it with a 2009 enable installed made that file almost useless for those using 2007 or 2008. Once the objects were in 2009 format, the objects, which often contain live design data were unavailable to users of the 2007 or 2008 version of the software.
We work on many different teams and have had to maintain 2009, 2010, 2011 and 2012 version available and separate so users could work on different teams requiring different formats. When 2013 came out we assumed we were again getting on a new merry-go-round. But then, 2014 and 2015 were released and the objects were now forward and backward compatible! And then, when 2016 was released, we were told that it continues the compatibility with the three prior versions.
Our current license offers up to 2015 so we are now rolling out new PC's with 2015 while current PC's are using 2013.
One caveat - if new objects are created, the older enablers cannot see them. However we have not been given any list of objects to see if this will impact us.

They need to release enablers for their core software. So when AutoCAD 2016 is released, they need 2016 enablers if someone is to open a file needing enablers due to content from one of their vertical products.
In the past, an enabler would actually update the objects to the current version, even if the file was being saved to an earlier release. So not only was it necessary to keep enablers up to date, but you had to make sure no one opened a file in a newer version that was in use of a project. And that meant even if you were in 2007, or 2008 versions of a vertical product, just opening a file and saving it with a 2009 enable installed made that file almost useless for those using 2007 or 2008. Once the objects were in 2009 format, the objects, which often contain live design data were unavailable to users of the 2007 or 2008 version of the software.
We work on many different teams and have had to maintain 2009, 2010, 2011 and 2012 version available and separate so users could work on different teams requiring different formats. When 2013 came out we assumed we were again getting on a new merry-go-round. But then, 2014 and 2015 were released and the objects were now forward and backward compatible! And then, when 2016 was released, we were told that it continues the compatibility with the three prior versions.
Our current license offers up to 2015 so we are now rolling out new PC's with 2015 while current PC's are using 2013.
One caveat - if new objects are created, the older enablers cannot see them. However we have not been given any list of objects to see if this will impact us.