Not sure if this is a temporary flaw. Hopefully it is.
But at the moment I recommend Revit 2018 users to use the IFC for Revit 2018 v18.2.0 version. Because the last 2 versions give unexpected errors and related missing geometry. Just a quick test is attached. As you can see the exporter is too picky. And is not using the options it has .
I expect the exporter to find the best possible solution while exporting. And when there is none, that it could fall back on the Category mapping. Of course some warnings are really appreciated. But at the moment it simply fails. This is a step back.
We know there were some problems exporting with v18.3.0, which is why we released v18.3.1. This is a result of some major rewrites that had some quality issues. I see that there are R2017 and R2018 files above. Are these all tested with v18.3.1 export, what were the settings, etc.? We can try to reproduce locally.
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tested 3 versions. v18.3.1 (called _new) v18.2.0 (called _old) and v18.3.0
I exported some simple geometry and tried to map those in different ways by using Ifc Parameters . As you can see in the new attachment
I am having problems with Revit not exporting geometry while it obviously is able to export the geometry in the old v18.2.0 version.
I do appreciate warnings on export that’s nice for review.
But if the exporter is able to export a Floor to ifcCovering with the predefined type FLOORING, I am really surprised that I cannot use the normal IFC Parameters to say so, without corrupting the IFC file.
That is really my biggest problems, why I would prefer the old v18.2.0 version for now. I am more and more telling Revit what it should do in a specific way. That should not be the reason for a corrupt file.
Smaller suggestions are still.
It is strange to see that I cannot map a Generic Model to a specific Entity or Type in a way I choose. It is still Generic.
On the other hand I can map a Model in Place to almost anything. While a normal Category is limited. But oke, I can live with that. And it must be really hard to build a correct IFC based on a semi random input from Revit. So I should deal with that myself.
So I would expect the exporter to:
1. Check the Yes/No category mapping list for exported (sub)categories
1.1. If Yes, than check the ifc Parameters of an element for a Predefined Type in 2 ways.
Combined or separated definitions.
1.1.1. If the Type is possible than use it
1.1.2. If the Type is not possible, than check if the Entity of the Type is possible
1.1.2.1. If yes, than use it.
And perhaps give a warning – appreciated.
1.1.2.2. If not, than use that category mapping.
And give a warning – appreciated.
1.2. If No(t Exported), than skip the (part) of an element while exporting to IFC.
Not sure if this is a temporary flaw. Hopefully it is.
But at the moment I recommend Revit 2018 users to use the IFC for Revit 2018 v18.2.0 version. Because the last 2 versions give unexpected errors and related missing geometry. Just a quick test is attached. As you can see the exporter is too picky. And is not using the options it has .
I expect the exporter to find the best possible solution while exporting. And when there is none, that it could fall back on the Category mapping. Of course some warnings are really appreciated. But at the moment it simply fails. This is a step back.
Last edit: Teun 2018-03-05
Hi,
We know there were some problems exporting with v18.3.0, which is why we released v18.3.1. This is a result of some major rewrites that had some quality issues. I see that there are R2017 and R2018 files above. Are these all tested with v18.3.1 export, what were the settings, etc.? We can try to reproduce locally.
Regards,
Angel
Hi Angel,
I am not clear enough. So let me try again.
I tested 3 versions. v18.3.1 (called _new) v18.2.0 (called _old) and v18.3.0
I exported some simple geometry and tried to map those in different ways by using Ifc Parameters . As you can see in the new attachment
I am having problems with Revit not exporting geometry while it obviously is able to export the geometry in the old v18.2.0 version.
I do appreciate warnings on export that’s nice for review.
But if the exporter is able to export a Floor to ifcCovering with the predefined type FLOORING, I am really surprised that I cannot use the normal IFC Parameters to say so, without corrupting the IFC file.
That is really my biggest problems, why I would prefer the old v18.2.0 version for now. I am more and more telling Revit what it should do in a specific way. That should not be the reason for a corrupt file.
Smaller suggestions are still.
It is strange to see that I cannot map a Generic Model to a specific Entity or Type in a way I choose. It is still Generic.
On the other hand I can map a Model in Place to almost anything. While a normal Category is limited. But oke, I can live with that. And it must be really hard to build a correct IFC based on a semi random input from Revit. So I should deal with that myself.
So I would expect the exporter to:
1. Check the Yes/No category mapping list for exported (sub)categories
1.1. If Yes, than check the ifc Parameters of an element for a Predefined Type in 2 ways.
Combined or separated definitions.
1.1.1. If the Type is possible than use it
1.1.2. If the Type is not possible, than check if the Entity of the Type is possible
1.1.2.1. If yes, than use it.
And perhaps give a warning – appreciated.
1.1.2.2. If not, than use that category mapping.
And give a warning – appreciated.
1.2. If No(t Exported), than skip the (part) of an element while exporting to IFC.
Regards,
Teun.
I tested this case today with IFC exporter 18.4.0.0. and the exporter works again as expected.
Really happy. Thanks.
Teun.