Open roads Crashes/Closes on attaching a cad file

My workstation includes the following software:

ORD                       10.10.21.04

SS10                       08.11.09.918

C3D 2022            13.4.2119.0  (State Kit)

Our IT department recently updated ORD to 10.10.21.04

When I opened an ORD survey file,

ORD would actually crash when trying to Xref a DWG file. (regardless of ACAD version)

I read in a Bentley thread, that adding an underscore to the end of this folder name may resolve the issue:

C:\Program Files\Autodesk\temp\Civil 3D 2022 Object Enabler

So – new folder name:

C:\Program Files\Autodesk\temp\Civil 3D 2022 Object Enabler_

Does resolve the issue in ORD.

But my version of SS10 has now lost it’s ability to Xref a DWG. (regardless of version)

I have tried every version from v.2000 through v.2018

Removing the underscore from the Object Enabler folder will also not work.

I did notice that our IT department has also updated to SS10 version 08.11.09.918

As a test, I found another user in our department with the following set up:

ORD                       10.10.21.04

SS10                       08.11.09.878

C3D 2022            13.4.2119.0

His machine has the same issue in ORD, which is resolved by adding the underscore.

But his version of SS10 can still read the DWG files, with or without the underscore.

At this point I am suspect that version 08.11.09.918 may have issues related to the ACAD Object Enabler.

Additional info…

We also have a user that has

SS10                       08.11.09.918

But he’s only up to v.2020 on his C3D.

His SS10 is able to Xref DWG’s without issue.

New theory…

08.11.09.918 is not playing nice with AutoCad Object Enabler 2022

Hi Michael,

I've experienced something similar except for me it is only some and not all DWG files.
I too am running ORD 2021 R2 and Civil 3D 2022 with the object enabler installed.
What I have found is that any DWG file which has any Civil 3d data in it, or has been created from a Civil 3d template, or has simply been opened and saved in Civil 3d is enough to trigger the issue for me.

The only fix i've found that works is to open the offending file in Autocad or Civil 3d and type "EXPORTTOAUTOCAD". This creates a stripped down version of the file which doesn't contain any Civil3d object data, then I reference this file into ORD.

Thank You Matt, I do appreciate the input. I like the EXPORT idea and may be using that as a work around. Now that C3D 2023 FDOT State Kit is available, my next plan is to remove all instances of C3D 2022, then install the 2023 versions. I will post my results... after I put a few fires out.

Thank You Matt, I do appreciate the input. I like the EXPORT idea and may be using that as a work around. Now that C3D 2023 FDOT State Kit is available, my next plan is to remove all instances of C3D 2022, then install the 2023 versions. I will post my results... after I put a few fires out.