Adding Leader to Multileader Puts Multileader onto Current Layer

[rlattaQWEML]

Adding a leader to a multileader object reassigns that object to the current layer. I don't want this happening. I want the object to stay on its original layer. This just started happening recently (I'm on C3D 2025). Is there some system variable I need to adjust?

Thanks!

EDIT: See attached video

[brian.strandberg]

Confirmed in Civil 3d 2025.1  Did not do this in 2024.4.  Thanks.

[aharmon]

I'm having the same issue in C3D 2025. Very aggravating.

[lim.wendy]

Hi Robert,

Thank you for reporting this issue with the Multileader object changing layers in Civil 3D 2025. I appreciate you taking the time to document the problem and provide video examples.
I've researched this internally and found that other users have already reported the issue. I can confirm that our development team is working on fixing this behavior.
Unfortunately, I cannot provide a specific timeline for when the fix will be released. However, if you need an update on the status, please reply to this thread. Alternatively, you can submit a Technical Support ticket and reference the ID ACD-45011 for more direct assistance.

[chriscowgill7373]

it is all part of the new MLEADERLAYER - system variable that was introduced in 2025, puts an mleader on the layer specified.  unfortunately, it seems to think that when you modify an existing mleader, it is the same thing as creating it, so it moves it to the layer that is called for (current, or a specified one)

[rgrainer]

I hope you are aware that this has been an issue for 5 months or so.

This is seriously affecting my workflow and this "feature" should never have been introduced as it was/is. I'd like to see the wish list where this request came from. Seriously, who asks for this type of thing?
No one should be asked to or be made to create these tech support tickets. This is all Adesk's fault and no one should have to waste their time submitting anything to anyone as this is a known issue and it also bothers me that no one at this organization seems to really care about getting this addressed in a timely manner. 

[JustinGG5N9H]

Looking for an updated on this issue as well. Replying to this post to keep it on your radar.

[kheeED49R]

MLEADERLAYER-----0

[chriscowgill7373]

I did not see this listed in the 2025.1.1 that was released a few days ago, has anyone tried it since then?  @kheeED49R can you please provide more context to your response?  Are you saying if you set the mleaderlayer to 0 it will not change your current mleaders when you edit them?

[JustinGG5N9H]

No, the problem was, anytime you added a new leader to an existing Multileader Note, it would changed the Multileader Layer to what ever layer you had set as current. (Example: All my waterline notes are set to C-Anno-Water. I need to add another leader to a note for a new water valves I added. I was just working with C-Anno-Sewer. If I add a leader to my water valve note, the note switches to the C-Anno-Sewer layer, and then I have to manually switch it back.)

Also, I have not updated yet. I will run and respond to let everyone know.

[JustinGG5N9H]

Update ran, and issue unresolved. The Layer still changes.

[mhaarmannB8YYD]

I have the updates and it still happens. Also happens with REVCLOUD. 

The latest update fixed it for LT.  🙂  Guess we'll have to keep waiting.

[Cadguru42]

I believe this is a known defect that was caused by the C3D 2025.1 update. I haven't installed it because of this very issue and it looks like C3D 2025.1.1 also doesn't fix it.

[rlattaQWEML]

This actually appears to me to be corrected on my end. See attached new screen video. I'm running 2025.1 Update (Product version 13.7.765.0).

[aharmon · Accepted solution]

The "AutoCAD_2025.1.1_Update" fixed this for us. Don't confuse the C3D updates with the core AutoCAD update that this fix requires. I had to manually download it as it didn't show up in Access.

[JustinGG5N9H]

I did update for AutoCAD 2025.1.1. No effect on our end.

[aharmon]

Strange. I confirmed the problem with the mleader on a user workstation, installed the AutoCAD 2025.1.1 update, and then retried and it was fixed. I didn't even change the MLEADERLAYER setting. It's actually set to "use current" and works fine now.

[JustinGG5N9H]

As you can see, I have updated to AutoCAD 2025.1.1. (Image Below), and the issue continues (Video Below)

 

[mhaarmannB8YYD]

- My AutoCAD 2025 was updated as well to 2025.1.1 and it did not fix it either in Civil3D2025. Still changes the layer to the current layer when you add a leader.

- Found out how to get around this until they update it:

• MLEADEREDIT command still works if you type this in and then add your leader
• Which means you can go into your CUI and edit the Macro for this button on the ribbon  scroll down to the Annotate - Leaders>>>>>select and then select the Add Leader from the multileader panel>>>>>
•  select the Macro under the Command>>>>>>
•   change to >>>>>> 
• "APPLY" the changes and/or "OK" and when you select the "Add Leader" button now, it should use the MLEADEREDIT command to add the leader and NOT CHANGE THE LAYER TO THE CURRENT LAYER. For some reason it turns on the Dynamic Input (DYNMODE) ON? Which you turn off afterwards but at least it works.
• Or you can use the MLE short-cut key (or change to your preference) for MLEADEREDIT. Haa, haa.
• Hope this helps until they update it for Civil3D.

[c_haymon]

This worked!! Thank you 🙂