First-off thanks autodesk for adding a random feature that makes things harder than they have to be for no reason whatsoever. Every-time I move my crop region just slightly all my gridlines go haywire. Actually, if I hide or unhide beyond the crop box, them my gridlines jump all over the place. WTF!!!? They also convert from 2d to 3d...
My gridlines extend past the crop, they are set to 2d. I do not want them to move with the crop box. How can I stop this from happening?
Stretch the 2D extent a bit and they will be disassociated from the crop region.
it works, the 2d grids won't move from crop box unless the corp box is associated with scope box.
@jfjacques wrote:First-off thanks autodesk for adding a random feature that makes things harder than they have to be for no reason whatsoever. Every-time I move my crop region just slightly all my gridlines go haywire. Actually, if I hide or unhide beyond the crop box, them my gridlines jump all over the place. WTF!!!? They also convert from 2d to 3d...
My gridlines extend past the crop, they are set to 2d. I do not want them to move with the crop box. How can I stop this from happening?
Nothing new going on here. Can you show us screen shots of what you are trying to do?
Also I understand that 2d extents are supposed to latch onto the cropbox, but I don't think that hiding and unhiding objects beyond the cropbox should make my gridlines move. Starting to look like a bug.
@jfjacques wrote:
How can I see if my crop box is associated with the scope box?
Just to be clear, datums (i.e. Grids & Levels) are associated with Scope boxes. Crop boxes are not ever associated with a scope box.
@jfjacques wrote:Starting to look like a bug.
Even before looking at solutions others might have?
How about those examples?
@jfjacques wrote:
Also I understand that 2d extents are supposed to latch onto the cropbox, but I don't think that hiding and unhiding objects beyond the cropbox should make my gridlines move. Starting to look like a bug.
What are those objects?
By associated i meant when your plan in properties has a scope box defined, cropbox will match to that and grids will move.
From what you are describing, it sounds as if the 2D and 3D extents of the grids have never been "disassociated" from each other.
When you first place a grid line that establishes the 3D extents of the grid. If you then crop the view, and the 3d extents of the grid fall outside the crop box, the grid extents will display 2D. If you continue to move the edge of the crop box further away from the 3d extents, eventually the 2D offset distance starts to move the 2D extents to keep it "X" distance away from the edge of the crop box. "X" distance is a system setting not controlled or editable by the user. If you are seeing this then you can grip edit the 2D extents of the grid. if you do this, now the 2D extents are in a different place and disassociated from the 3D extents. No matter where the crop region is now, the 2D extents will remain.
It can get weird and confusing if you have multiple views where you are manipulating the grids and not paying attention to if you are changing 2D or #d extents, then you go look in another view and it seems like they are "jumping".
Maybe review some of the topic in this topic cluster of the help to try and get your grids back to behaving correctly as you want them.
http://help.autodesk.com/view/RVT/2020/ENU/?guid=GUID-4E36EDA0-2F4E-4619-B568-AC758E8D9770
What is meant by grip edit?
Do you mean just pull them back within the crop region?
Thing is the crop regions are different on every sheet- should the crop region on one sheet affect the gridlines (2d) on another sheet?
I have been pulling them within the crop region, they still seem to move.
Also this doesn't address the issues that hiding and showing the view on the exterior of the crop region moves the gridlines.
Moreover when I crop the gridlines and check to hide annotations in PP, some gridlines hide and others stay visible.
- Also wondering why this feature exists in the first place. Crop regions and gridlines often have to move independently of each other, especially on a tight sheet. Also gridlines already move easily as a unit. What's the point of this feature?
Have you tried utilizing the separate annotation crop region to get what you want?
Still waiting on examples.
@jfjacques wrote:
What is meant by grip edit?
Select a grid, and then use the blue dot on the end to re-position it. Click and drag.
Do you mean just pull them back within the crop region?
No see above. Move them independent of the crop region
Thing is the crop regions are different on every sheet- should the crop region on one sheet affect the gridlines (2d) on another sheet?
No. But not every grid may be set to 2D on every view. That is what i suspect is the problem. you have some that are 3D (moving in every view) and others in 2D.
I have been pulling them within the crop region, they still seem to move.
Sounds like you are adjusting the 3D extents.
Also this doesn't address the issues that hiding and showing the view on the exterior of the crop region moves the gridlines.
That is turning the crop on and off. Yes this would change the position of the grid line end. If the crop was pulled in past the 3D extents of the grid, it will automatically "trim" it to the crop edge. When you turn off cropping the grid will return to it's 3D extents.
Moreover when I crop the gridlines and check to hide annotations in PP, some gridlines hide and others stay visible.
??????
- Also wondering why this feature exists in the first place. Crop regions and gridlines often have to move independently of each other, especially on a tight sheet. Also gridlines already move easily as a unit. What's the point of this feature?
The feature is there to automatically "trim" gridlines when you crop a view, otherwise you would need to touch every grid every time. with automatic trimming, that may not necessarily be required every time.
I would again suggest looking over the topics in the section of the help on datum extents and visibility. http://help.autodesk.com/view/RVT/2020/ENU/?guid=GUID-4E36EDA0-2F4E-4619-B568-AC758E8D9770
Lots of good information there and would probably answer a lot of these questions.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.