DREFs not updating automatically

DREFs not updating automatically

Joe-Bouza
Mentor Mentor
285 Views
6 Replies
Message 1 of 7

DREFs not updating automatically

Joe-Bouza
Mentor
Mentor

Why would this start to happen? did a system variable reset?

Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

0 Likes
286 Views
6 Replies
Replies (6)
Message 2 of 7

Cadguru42
Advisor
Advisor

I've also had issues with that in C3D 2026, but haven't figured out a trigger. It sometimes happens with pressure networks, pipe networks, and alignments. 

C3D 2024-2026
Windows 11
32GB RAM
Message 3 of 7

Joe-Bouza
Mentor
Mentor

(command "AECCFORCESYNCHRONIZEREFERENCES") to the acaddoc.lsp

 

do you think it could be a hinderance?

Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

0 Likes
Message 4 of 7

Cadguru42
Advisor
Advisor

@Joe-Bouza wrote:

(command "AECCFORCESYNCHRONIZEREFERENCES") to the acaddoc.lsp

 

do you think it could be a hinderance?


Wouldn't that just sync on open? Is that what you're noticing?

C3D 2024-2026
Windows 11
32GB RAM
0 Likes
Message 5 of 7

Joe-Bouza
Mentor
Mentor

correct.

Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

0 Likes
Message 6 of 7

Cadguru42
Advisor
Advisor

@Joe-Bouza wrote:

correct.


I don't see anything that command should mess up. But then again, this is C3D we're talking about. The few times it's happened to me I chalked it up to our project being on ACC and Desktop Connector not working properly. But it could be something else going on.

C3D 2024-2026
Windows 11
32GB RAM
0 Likes
Message 7 of 7

cwr001
Collaborator
Collaborator

That's funny - I also ran into non updating pipenetworks recently and chalked it up to the project being quite big and Civil3d just being wonky. (I'm in 2025.2.2 though)

But the fact that it's happening to others without a clear cause is something between a nuisance and deeply concering.

This stuff should "just work", otherwise DRef's are sort of pointless.

 

Updating the acaddoc.lsp is a nice brute-force solution but it might slow down opening times for files with a lot of references.

 

I also discovered other issues that were not a problem a release ago: for example automatic corridor intervals at elevation targets are suddenly not created although the setting is set to "True". This can potentially lead to very unpleasant situations.

We are in the remarkable situation that we don't get any new features for certain parts of the software yet still fresh and hot bugs are introduced. Autodesk must have discovered vibe-coding...