Embedded window schedule in Room schedule

[Kimtaurus]

I would like to embed a window schedule into my room schedule. Unfortunatly the location point of a window lies in the wall, whereas my room reaches upto the wall face. As a result the windows do not show up in the embedded schedule. Anyway to resolve this? Without changing the Room Computation rules, as this also changes my other Room Schedules.

I already tried adapting my window-family, by moving the wall and window (you can't move the center of a calculation point). As you can see in the attached image: the center of the location point is placed on the interior side. Still no avail. I only get a window to show up if I put it completely inside the room; i.e. place a new wall inside the room and then place a window.

Note: our exterior walls are made up of 2 seperate walls: interior structural wall and the exterior facade (bricks and insulation). The windows are placed on the exterior wall.

[dzanta]

go into the window family...

turn on calculation point

select it

look at dead center of calculation point...click it

this flips the orientation of the calculation point

use it in your project

also, within the project, select the window and verify it is in the correct wall you want since you have a two-wall construction

try moving the window to the other wall as a test to see the behavior

[Kimtaurus]

I made a small test project: 4 walls: 3 standard wall and 1 two-wall. Wall construction doesn't seems to affect the way the RCP works.

So I've tried flipping the Room Calculation Point: it doesn't help. Also, this seems a strange procedure, since Revit has it set as a standard: interior-side is from:room and exterior-side is to:room. Which seems logical to me, so flipping the RCP doesn't make sense.

Oddly enough if I flip the window in the project exterior-interior, the window does show up in the schedule (see attached image). This is the case for both "walltypes". [BTW: the window I used in this test is a Revit library window, so there's nothing I've change which could affect the result].

This is even stranger, as this implies I (and Revit) would have to change the way all our windows are modelled.

[Kimtaurus]

Has anyone else experienced this? Or does someone know the solution.

[VanderwesthuizenJ]

Yes I am with you on that.

I created a new window family. But before I modelled any new window I changed all exterior to interior and vice versa i.e. I flipped the wall, I renamed the reference plains, I even renamed the family view names exterior to interior etc. I moved the flip arrow controls to the “new exterior side”. I then made sure that my Room Calculation Point arrows flow from my new interior side to the new exterior side.

After I loaded then window family into a project I found that everything worked as it was supposed to. So I also think Autodesk made an error here. The conflict happens between Revit’s From Room or Control Point and the Family’s Exterior Location computation within a Project.

How do we fix existing window families without a hassle

How does an exterior window appear in schedules without having rooms on both sides of an exterior wall? Think about that…

Anyone with an answer to the problem?

[Anonymous]

Has anyone found a solution to this problem? I am trying to do the same thing and having the same problem. Remodeling all our windows will be prohibitively time-consuming, and since they're all facing the "correct" direction according to the template, I'm hoping there is a solution. 

[ToanDN]

Edit:  I reread the problem and I think I misunderstood it when I typed the answer.  So please ignore what I show below.

_______________________________________________________________________________

There is no need to fix the window families.  It happened because some windows were placed pointing to the wrong side the 1st time.  They were then flipped to the correct side but the From Room/To Room did not change accordingly (bad Revit).  You simply just need to open a window schedule and change them yourself.

[DmetcalfGHY4B]

This is patently annoying occurrence that needs to be re-mediated going into every family and editing them to fix this issue isn't an option. I haven't any real need for this approach but users are not well served when these occur when adopting BIM workflows.

[DmetcalfGHY4B]

This is patently annoying occurrence that needs to be re-mediated. Going into every family and editing them to fix this issue isn't an option. I haven't any real need for this approach but users are not well served when these occur when adopting BIM workflows.