Activity for Andy Parrella
-
Andy Parrella posted a comment on discussion General Discussion
Is this posted over at GitHub? We don't check this forum as much any more. However I have created item REVIT-199478 to see how we can make this happen. Thanks and sorry for the... four year delay :(
-
Hi - I added instance parameters for each of the panels - now this exports window panel properties like this:: IFCWINDOWPANELPROPERTIES('2UTuR2wjH3Tvyv4oLd0su$',#42,'30_WI_drievoudigraam_TVA:3000x2134:15917:1',$,.TILTANDTURNLEFTHAND.,.NOTDEFINED.,$,$,$);
-
Hi - I added instance parameters for each of the panels - now this exports window panel properties like this:: IFCWINDOWPANELPROPERTIES('2UTuR2wjH3Tvyv4oLd0su$',#42,'30_WI_drievoudigraam_TVA:3000x2134:15917:1',$,.TILTANDTURNLEFTHAND.,.NOTDEFINED.,$,$,$);
-
Hi Joao, sorry for the delay. If you still have it, could you send a simple model with the door/window family? I want to make sure I reproduce it accurately. Thanks.
-
I do see Phase Demolished exported when I export Revit Property Sets. It goes under a group "Phasing." If the element is not demolished in any phase, then the parameter will be empty and does not get exported. If you need this parameter for all elements you could make some far future phase and call it "Never"
-
OK I see some geometry that is coming out invalid in Revit (the letters N,S,E,W) So a woraround might be that since it appears this is an imported marker, what if you used a different one? Or open it in the original app that created it and resave it.
-
Hello. Yes, I can reproduce this in the latest version of Revit. There are a bunch of debug warnings on opening your model, so that's a clue. I will file an item to fix. Andy
-
Hello An, Actually one of the developers says this is possible in this way: assign the desired level name to parameter IfcSpatialContainer. This can also be used to assign the container to "IFCSITE" and "IFCBUILDING". IfcSite can be useful to assign IfcSite as container to objects outside the buildings (e.g. on the site). SO the valid values are: "IFCSITE", "IFCBUILDING", or any Level name (e.g. "Level 1", "Level 2")
-
Hello An, It's true, Revit exports to the first level of an elevation that it comes to. One thing you might be able to do is to add a shared parameter to the elements referring to the "proper" level name, export to IFC and then use those parameter values to sort them out on the receiving application. Andy
-
The geometry in that image looks very strange. Is the geometry very far from the origin (like, >20km?) That can cause big problems in Revit. You might have to move the geometry closer to the origin and then export again.
-
Sorry it is taking a while to fix this. I hope to see more progress on IFC soon. One thing that may make it easier to align links to the proper place in Revit is that we now allow showing the internal origin of both the host and linked models.
-
Thanks. i can reproduce this and I will file an item to get it fixed.
-
I can reproduce this with a new model using 19.3, so there is something we need to fix. If you can use the previous exporter for now, please do.
-
Hi Ahmed. Sorry for the delay - as for these rooms, first off make sure you have the latest IFC open source exporter. (Since you are here you probably do.) I think many room issues are fixed in later versions of Revit, but if upgrading is not feasible, then you might be able to fix these rooms by adding room separation lines around the problematic rooms before export.
-
HI Alessandro - someone else reported this and I was able to reproduce it using their information. I found that somehow the exporter needs a newer version of some Newtonsoft files. Can you try this: unzip this Newtonsoft.Json.zip into your Revit 2017 Program directory? I find that this makes it work. Andy
-
I don't see the customer property set duplicated in your IFC file? It's only applied to the instance, as specified in your mapping file.
-
Hi Joao, I replied in GitHub.
-
after uninstalling the IFC apps, can you confirm that those directories are empty or gone? Also - Please start up Revit, wait until it is done and close Revit. Then find the journal created (C:\Users\<yourusername.\AppData\Local\Autodesk\Revit) during that session. Please send me that journal. It should show useful information about the problem. Thanks.
-
Hi Alessandro, I think you have the addin installed from the appstore and from Git/SourceForge. I think for a first try, uninstall both, and then install from either location.
-
Hi Joao, As Dirk said if you post a very simple file that shows the issue we'll take a look. Thanks!
-
It works for me...open the exporter, go to Modify Setup, choose the Import Setup icon and select the .json file for that configuration. Click Open, then OK and it should appear in your setup pulldown?
-
It wqorks for me...open the exporter, go to Modify Setup, choose the Import Setup icon and select the .json file for that configuration. Click Open, then OK and it should appear in your setup pulldown?
-
Hi, sorry about the delay, but that file seems to be gone from the server. could you upload it again? thanks. Andy
-
This would work if you could make only the demolished elements visible, then you could use IFC export of visible elements only. However we can't do that, so a filter could hide the non-demolished elements. Unfortunately the phase demolished parameter isn't available to filters, so here's a slightly involved thing you could try... add a shared parameter "demolished" to the walls category. Then populate the parameter with yes or no, either by hand in a schedule, or using a macro or dynamo script. Then...
-
Sure, please do.
-
Right, with a non-workshared model I can't export - we'll check it out.
-
Right, with a non-workshared model I can't export - we'll check it out.
-
Hi Matthew, that is really a huge model and it is likely that we are running out of space in our exporter. One thing you can do is to break the model up in to parts using filters to hide half of the elements (maybe all MEP elements) and export using the option Export only elements visible in view. Then reverse the filter and export the other elements. The two IFC files will be in the same geographic relation to each other.
-
I'll check it out, Mark. Did you make sure you have the latest open source for 2018? (is that a dumb question considering you're here?)
-
Okay: If I export a Revit model with a Revit link, while using that option, I will get two IFC files: One for the host model and one for the linked model. They will remember their proper locations relative to each other. If you have the same Revit model linked twice, you will get three IFC files. Host and two links. The last part means that if you link an IFC file and then export it again, you'll lose information because the linked IFC file as it appears in Revit is not as "smart" as the native Revit...
-
I see what you mean - we are exporting the subcategories when you have them turned off. This works for other categories - you can make a door slab not exported for example, and it won't go out. I will have to investigate, but I suspect it has something to do with the multiple overlapping geometries with different subcategories.
-
I see what you mean. In your IFC file there exists both a void wall and an openingelement in the window. However when I export your file from 2018 I get the proper (2017 like) behavior. I am using the 18.4 exporter and you seem to have the 18.3.1. Try updating that installer and see if that helps. https://apps.autodesk.com/RVT/en/Detail/Index?id=6193770166503453647&appLang=en&os=Win64
-
Thanks, Hannes - I can reproduce this. I think Revit is getting confused by the various cuts needed and I'll file and issue to look into it. A workaround that I checked is to edit the wall profile to cut out the area of the beam (rather than having Revit cut it automatically.) Then it exports properly. Andy
-
I see some changed IFCSTAIRFLIGHT GUIDs too here. So overall - all the changing GUIDs are at the group or type level. Edit: these elements don't change GUIDs when copied into a new model.
-
I see some changed IFCSTAIRFLIGHT GUIDs too here. So overall - all the changing GUIDs are at the group or type level.
-
I see some changed IFCSTAIRFLIGHT GUIDs too here.
-
None in these exports.
-
from newest code I don't see any changing GUIDs for railings in this model. We don't make types for railings.
-
When I export these categories from isolated models, the GUIDs do not cha nge. However from the customer's model I see the GUIDS for IFCCOVERINGTYPE changing although the one for IFCCOVERING stays the same. I haven't gone through the others yet.
-
This is a known issue (REVIT-130647) that is on the list to fix. I'll give it a nudge.
-
Hi Eddy, I can't open that .rar archive for some reason - maybe it got corrupted. Maybe you could attach it again? Also if you could include the .rvt that creates those IFCs it would help a lot. Thanks! Andy
-
Got it - I think that makes sense. Sorry it took so long to respond, it's been on my todo list for a while.
-
1.Github is where we are gradually moving, so I’d say create new threads over there. 2.I think that is in the plans, but if not I will add it.
-
Looks like you're right - I will let the dev know.
-
Seems like there might be some unit conversion stuff going on - i filed an issue to fix.
-
Angel, that's REVIT-135617
-
I don't see this happening in 2018 or later with a new file I created using out of the box windows. However I do see the issue using your file. It must be the window is created differently - we'll figure it out.
-
Eddy, what are the particulars of what doesn't work? I see basic elements getting their GUIDs and retaining them on re-export.
-
Got it, thanks. we'll check it out.
-
So it does work in IFC2x3? Or not there either?
-
Hi Steve, just to make sure - did you change the mapping as shown in the attached image? It can be very picky about spelling. I confirmed that grids export for me with the 19.1 exporter. Andy
-
Checking back in - looks like the issue at the top of this thread is fixed in the 18.4 exporter.
-
By the way with the newest exporter (18.4) the three elements in the first issue do export.
-
Thanks - this is reproducible for me. I will forward it for update.
-
This is the case with IFC 2x3 as well. Seems reasonable...
-
Closing and reopening the file will do it, but presumably you have done that.
-
I really haven't been able to see why - the fact is it works for me. Forcing a full regeneration might be the key.
-
Thanks.
-
Hi Jeroen, I will take a look. Could you send the RVT file so I can try it? Thanks.
-
Hi Jeroen, I will take a look.
-
I can reproduce that just by making a regular wall and an in-place slanted wall and placing windows in both. I'll file an item to investigate.
-
Hi Eben, This is something I've seen and we have a task to fix it - but unfortunately we haven't got to it yet. Andy
-
Hi Simon, I exported that file from Revit 2017.2 with the latest exporter and I can see what you are talking about. I also find that if I uninstall the exporter and use the out-of-the-box one, the materials are there for both. Maybe you can do that for now, and I will create a ticket to look into this. Thanks for bringing this to our attention.
-
Hi Simon – You’ll have to share that A360 folder with me before I can see it. Just invite andrew.parrella@autodesk.com thanks!
-
I can send you a link to upload the revit model if you would oblige. Do we have your email?
-
I can send you a link to upload the revit model if you would oblige.
-
Hi Simon, could you send us those IFC files? Also your sample Revit file. There is something we should look at. Thanks! Andy
-
I've already invited you through that email. It should be an empty folder so you can upload your file. Does that not work?
-
You can see the version of your exporter and UI in an exported IFC file: At the end of the FILE_NAME line.
-
Oh, I created a shared folder and it shows you as invited through your email here. XXXX@users.sourceforge.net> Is there a notification floating around somewhere? I will send the invitation again.
-
I have an issue filed to make Revit look for existing parameters becore creating the new ones, and use those if possible.
-
For these I am seeing the same output using IFC4DTV with 18.2 and 18.3...though I do see the inclusion of IfcInterceptor. what's different then?
-
For these I am seeing the same output using IFC4DTV with 18.2 and 18.3...though I do see the inclusion of IfcInterceptor.
-
For these I am seeing the same output using IFC4DTV with 18.2 and 18.3...though I do see the inclusion of IfcInterceptor.
-
I filed an item for this one. thanks.
-
I can reproduce this one using your model, but I cannot, if I create for instance a roof with a shaft cut in it. Also I cannot reproduce it with model text exported as a roof. I am using a slightly updated version of the exporter at the moment - that might be the reason. We may be able to release it before too long.
-
I can reproduce this one, very interesting.
-
I can confirm this in his files. It's only for 2018. Dirk, for now you should go back to the previous exporter version.
-
I sent you an invitation.
-
Wow, I can see it now. the slab with the plug in it exported with the color for concrete. Interesting that when I unjoin the plug from the slab, it is exported properly. I will file an issue to investigate. So it looks like some of these elements were imported, using Dynamo? I see render materials in there.
-
sorry Marie, we're not there yet.
-
Hi Owen- We have done a lot more recent code work for the linking case than for the open case, so it's not too surprising that there are differences in results. I'll PM you to get the IFC file so we can look at it for the Open case.
-
Nothing new to report.
-
I don't know - looking at that IFC file in Solibri shows three elements of one color and one (with two bodies) of another color? What am I misunderstanding...
-
I think it goes in C:\Program Files\Autodesk\Revit 2017, contrary to what I thought originally!
-
Ok, I got the model and I can reproduce the issue.
-
HI Mileta, It should export to IFC when you specify "Export Revit Property Sets.". That works for me. If you're still having problems, maybe attach a small file that shows the issue. thanks. Andy
-
Actually Eric, Can you try exporting the stair using the option allowing for "mixed" representations? Parts of the stair may be able to be exported as extrusions and would then get an axis and footprint.
-
I'll take a look, Eric. an Assembled Stair is also known as a Component Stair, as opposed to a sketch based stair.
-
Hi Bernardino, Are you exporting from a 3D view? Revit rooms are not visible in 3D by default, so you would have to export using the option to include rooms in 3D views. Andy
-
Hi Bernardino, Have you installed the alternate UI from the Autodesk Appstore? It's available here: https://apps.autodesk.com/RVT/en/Detail/Index?id=1049118595309324136
-
If it looks ok in Solibri it is probably ok. Navis has a setting to use what is essentially Revit's IFC engine - is that enabled?
-
Hi Marie, we investigated and it is something we need to implement. In the meantime columns can be surrounded by room separation lines. Andy
-
Hi - Yes, this is fixed in 2018, everything exports. It is one curtain wall. ( Should I answser the question four times? :) ) Andy
-
Hi Felix, IFC4 is still a pretty new format, and a lot of viewers don't support it completely. I find that if you link your IFC4 file back into Revit, it looks better, but not perfect. As for the 2x3 export, the 2x3 format is less sophisticated in dealing with the large warped surfaces of your roads, so it has to tessellate. Actally I had great success with your file using 2x3 and selecting extra low level of detail on export.
-
Hi Oliver, I'm on the team that created this -If you can send a test file and the journal showing it happening, maybe I can see what is going on. There may be something different about your setup that is causing it. I can send you an upload link Andy PS I'll send you an upload link if you need one.
-
Hi Oliver, I'm on the team that created this -If you can send a test file and the journal showing it happening, maybe I can see what is going on. There may be something different about your setup that is causing it. Andy
-
Okay, have you tried uninstalling the open source exporter and trying it? That would be a clue. Also - can you send me a journal from Revit where you just open Revit, open a blank project, try to export to IFC (and fail) and close Revit?
-
Yes, leave it on In-Session Setup.
1 >