Cannot export crop view from a 3D view

[Anonymous]

Who was the brain behind this brilliance?

When exporting a file with large extents to DWG from Revit, you always get this error:

View boundaries too large to export

So you add a small crop boundary to the view and turn it on:

Add crop and show boundary.

You then run the export again and Revit gives you this error:

Crop boundary will be ignored

So you hit 'Cancel' and the export proceeds, ignoring the crop and exporting the entire view, which is what I originally wanted in the first place! WTF?!?!?

[RobDraw]

Good luck.

[barthbradley]

@Anonymous: What about using a section box? For 3D views, crop region boundaries are not exported, so you cannot use crop regions to limit model geometry. Instead, use section boxes. 

[ToanDN]

So it was too large at first, then you made it smaller to accommodate, then it turned out "too large" is not too large anymore?  Sound utterly normal to me.   

[Anonymous]

I'm not trying to limit the geometry at all! I want the entire extents of the file, but HAVE to create a crop, then ignore it, to export the entire extents. Why can I not export the entire extents without doing the unnecessary steps of adding a crop and then ignoring it. THAT's my point...Stupidity! (Thanks for the mod changing my subject for clarity, but you did not, obviously!)

[Anonymous]

LOL!!!!!

[Anonymous]

Also, why does the original dialog say the warning "can be ignored", but I CANNOT ignore it and get my export....Instead, I have to jump through the crop/ignore crop hoop?

[barthbradley]

I give up. Why? 

[RobDraw]

I think this is just another case of Revit using the same term to mean different things.

The "boundary" in the first message has a different meaning because there is no crop applied. That boundary may be way beyond the extents of the objects in the model. (No crop, no extents)

The "boundary" in the second message actually refers to the extents, or applied extents. It won't export a representation of that crop. (Crop, extents)

So, not unlike in the English language, the same word can mean more than one thing.

[Viveka_CD]

Hi @Anonymous

Thanks for sharing the screenshots and pointing out this error.

I'm trying to verify with the team if this is a limitation in 3D view, meanwhile, can you share your file and journal to investigate further?

I can send you the private folder to upload.

Looking forward to your reply update.

Regards,

[Anonymous]

It's not my file to share, unfortunately, but this happens on any project with larger extents than just single buildings (i.e. contains part of a site area surrounding a building).

[Viveka_CD]

@Anonymous no problem if you unable to share the file.

Is the site created in Revit? Also, specify which version you sue.

[Anonymous]

Site is created in Revit (topo surface) and I am using version 2017, but this happens in all earlier versions as far as I can remember. Basically, it seems there is some random boundary extents that Revit doesn't like when you try to export, and then you apply a crop to wrangle that number in, which it then ignores and exports all of the data anyway. Go figure!?!

Here's a diagram of attempts to find the magic size of the crop that would allow export.

Crop compare.

And here is what I get when I import into 3DS Max (The entire extents):

Entire extents - What I wanted! 🙂

[Viveka_CD · Accepted solution]

Hi @Anonymous

I see what you are saying. 

Thanks for sharing the screenshots. I'll log this information with the specific team.

The product team will review this and investigate further for a resolution. I'll keep you posted for updates.

Regards,

[VenB]

It shows solution. I don't see any solutions of the issue here. Thanks.