View Range demystified!

[JamesVan]

Based on reading the following thread, http://forums.augi.com/showthread.php?t=7013, I was inspired to create a graphic example to help me and my colleagues get a better grasp on the View Range concepts. I have posted the graphic explanation as well as an example to this post.

[beegee]

Nice graphics James. Just what visually orientated people need !

[Scott Hopkins]

Helpful diagram - Thanks James

[juggergnat]

Nice graphic. But one thing that was never clear to me is the role that the TOP of the view range is for. How does the TOP range affect the visibility of elements above the cut plane?

One classic Revit conundrum, I want to show the roof lines of an eave above on an architectural plan. Maybe I want to show soffits or other elements that really should be on the floor plan if they have an aesthetic or spatial value. Underlay doesn't work because the view properties of a normal plan do not allow you to underlay a reflected ceiling plan. I've wrestled with this many times, anyone figured it out? The only way I have found to do this is to draw model lines on a roof plan with the level set to the floor plan, but this creates a pain because the model lines start showing up everywhere in other views because they are 3d objects. You can create a workset, etc...but the workaround goes on and on.

JG

[Scott D Davis]

Underlay the roof plan, use the linework tool set to Overhead line type, pick the eave lines, (no locking necessary!) then turn off the underlay....now if the eave line changes, the overhead lines move accordingly.

[Scott D Davis]

james,

I'm hopeful a graphical interface much like you've shown will soon be included in Revit, where the user can adjust the settings by moving the graphic lines.

Nice explanation!

[sfaust]

in answer to the question about the top range, it is my understanding that this only affects ceiling plans, not floor plans...

[beegee]

.... one thing that was never clear to me is the role that the TOP of the view range is for. How does the TOP range affect the visibility of elements above the cut plane?

Yes, the Top Clip Plane is used for RCP views, defining the primary range extent.

There are a few categories for which an object located above the Cut Plane (but partially below the Top Clip) is shown in normal plan.
These categories include Windows, Casework, and Generic Models. These objects are shown as viewed from above.

[jamie.casile80054]

Hi,
So, just as clarification, in a floor plan, the Top value in the Primary Range is irrelevant and has no effect on the view? (as long as it is above the cut plane, its fine?)
thanks,
jamie

[rjcrowther]

That makes a lot of sense to me. Don't suppose you could somehow wind up on the Revit User Manual team and fix up some of the other items that are difficult to comprehend.

Rob

[cphubb]

Yes, the Top Clip Plane is used for RCP views, defining the primary range extent.

There are a few categories for which an object located above the Cut Plane (but partially below the Top Clip) is shown in normal plan.
These categories include Windows, Casework, and Generic Models. These objects are shown as viewed from above.

Actually any item where the user uses the <above> Object Style for Symbolic Lines, and the item does not intersect the Cut plane will show on the floor plan as <above> but as beegee noted viewed from above.

[sjsl]

What we really need is just a simple slider control (that is live of course) so you don't have think about is it 1" above or below or some other esoteric dimension that is going to get an error. "I'm sorry you are so stupid you can't figure the View Range out good luck now!"

[CGM]

That makes a lot of sense to me. Don't suppose you could somehow wind up on the Revit User Manual team and fix up some of the other items that are difficult to comprehend.

RobG'day Rob,
I agree with that, at the same time we could pass on this link -

Welcome to Plain English Campaign (http://www.plainenglish.co.uk/); they've been campaigning against gobbledygook 'n jargon since 1979. This article in particular made me smile:
IT departments are the worst, say human resources
Human resources staff have singled out IT departments as being the most difficult to communicate with.
They say that IT staff have complex ways of working and spout gobbledygook, which alienates other staff and causes 'departmental feuds', according to a study by software company Sage. Acronyms, jargon and complex procedural documents are more prolific in IT than in any other department.

An organisation's marketers seem less involved in internal squabbles, but when asked they, like human resources, rated the IT department as the likeliest cause of tension.
"Competition has always existed between departments in the business world, and different parts of the business will tend to use different terminology and language," said David Pinches of Sage.

"However, as customers demand more, and business operations are required to become 'slicker', it will become increasingly important for the company and its various departments to communicate more effectively between one another." Excuse the interruption; but the lack of effective communication in CAD / IT does niggle me alot. :Oops:

[rjcrowther]

Thats an impressive piece of gobbledygook you found there. Next time I have had a rather 'frothy' evening I will have another look at it and perhaps it will make some sort of sense then.

[Alex Page]

Actually any item where the user uses the <above> Object Style for Symbolic Lines, and the item does not intersect the Cut plane will show on the floor plan as <above> but as beegee noted viewed from above.

Could you explain this a bit clearer - Im not quite sure what you mean!

[DaveP]

There's an excellent explanation in Chapter 3 of Introducing Revit Architecture 200? by Eddy Krygiel. Greg Demchak, and Tatjana Dzambazova. With pictures!

I'd highly recommend buying both this book and Mastering Revit Architecture.

Or at least go to Barnes & Nobel and read chapter 3

[cjneedham]

One of those things I never thought I'd get around to was to nut out how the view range applies to Reflected Ceiling Plans ... once and for all. Taking James' illustration as a starting point, I took the plunge. I had heard some say that using levels to define the position of ceilings was good for RCPs, since you can set your cut plane relative to the ceiling level. While I do think this is a good idea, ultimately it makes no difference to how view range works. I hope the attached illustration helps clear it up for some.

[ws]

Brilliant Chris - thanks very much :beer:

I've always struggled with this but at last I've 'got it' thanks to your diagrams - particularly the reflected ceiling plan one.

[ejburrell67787]

Thanks indeed James and Chris. Visual explanations work wonders!

[xiqx]

Nice pdf!

Just a question why don't you use regular floorplans with the cutplane above the ceiling? Because of the lighting fixtures?

Revit structure has the ability to look upwards would that work for your ceiling plans?

[cjneedham]

why don't you use regular floorplans with the cutplane above the ceiling?

Mostly, I would say because in architecture, they are referred to as 'Reflected' Ceiling Plans, hence looking upwards, not downwards. But thanks for the tip re Revit Structure!

[bulletproofdesign]

Any of you who use section tools realise that the section cuts at the line and you see what lies beyond until you reach the extent of your 'far clip offset'.

In Revit Architecture, a Plan view isn't a 2D plan view. It is in effect a horizontal section, except it has 2 'clip planes' one in front and one behind.

To see exactly what lies in your plan view, open a generic 3D view. right click the 'view cube' ->orient to view->Floor Plans->Ground Floor (where 'Ground Floor' is the floor you want) and voila, revit will change the visibility graphics to 'Ground Floor' settings and locate a 'SectionBox' with 'Ground Floor' crop region as the sides and 'Top' and 'Bottom' view planes as the top and bottom. This will show you what 'Floor Plan' is actuclly showing.

Very helpful Graphic by the way! clearly shows what seems confusing for months... :D