Layout bug: rotated text cut off - depends on position on paper

See pic and Layout file. Size A0 paper. Using default text in layout. When rotating the text 90 degrees, some parts of the first letter are cut - it depends on the position on the paper.

textCutOff.layout (9.8 KB)

Note: I noticed the same cut-off problem in Layout before when using dimensions in SketchUp - that bug still isn’t solved (May 2018). See Layout-bug: Dimensions (from SketchUp) are 'cropped' - depends on position on paper

I can reproduce it. This appears to be related to the distance from the page’s origin (top left corner) to the text. On large sheets text on the far right and/or bottom get this cropping worst.

@adam, have you seen this?

1 Like

We have seen this before, but we haven’t had time to determine the root cause of this issue. As @DaveR said, it gets worse the further from the page origin you get.

Adam

1 Like

Just tested and this issue is still there in LayOut 2023

On a related note, the position of the text shifts as the text box is rotated.

In the image below the text box highlighted in blue is nicely centered both vertically and horizontally. Doing an array for example illustrates the glitch.

Is anyone else experiencing this or is there a fix?

Thanks

This is the kind of thing I see. I don’t have Century Gothic on this computer but I tried a variety of other fonts. No weirdness that I could see.

Thanks DaveR,

Unfortunately for me all fonts do the same thing. Even the standard Arial Font.

This has been an issue for me for at least the last 4 or 5 versions that I can remember, so maybe its something to do with my system?

Digging a little more, it seems related to the OP in that the closer you are to the upper left hand origin corner, the less noticeable the problem is, the further you go to the lower right hand corner the more extreme.

Here is my Layout File in case anyone can spot if I am doing something wrong.

Layout-Text-Rotation-Issue.layout (78.2 KB)

Thanks

Hoping this issue gets some attention from Trimble. As you can see in my OP, this issue is already present since at least 2018.