While I was checking the changes with exporting Curtain Walls, I discovered something I haven't seen before. A Revit Curtain Wall embedded as a 'panel' in a different Curtain Wall was not being exported at all. I have been using this in projects to have a better control over the position of horizontal and vertical mullions in projects. In Revit 2014 it still works but it doesn't seem to work with the newest and the older version of the exporter for Revit 2015 and 2016.
Beside this, a Shared Door Panel still has no relation with the Curtain Wall as a whole.
Could you include a simple example of what you are trying to do? I am fairly sure we didn't take into account the case of a curtain wall embedded as a panel inside another curtain wall, so I could imagine that it would arbitrarily work or not work. I'll also forward this to other members of the Revit team as an interesting workflow.
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Jakub,
I encoutered the same problem again a few weeks ago and build a small Dynamo script to copy paste the nested Curtain Walls in the same place. Wich was sufficient enough for that project.
I was not able to change the 'nested Curtain Wall Panel' to an Empty System Panel, and stopped working on that part. But I did copy the ID's to clipboard, so I can use 'select by ID' in Revit and change those panels to Empty System Panel in Revit.
I also stopped because they wanted to check everything wich is a good thing. Some coppied Curtain Walls flipped and had to be flipped back. And I am also not completly sure what will happen with multiple times nested curtain walls. You'll have to change all the nested Curtain Panels to empty Curtain Panels by hand and then run the script again.
So use with care, but perhaps it will help a little for the moment.
You need the packages: Clockwork, Archi-lab_Grimshaw, Rhythm, Springs, Beaker.
Hi Angel,
The simplest form of this issue is in the file attached.
Desctiption:
I created a Curtain Wall (Curtain Wall 1). It has no rules just some manually placed grid lines.
I chose 3 of the System Panels on Curtain Wall 1 and changed them to Custain Wall 2.
We end up with Curtain Walls (Curtain Wall 2) acting as Panels in Curtain Wall 1.
So we have 9 curtain panels in total residing in Curtain Wall 1.
6 of them are System Panels (exporting fine).
3 of them are Curtain Wall 2 (not exporting).
See the attached picture for results.
Aha, with a refreshed mind I remember that this is a limitation of the agreements for IFC Implementation across companies. We are not allowed to have nested containers. So we have to turn all nested sub-components to be part of the original.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So what does that mean for us workflow wise? Are we forced to get nested containers (Curtain Walls acting as Curtain Panels) out of master Curtain Wall?
Would be great if we had an option to "flatten nesting uppon export" like we have "split by level uppon export". Do you see that possible?
So we might save some powerful workflow for us in Revit and still share pretty "flat container structure" in IFC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In so many cases this kind of nesting is just a handy tool for achitects to achieve design goals and control geometry. This nesting has value for an achitect in design process and really a value (relevant information) to drag all the way to IFC for sharing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If they are not exporting at all, that's a bug. We'll verify that, although I suspect that is fixed in 2018 (I'll have Andy Parrella chime in on that). So there shouldn't need to be an extra option to flatten it - that shoudl just happen (which is still sub-optimal compared to nested components, but that's where we are today with IFC.)
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the new update.
While I was checking the changes with exporting Curtain Walls, I discovered something I haven't seen before. A Revit Curtain Wall embedded as a 'panel' in a different Curtain Wall was not being exported at all. I have been using this in projects to have a better control over the position of horizontal and vertical mullions in projects. In Revit 2014 it still works but it doesn't seem to work with the newest and the older version of the exporter for Revit 2015 and 2016.
Beside this, a Shared Door Panel still has no relation with the Curtain Wall as a whole.
Last edit: Teun 2015-11-25
Hi,
Could you include a simple example of what you are trying to do? I am fairly sure we didn't take into account the case of a curtain wall embedded as a panel inside another curtain wall, so I could imagine that it would arbitrarily work or not work. I'll also forward this to other members of the Revit team as an interesting workflow.
Regards,
Angel
Hi,
I build a sample file for you. Based on the out of the box template.
Regards,
Teun.
We've had other requests for this behavior, so I have added these example files to that issue.
Thanks for the reply.
We would love to see this strange behavior being fixed. Just as it still is working in R14.
Any news on this topic?
I have been asked questions why Revit didn't export Curtain Walls from Revit.
It seems like the same problem.
We'll take another look and verify.
I can verify it - we have an issue filed. Angel I'll send you the info.
Hi, how is that going with this issue?
Im using exporter 16.6.0.0. and the problem still persists.
We really like Revit's ability to embed curtain walls (like panel) within curtain walls. Its very handy to control more sophisticated rythms.
I desperately need a fix for that.
Hmm, I thought that was fixed. Send us a trivial example so we can verify (perhaps you have a slightly different workflow).
Jakub,
I encoutered the same problem again a few weeks ago and build a small Dynamo script to copy paste the nested Curtain Walls in the same place. Wich was sufficient enough for that project.
I was not able to change the 'nested Curtain Wall Panel' to an Empty System Panel, and stopped working on that part. But I did copy the ID's to clipboard, so I can use 'select by ID' in Revit and change those panels to Empty System Panel in Revit.
I also stopped because they wanted to check everything wich is a good thing. Some coppied Curtain Walls flipped and had to be flipped back. And I am also not completly sure what will happen with multiple times nested curtain walls. You'll have to change all the nested Curtain Panels to empty Curtain Panels by hand and then run the script again.
So use with care, but perhaps it will help a little for the moment.
You need the packages: Clockwork, Archi-lab_Grimshaw, Rhythm, Springs, Beaker.
Hi Angel,
The simplest form of this issue is in the file attached.
Desctiption:
I created a Curtain Wall (Curtain Wall 1). It has no rules just some manually placed grid lines.
I chose 3 of the System Panels on Curtain Wall 1 and changed them to Custain Wall 2.
We end up with Curtain Walls (Curtain Wall 2) acting as Panels in Curtain Wall 1.
So we have 9 curtain panels in total residing in Curtain Wall 1.
6 of them are System Panels (exporting fine).
3 of them are Curtain Wall 2 (not exporting).
See the attached picture for results.
Last edit: Jakub Manek 2017-09-18
Aha, with a refreshed mind I remember that this is a limitation of the agreements for IFC Implementation across companies. We are not allowed to have nested containers. So we have to turn all nested sub-components to be part of the original.
Thank you Angel,
So what does that mean for us workflow wise? Are we forced to get nested containers (Curtain Walls acting as Curtain Panels) out of master Curtain Wall?
Would be great if we had an option to "flatten nesting uppon export" like we have "split by level uppon export". Do you see that possible?
So we might save some powerful workflow for us in Revit and still share pretty "flat container structure" in IFC.
In so many cases this kind of nesting is just a handy tool for achitects to achieve design goals and control geometry. This nesting has value for an achitect in design process and really a value (relevant information) to drag all the way to IFC for sharing.
Hi Jakub,
If they are not exporting at all, that's a bug. We'll verify that, although I suspect that is fixed in 2018 (I'll have Andy Parrella chime in on that). So there shouldn't need to be an extra option to flatten it - that shoudl just happen (which is still sub-optimal compared to nested components, but that's where we are today with IFC.)
Regards,
Angel
Hi -
Yes, this is fixed in 2018, everything exports. It is one curtain wall.
( Should I answser the question four times? :) )
Andy
Angel, Andy,
Thats exciting news, I'll give Revit 2018 a try ASAP then. I'll write you back if it works for us. :)