Crop region resets after jogging section / elevation

[Anonymous]

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

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

Like this:

AAAGGGGGHHH!!! It Reset My crop!!

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.

[john.vellek]

Hi @Anonymous,

This seems a bit frustrating.  When I do this in my model it behaves as expected. (working in 2017). Can you attach the portion of your model affected so I can take a look for you?

[Anonymous]

Hi John,

Thanks for taking a look at this 🙂

The 'Geometry' Model is linked into the 'Annotation' model. This is what we do when we have multiple projects over many years at the same (large) facility.

The models have been stripped down for security, but the error still occurs.

[john.vellek]

Hi @Anonymous,

Unfortunately, there are only two walls on the plan so I am not sure if this is really enough to play with. I added a couple including a low wall to the bottom side.  I split the elevation and show you it in capture1 and the elevation capture1e.  The elevation to me looks as expected.

  

then I moved the split segment (shown in captrue2) to the right beyond the low wall I put in. Again, the elevation (capture2e) looks correct to me.

  

It does not appear that you are able to do it in the same fashion.  Perhaps it has to do with the crop window around the elevation. Have you tried resizing it to see if it is cropping too much?

[Anonymous]

Hi @john.vellek

I'm not sure why you're not able to recreate the error. My colleagues are.

- Which version of Revit are you using? I'm using 2016.

- Is the elevation you're working with in the geometry model or the annotation model?

- It looks like the bottom of the crop region in Capture 2e has been cropped out of the screenshot. are you sure that the crop region isn't moving?

Without modifying any geometry, here's what I've done...

Open the 'Annotation' Model. and go to the Fourth Floor Plan:

The elevation, which is already drawn, should look like this:

After jogging, the elevation, the plan looks like this:

and the elevation looks like this:

   

[john.vellek]

HI @Anonymous, I was working in 2016 and in the Geometry model. The crop region gets very long (vertically on the screen) when I adjust the split.  Although when I adjust crop region it in the elevation it all looks good. I can close the view of the elevation and then reopen it and it stays put.

I have included my model so you can see if anything looks different than yours but all I did was to had my walls, then the split.

Please update your post after you take a look at it.

[Anonymous]

Hi @john.vellek

If the crop region gets very long, then you've accurately reproduced the error.

Yes, I've been shrinking the crop region back down every time I adjust the split, but that has become incredibly time consuming.

I'd like to know if anyone out there has an idea about how to prevent the error in the first place, or why this might be happening so that our Revit people can begin working on a solution.

Thanks 🙂

[Anonymous]

I was able to duplicate the issue as well..   Looks like the crop region is resetting to the 0' or 100' default level, as the current levels are over 1000'.

I noticed you are using Project Base Point for actual elevations instead of using the Survey Point.  I think that is most likely your culprit.  Most models are built around the 100' mark, but changing Levels to Survey Point allows for actual elevations.

[john.vellek]

HI @Anonymous,

I think that @Anonymous is on to something here. Can you try changing your base point to see if it corrects the problem for you?

[Anonymous]

@Anonymous

I believe this might have something to do with it, especially since the depth of the crop region seems to correlate with the elevation.

Let me look at it when I get a break and I'll send an update.

[chrisplyler]

I can understand why the crop regions of elevations and section views might default to the full height of the model when first created, but once you adjust the height to where you want it, it ought to hold those height settings no matter what other changes you make to it.

[Anonymous]

OK.... So I realized that part of the problem was that there was redundancy in the elevation of the model elements. The Survey point was at 0', the project base point was at 1133.07', and Level 1 was at 2266.14'!

I reset everything to 0 and the problem persists. Not as drastic, but still unacceptable.

Furthermore when Level 1 is at the Project base point, the Level tag will only read correctly under the following conditions:

• Project base point = 1133.07
• Survey point = 0
• Tag set to read survey point

I set the project base point to 1133.07 in both models. The level tag reads correctly, and the crop region behaves identically to when the project base is at 0.

Thoughts?

[john.vellek]

Hi @Anonymous,

I created a section, displayed hidden elements and moved the project base point and survey base point to the first level. The height on the first level now reads 0.0

When I create an elevation it is now showing the crop region to the first level.

Is this not what you are seeing?

[Anonymous]

Hi @john.vellek

The problem persists nearly exactly as it did before.

Here's a new section:

... then I crop the section to the floor for which it was created...

Then I split it...

...now it has reset to someplace below project zero...

Splitting a section should never affect the crop region.

*EDIT

I should add that project zero in the images above is at 1133.07', but the behavior is identical when project zero is at 0'.

[john.vellek]

Hi @Anonymous,

Does your first level indicate a height of 0'-0"?

[Anonymous]

Yes, when the project base point is at 0', the Level 1 tag reads 0'-0".

It doesn't show that way in the screenshot because at the time I took it, the project base point was at 1133.07', however, the crop region behaves the same.

[john.vellek · Accepted solution]

Hi @Anonymous, Sorry for the delay in getting back to you.

When you create the split, it is not actually modifying the existing elevation view but replacing it with a new one which is why the Crop Region goes back to the default of showing all levels.

I suppose it would be worth exploring making each level its own unique model that is linked into a master one. If you placed the elevation on the unique single level model it would be interesting to see if it shows the crop region for just the one level - I believe it should.

[Anonymous]

@john.vellek

Thanks for your response. No worries on time. I've been dealing with this issue since 2014, so a couple of days aren't going to hurt anybody. I'm just grateful for the input.

A split creates a new view, huh? That's very interesting. So in theory, if I get Revit to create views at the proper elevationin the first place, this problem would subside?

I'll accept this as a solution for now and continue to investigate.

Thanks all for your input.

'till next time...

[john.vellek]

Hi @Anonymous,

In MY experience, when I change an elevation by splitting I have lost any drafting lines I have applied so yes, I think it is basically just replacing your current view. I am not the programmer so I could be wrong but I think it explains why it always jumps back to the default crop region. It has always done this for me.

Have a good weekend!

[Anonymous]

Actually, revit is not creating a new section/elevation when we adjust the split line, because we don't lose any of the anotations (as someone told before).

So therefore there's no reason for the aparently reset of the bottom of the crop view line.

I wish they could fix thsi problem for good, because is very time consuming.