Annotative block with multiple line attribute not scaling correctly Xref

[Anonymous]

Hi there,

I needed some annotative blocks with attributes in my project and when I tried to apply them to different scale I came upon this error. Thus, when in annotative block you have attribute with multiple lines checked then if the drawing with that block is loaded as XREF the text simply wouldn't scale together with block but remains in scale which is on top of the list. Lets be clear of one thing, in the drawing the blocks are scaled normally, this problem only appears when loaded as XREF.

The only solution I found is changing attribute to normal one, and for now it works, but in the future i may be in need of multiline style attribute that scale with block if it's loaded as XREF

Thank you for your time

Oghi

[pendean]

Can you share your anno block in a DWG file that exhibits this problem please and explain how exactly we may recreate your issue?

TIA

[Anonymous]

Hi,

so if you create any anno block that have attribute with multiple line option checked this problem appears. It doesn't matter of geometry within the block it's the text (attribute) that is not scaling (working).

As I previously stated, this only happenes when the drawing with these kind of blocks is loaded as XREF.

I don't know how I could explain any clearer?

Try to create this kind of block and save drawing. Afterward load it as XREF and try to change scale you'll see that text is not scaling it remains the same

Thanks

[steven-g]

To the best of my knowledge Annotative xrefs don't exist, the scale of the block in the xref'd drawing may well apply, I haven't tested it but I can't see it working for the same reason you can't use the dynamic components of blocks in xrefs, they need to be in the host drawing for that.

[Anonymous]

Hi,

So, I explained what is the problem if you do not understand there are attached 2 DWGs if you open them both and try to change scale 1:1, to 1:2 and 1:4 and you will see the difference.

I'm talking about annon blocks in an DWG when you load Xref, not annon Xref

thx

[Anonymous]

FYI

Maybe I didn't mentioned, if you do not check the multi line box in the attribute options it works just fine.

[steven-g]

I understand perfectly and your drawings just confirm what I was trying to explain. Your block is annotative only in the drawing in which it is inserted (the drawing named 'PROBLEM_XREF') if you open that drawing you can change the scale of the annotative block called 'FIX IT' as you want.

The drawing called 'PROBLEM' does not contain an annotative block called 'FIX IT' it only contains an xref of another drawing, and you cannot change the properties of the block in the xref from within the drawing named 'PROBLEM' that isn't a problem it is just NOT how blocks work, if you want the block to be annotative in this drawing it has to be inserted in this drawing as a block.

[ferdi.jafar]

Hey,

I have Xref-ed the block to a new drawing and right clicked edit xref in place and selected the block and in the properties at the annotation scale I added the annotative scales that I wanted and seems to work. Maybe this will help.

[Anonymous]

Hi,

I will try to explain myself better. Below we have 2 DWGs and one is loaded as Xref into the other. We have 2 annotative blocks one is with the problem when changing scale and the other is working normally, but only in DWG named PROBLEM (try with pre-loaded scales 1:1, 1:2, 1:4). If you are trying to see the problem in DWG named PROBLEM_XREF you cannot see it, because it is not the issue. See the difference between two blocks. The only difference is that in one block in options I've checked the box Multiple Lines and in the other not (See pic as reference)

Thanks

[ferdi.jafar]

The Dwg that you have attached seems to scale normally. No problem there.

[Anonymous]

Can you see that the word PROBLEM in the first block is not scaling?

At least that is what I'm seeing with AutoCad LT 2020

*attached pcs as ref.

[ferdi.jafar]

Please see below snapshots from the problem.dwg file.

[Anonymous]

Ok, but it didn't solve my problem if you are able to see it, and I still don't know how.

What AutoCad did you use?

[ferdi.jafar]

Hey,

Send me the dwgs that you are having trouble with.

Autocad I am using is 2020 LT

[pendean]

I wonder if not having these on is your problem, your top file behaves fine here for me with the XREF in it

[Anonymous]

Hi

No, not really, because if I turn them off the word PROBLEM just disappears, because it is present only in scale 1:1

FYI

I have Italian version of AutoCad 2020LT with english language pack, so my other colleagues have the same problem on their computers.

[steven-g]

I must apologise, I hadn't opened your drawings before, and I can confirm that I have the same ERROR in 2020LT in 2018LT and 2019LT the multiline attribute does change to suit the annotative scale inside the Xref, in 2020LT it does not, at least not on my computer so if it does work for other people then it sounds like a setting problem.

[pendean]

I must not be understanding the problem then< I can change the annotative scale all day long in your top file the the XREF content scales correctly.

But your statement:"...because it is present only in scale 1:1.." is interesting: open your XREF file, cycle through 1:1 then  1:4 then 1:5 and other scales, does it work? If yes, SAVE that file, close and open your top file, does the problem go away?

FYI I am testing in LT2020.1.2 update.

[steven-g · Accepted solution]

Dean, you must have a magic touch 🖖, the drawings you posted worked perfectly, so I deleted all files, downloaded the OP's latest version again, and it failed, so I opened the problem_xref file cycled through the scales then back to 1:1 and saved the drawing again (I made no changes just tried the scales and saved) and voila! open the first drawing again and now it works.

[Anonymous]

Hi there,

thank you for your replay. After changing multiple times PROBLEM file after few scales added and saves it did resolve the problem.

Thank you once again.

Maybe this is a minor BUG that could be fixed with a update or something