Adjust Level Line Offset from crop Region by scale or custom settings

[edanastas]

Is there a way to control the Level head offset from the crop region of the view. I'm constantly moving these levels out on sections and floor plans.

This would be awesome to be able to control with a default offset or at least if Autodesk doesn't want to give this control up (why, I don't know), then change the offset depending on the scale.

Let me know if I'm missing something.

Thanks,

Edward

[drandallbair]

One way to do this is to edit the Level Head family.  It doesn't give any dynamic control, but it does fix the problem of text overlapping the drawing and needing to be manually adjusted in each view.

The fixed margin is measured from the intersection of the two reference planes as it is in most families.  If you open Visibility Graphics, you can turn on the reference planes and actually see where this point is.  From there, you can just move the text and linework over by an inch or so (removing constraints as needed).

This is the default:  

This is about where I modified it so that it stayed out of the crop box:  

Load that in and it works.

If you need some at different margins, you can create different families of them, but since it is related to the level itself, there's no way (currently) to have it show up with a 1" margin in one view and a 2" margin in another.

[asWAPL9]

reviving this thread to gently remind you that it is 2021 and this ....problem... still persists. 

it should not be more complicated than changing two lines of code in the brains of revit to allow a custom offset of a level head from a crop region, however here we are, years later, still finding the same errors, or inconsistencies, on a 2500 euro membership, on a what.....20-25 year old program?

can we pleeeeaaaasssseeee get this through on the revit update roadmap

No joke have to set up over 30 sections on plans and i must adjust for every section the level offset from the crop region. that is a minimum of 60 monkey operations. I have calculated that I lost until now, 2 hours today, just waiting for the levels to process the "move" command in the background, because apparently, revit is not capable of understanding that a 2D element in a view is just a projection of the 3D element, so it has to render everything in the background, which takes roughly 10-15 seconds per section per move command. I will leave it to you to figure out my frustration level at this point, and hopefully I am getting my wishes across in the nicest passive aggresive way I can right now. 

Thank you for listening to my lamentations, @loboarch