Cannot delete 1:1 scale from Annotative block

[bull504]

Ever since upgrading to Autocad 2025, any annotative blocks that contain attributes that are inserted into a drawing always contain the 1:1 scale attached to them and it cannot be deleted. Example, the elevation callout below was inserted on a 3/4" scale but comes in with the 1:1 also. In previous versions it would only have the 3/4" scale attached. I cannot delete the 1:1 from the block. Anyone know what is going on? 

[-didier-]

Bonjour @bull504 

This is the normal behavior of the software.
AutoCAD needs this scale coefficient as it needs layer 0 and the line type "continuous".

This is the minimum, which cannot be purged

Amicalement

[cadffm]

Hi,

>>"was inserted on a 3/4" scale"

Do you mean "while 3/4" scale was active (CANNOSCALE) ?

>>"but comes in with the 1:1 also"

How do you insert the blockreference? Is it different if you are using CLASSICINSERT command (while CANNOSCALE is set to 3/4")

?

>>" I cannot delete the 1:1 from the block. "

Sounds impossible, please share a sample .dwg (with only one fresh insert), thx.

[cadffm]

@-didier- 

That's (near to) true, but we are talking about OBJECT SCALEs, not about the defined scale list in the file!

[bull504]

@-didier- @cadffm 

Correct, I am specifically referring to the objects scales. I understand 1:1 is required for the drawing scale list. I am not trying to remove it from the drawing, just the object. Which is how I've usually done it for 10 years. How it is behaving now in the 2025 version is completely new. 

[bull504]

1) yes, while 3/4" was the active scale of CANNOSCALE

2)Block is inserted via a tool palette. Using the CLASSICINSERT command the block behaves appropriately as long as I edit the attributes to be non-annotative within the block

3) Attached drawing, Side note, this only affects blocks with attributes, it does not happen with other annotative objects such as dimensions. It's annoying because If I am working with 2 scales (3/4" and 1/2") when I change my CANNOSCALE accordingly, I can no longer read objects on the previous scale because they will default to 1:1 for anything not on the currently active CANNOSCALE

[AdamPJN3D]

I'm having the exact same issue. I'd love a solution. I recently updated to 2025, I never had this behaviour in my older version. The problem seems to be related to the palette and inserting blocks with text. Possibly annotative text styles.

[baccioni]

Any solution to this? This is quite a significant issue:

If I import an annotative block from my Palette with the drawing scale set to 1:50, the block comes with a double scale property, 1:50 and, always, a 1:1 undeletable scale. 

So it happens that if I set the drawing scale at 1:20 and I set "Show annotation scale" to always,The block uses the geometry at 1:50  and the text at scale 1:1, rendering the text barely visible and offset

[pendean]

@baccioni For the most part we end users cannot change the behavior of the software. Sorry.

Ask Autodesk to change it (back?) in future versions here

 https://www.autodesk.com/company/contact-us/product-feedback

[baccioni]

No dude. Undetrstand my words. This is a bug or something I miss that cjhanged. It's never been like that. It started in 2025. 

When I insert an annotative block from the Palette it's inserted with a bugged 1:1 scale.

If I insert the block (previously inserted fromt the Tool Palette, hence already in the drawing) from the Block insert Palette, it works perfectly.
These are both blocks inserted at 1:100. The one above comes from Tool Palette

See the scales

This is what happens when Annoallvisible is set to 1 and drawing scale is set to 1:50

The blocks are the same. But the one with the messed up text comes from the tool palette

[paullimapa]

Have you downloaded and installed the 2025.1.1 update? Perhaps that may make a difference 

[cadffm]

@bull504 @baccioni @AdamPJN3D 

Yes, something wrong with the TP insertion tool in this case.

I can't test it today,  and not tomorrow, with the newest ACAD2025.1.1 (are you all tested with Acad Productversion 2025.1.1 / released October 29, 2024)?

and my test in December is long time ago, so I can't remember the tested version.

Anyway, I think the problem will be solved with the next product (not product update).

Let's call it a vision.

But: It probably won't solve the problem with existing block references.

I hadn't looked into an edit to remove the scale in December.

Maybe I or someone else will find time to do that.

[baccioni]

Yes Sebastian, I'm using the latest update. I tried to redefine the blocks using design center, tried to resave the block, but nothing seems to work. I can't get rid of the 1:1 scale from the block pasted straight from TP (or pasted from blocks coming straight from TP; only if I reinsert the block from BP I get rid of the 1:1 scale). Hence I have a few hundreds of corrupted blocks that won't display text. The worst happens in nested blocks. I hoped to find a way to isolate the blocks with a specific annotative scale (the corrupted 1:1) but it seems that neither QS nor Filter can do that. I  think I can access that with Autolisp+ActiveX, but I have not yet tried it. If you stumble upon something, I'd appreciate if  you let me know.

KR,

Roberto

[cadffm]

So it is still a problem with TP in 2025.1.1 

(does it work if you don't have annotation objects inside the block? What is useless, so test it)

Test only in new files, where all blocks not pressent.

-

We need to wait for the next update or program version.

[baccioni]

It seems so.

The bug shows with Annotative blocks that contain text (attributes, plain text etc.), when imported through TP.
Blocks without annotations perform regularly.

Blocks with annotations have this 1:1 bugged scale addition that messes up text display.
Blocks with annotations imported through TP and duplicated through BP (block insert palette) get rid of the bug.
If it's not a bug and someone knows of a new behavior of 2025 that provokes this, and how to manage it, please let me know.

[cadffm]

I am not sure if you tested what I asked for (sorry, my english 😶), so let me ask again:

You said:

"The bug shows with Annotative blocks that contain                           text (attributes, plain text etc.), when imported through TP."

I am hoping

"The bug shows with Annotative blocks that contain ANNOTATIVE text (attributes, plain text etc.), when imported through TP."

Please verify that (I couldn't read about this in your reply)

BEDIT on of your blocks in question,

Command: (sssetfirst nil (ssget "_X" (list'(-3 ("AcadAnnotative"))(cons 410 (getvar 'CTAB)))))

If some objects are selected: Properties Palette [CTRL]+[1], Turn Annotation = No

Command:_BSAVEAS testblock

create a TP insertion tool and test it with this block.

Still an issue?

If so, I was wrong with my idea.

>>"Blocks with annotations imported through TP and duplicated through BP (block insert palette) get rid of the bug."

Because the block is always okay, we are talking about INSERTS (Blockreferences of this Block) and TP,

the TP insertion tool creates a bug for these Inserts.

[baccioni]

What's your language Sebastian? If it's spanish I can read it. Also French. And Italian. 

[baccioni]

In any case I tried Annotative blocks with annotative and non annotative text. If that is the question. And it's not working.

[cadffm]

Alemán, no frech, no espanol, no italiano, Sólo conocimientos rudimentarios de inglés o alemán.

Yes, that was the question: It also fails with blocks that do not contain any annotative objects like attributes or text, mtext, hatches or block references too?

Your answer is Yes, so the only things you can do are

- don't use TP or

- check out a way by programming to get rid of the wrong connection of scale&blockreference

- wait for the next release and cross your fingers

[baccioni]

---

@cadffm wrote:

Alemán, no frech, no espanol, no italiano, Sólo conocimientos rudimentarios de inglés o alemán.

Yes, that was the question: It also fails with blocks that do not contain any annotative objects like attributes or text, mtext, hatches or block references too?

Your answer is Yes, so the only things you can do are

- don't use TP or

I will switch to Block Palette Libraries, using my Tool Palette files as sources. This works. Not ideal, but works.

- check out a way by programming to get rid of the wrong connection of scale&blockreference

I will think about that. I'm too busy now with a fast paced project. 

- wait for the next release and cross your fingers

well... crossing fingers rarely works. I'm still waiting for the solution to pc3 bug that was raised in 2024, and never solved.

---