Crop region resets after jogging section / elevation

Crop region resets after jogging section / elevation

Anonymous
Not applicable
6,782 Views
23 Replies
Message 1 of 24

Crop region resets after jogging section / elevation

Anonymous
Not applicable

I start out with a section or elevation that looks like this....Elevation 001.JPG

 

...but I want to see the corner window return, so I use 'Split segment' to jog the view.

Like this:

Plan.JPG

 

AAAGGGGGHHH!!! It Reset My crop!!

Elevation 002.JPG

 

Anybody know why this happens?

 

Things tried:

  • Updating Revit
  • Rolling back Revit
  • I Deleted the crop boundary and manually drew my own. This seemed to work graphically, but the viewport resets with the crop region, so it's not a functional workaround
  • I tried locking the crop region, but it locked the whole view, and I couldn't split it.

Smiley Sad

0 Likes
Accepted solutions (2)
6,783 Views
23 Replies
Replies (23)
Message 21 of 24

james.levieux
Advocate
Advocate

I am soooooooo tired of this obvious bug!   I'm working on a hotel in Sun Valley, Idaho that has a sea level set to 0 that puts the building 5000 feet above the survey/project point.  That's like DAYS of crops when you're drawing hotel guestrooms!

 

So, when you jog a cut-line, Revit creates a new view.  So if Revit is so smart that it can replace the annotation elements from the old view, why is it so dumb that it can't get the crop extents from the old view and use those same extents for the new view.

 

My view is that, if we must have some arbitrary default extents (for whatever arcane reason!), the extents should be at LEAST limited to the LEVELS that exist and not some data point 5000' feet below everything.

 

I'll post a link to this in Revit Ideas

 

jameslevieux_0-1701979445340.png

 

0 Likes
Message 22 of 24

james.levieux
Advocate
Advocate

Sorry,  I didn't mean to say I solved this horrible mess!  I was looking for a way to refer to my particular post and I used the "permalink" thing.  It doesn't appear to work for that purpose.  Does anyone know what permalink is for?

jameslevieux_0-1701980089309.png

 

 

0 Likes
Message 23 of 24

james.levieux
Advocate
Advocate

....and minutes later, I've found that I'm entirely incorrect.  The default extents do appear to be limited to the extents of the levels in the project.  I'm working in a model that contains the architect's linked model.  They have a physical level line at the 0' elevation in a workset that I had turned off.  

 

REVISED: the default view extents should be limited to the levels in the current model (and not include the linked model), and better yet, limited to the levels in currently loaded worksets.  

 

Imagine 2 check boxes:

 

When calculating the default view extents for sections and elevations:

  1. exclude levels in linked models.
  2. exclude levels in unloaded worksets.

 

 

 

0 Likes
Message 24 of 24

james.levieux
Advocate
Advocate
Accepted solution
0 Likes