topic Match orientation to layout - doesn't work with annotative or dynamic blocks ? in AutoCAD Forum

Match orientation to layout - doesn't work with annotative or dynamic blocks ?

aj_email_2010 — Wed, 04 Mar 2020 11:20:44 GMT

When creating a block there is the option to "Match orientation to layout", which if 'yes' is selected then the block auto-rotates so that it will always show "zero rotation" when viewed in a viewport from paperspace, even if that viewport has been rotated/twisted using the command "DV".

But it seems that the option to "Match orientation to layout" doesn't work when an object within the block has been set to "annotative" or if an object within the block has been given a "dynamic control".

Does anybody know a way around this?

I am trying to create a very simple auto-rotating block that is basically just a leader and an editable text attribute - in effect trying to create an auto-rotating "MLeader".

p.s.

posted a similar question in the dynamic blocks section, but there doesn't seem to be many viewing or replying in there

Cheers.

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

imadHabash — Wed, 04 Mar 2020 12:37:10 GMT

Hi,

can you attache here a CAD dwg sample that describe your issue please ?

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

aj_email_2010 — Wed, 04 Mar 2020 14:19:57 GMT

Sure, please see two DWGs attached.

The first DWG has the "MLeader block" auto-rotating with the viewport DV angle, this is just a simple block consisting of a leader and a text attribute. But this option does not have the full functionality that we are looking for, as we want to be able to control the position of the arrowhead each time we insert the block.

The second DWG has the functionality but does not provide the auto-rotate, this is because the "Match orientation to layout" option automatically disables itself once the block is saved with a 'dynamic function'.

So we are simply looking to find out if the software is able to jump through what seems like a simple hoop to achieve the result we are after.

Cheers.

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

imadHabash — Wed, 04 Mar 2020 14:47:45 GMT

Kindly ... see attached CAD dwg Test file ? it's works ... isn't it ? i just make a new attribute block .

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

aj_email_2010 — Wed, 04 Mar 2020 14:58:56 GMT

Thanks for the reply. Much appreciated.

The Test.dwg block that you attach is the similar case for one of the DWGs I originally replied with.

In that yes that does rotate with the viewport, but we need the dynamic functionality to be able to move the arrow head. As soon as the dynamic control is added to the block, the function of "Match orientation to layout" becomes automatically disabled.

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

aj_email_2010 — Thu, 05 Mar 2020 08:49:53 GMT

I guess I'll have to accept this is something that the software simply can not do?

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

imadHabash — Thu, 05 Mar 2020 10:44:52 GMT

Agreed ... Dynamic blocks loose this valuable option .

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks

eandersonJQW5V — Wed, 18 Aug 2021 18:07:05 GMT

I hate that AutoCAD does not have the ability to make dynamic blocks Match orientation to layout!!

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks ?

RobDraw — Thu, 19 Aug 2021 10:19:33 GMT

Hate is such a powerful word, especially these days.

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks ?

JLJZPWBF — Wed, 15 Feb 2023 21:23:45 GMT

The block can be annotative, but it can't be a dynamic block to match view orientation.

What kills me is that I can put an attribute (not in a locked position) in the block but it doesn't even give me a grip to where it could be moved. I use data to fill in the attribute when I import it, but since I can't move the attribute out of the way in many places that overlap other things in the drawing. So now I have to import it twice, once for the block and then again with a block that is just an attribute. It's incredibly annoying and frustrating.

Re: Match orientation to layout - doesn't work with annotative or dynamic blocks ?

ryan_rinconesBGVVS — Fri, 24 Apr 2026 16:18:24 GMT

Just gonna drop this here . . .

I had the same problem as the OP, so I spent some time putting together 2 separate blocks with the intention of having then AUTOMATICALLY orient with any viewport rotation, without the need for a rotation parameter. One is a block with simple mtext using an annotative text style set to "Match Orientation to Viewport", the other is a block with a legit text attribute, using the same text style but also with attribute and block settings configured accordingly. My goal was to eventually use these along with the add-In "Increment" by Giles Chantreau, which is free and awesome; been using it for years. It allows you to either create new items or replace existing with a defined sequence of numbers or letters. For this, the block with attribute was the only viable solution, as the Increment app identifies the attribute value and is able to create new instances of the block with sequentially-advanced attribute values. The app can create basic text objects sequentially without the need for a block, even creating prefixes or suffixes. But in my case, I wanted to use blocks for the one-stop edit or copy to a new block if needed (vs having a ton of individual text objects). Anyway, didn't mean to plug the add-in but my main hope is that these blocks are what folks like the OP are looking for.

NOTE: as part of adding annotative scales to the attribute block, I had to show ALL scales used before adding. This seemed odd at first since the attribute within is set to Anno=NO but then I realized that the text STYLE is set to annotative. One of those things that is not readily evident but where the behavior after making the change has a 'retroactive rationale". 😃