Not really - Autodesk has this setting in AutoCAD. Not many Engineers know
it exists or what it does. If you ask them to Set the proxygraphics
Variable to 1 and resave the DWG it is easy to do and takes a few seconds.
That makes the extended objects from Civil 3D available in the DWG as Proxy
Objects (Close Approximation Replacement Objects), because AutoCAD DWG does
not fully understand the Extended Civil 3D Objects or the core engines that
create them - look at it like TBC builds a Corridor. The Corridor builds a
Surface and Linework. To send data to AutoCAD the Linework can go out as
CAD objects (with some chording tweaks to handle AutoCADs inability to
handle 3D Curve Geometry), the Alignment we send as a Chorded Line because
AutoCAD doesnt understand Spirals or Vertical Curves or Stations or Station
Equations, and the Surface we send out as 3D Faces because AutoCAD doesnt
understand Surfaces only 3D Faces. If we want to send the same data to
Civil 3D then we can use LandXML that understands TIN Models and Alignments
and Linework and Points and is a richer exchange of Model Data - but we
still cannot send a Corridor Model because a Civil3D Corridor and a TBC
Corridor are completely different in terms of the way that they are put
together, so we send Surfaces and ALignments and Linework which is "Good
Enough" for the share data [provided the Receiver doesnt want to edit or
tweak the corridor). In that event we need to send them the VCE or VCL File
and they need TBC to read our files using TBC. Same in Reverse - If the
Source User is using Civil 3D there is a lot of their data in C3D that
AutoCAD doesnt understand (while they work together, you need C3D in
AutoCAD to fully understand the data). The DWG file has the extended data
in it but we cannot read it as we are only able to read the Drawing part
(the AutoCAD part). AutoCAD added the proxyGraphics setting to allow
Extended Objects to be able to be seen in AutoCAD and also in DWG True View
without having to need C3D, but they are Proxy Objects - Objects that look
kind of the same and have similar or close to actual properties, but are
approximations of the original objects because AutoCAD itself has no idea
what the originals really are or the tools to display and edit them (it is
just a CAD system) - only C3D in AutoCAD knows that. If the Proxy Graphics
Setting is OFF or set to 0 then we dont see the proxy objects at all - if
it is set to ON or 1 then we get the Proxy Objects and have something to
work with and those are close to but not the same as the original objects.
This is the bulk of your problem. The other problems are XREFs - XREfs are
External Files referenced into a Drawing DWG in AutoCAD. This allows
several CAD DWG Files to be viewed together in AutoCAD without having to
merge the data into one DWG. If you get just one DWG that references other
files and you dont get those then you cannot see the data because it is in
other files that you dont have. The AutoCAD user can write a new DWG with
all the XREF Data and the Current File Data into the new file, and if they
send you that then you can see all the data that they were working with.
Many Engineers forget to send you all the DWGs or Forget to create a New
DWG which combines all of the data you need into one file. We cannot
magically create data that we dont have because it is in other files that
were not sent to you.
There are other issues but these are the big 2 and they are easy to solve
by the Engineer or anyone that has a Civil3D license - set the
Proxygraphics Variable to 1 and save all the XREFs into one new DWG for the
deliverable, or save ll the DWGs for the Project and send them all as the
deliverable (all with the Prioxygraphic variable set to 1).
I hope that helps
Alan
On Thu, Apr 16, 2020 at 5:15 PM jason@b-jcontracting.com <trimble@jiveon.com>