i tri to export steel plates as ifc with dynamo script. but the steel plates are not visible when i check it. the picture below show the script that i have made, i’am also using the packages Genius loci for the export ifc.
In the first instance I would suggest you check your IFC mapping settings to make sure they are set correctly in accordance with the IFCSchema as they can sometimes be auto set to not export. Plus also make sure the view is set to fine view with all relevant info is visible.
This is the area for changing the IFC mapping - Help
the settings for export i already fill it in, otherwise it will not work manually. but the thing is that manually it goes rigth but if i will try it with script it didn’t work. in later version of revit the script works.
It’s because the node has a lot of settings hardcoded. So whatever you check in your ifc settings wont matter. You are feeding your settings into the user defined property sets, it’s not the same thing.
Upgrade to a supported build. You are missing 2.5 YEARS of security patches and as a result everyone who works on the job is at increased risk of an infosec incident.
There is a reason that AEC firms are always around the top of the lists of ‘industries impacted by ransomware’ and such. And it has nothing to do with the potential profits a malicious actor can get as impacted firms are small targets in terms of revenue, nor does it become a point of pride for the malicious actor like if they hacked the FBI directly… It has everything to do with the lack of installed updates an continuous reuse of legacy software.
Thanks to the subscription model there is no longer any valid reason to keep with the old version. And if someone on the team (like a GC, primary contract holder, or owner) is saying ‘no’ they should pick up the cybersecurity insurance premium for all companies over the duration of the project’s use of unsupported software.
i understand that Jacob, but these projects are started at 2019 and they still working with project. so the upgrade could be giving problems for the projects
That simply isn’t true for any build with a 2 as the 3rd digit,a nd has only been true for one build in the last 20 years (upgrades from pre-2017). Heck many projects can even take advantage of ‘upgrade in cloud’ feature these days and no one even has to open a model to get things updated. For most projects the new software installation is more time consuming, and that needs to happen for each user anyway as someday they will be on a project using the new release. Just tell the team ‘pencils down’ on Friday at noon; then take an archive of everything; then do the upgrade and call it a day.
Note that I don’t say this for any benefit to me - i don’t get a boost in any awy if you do or don’t upgrade. Instead I speak as I don’t want to see people go though what I have seen others struggle with. I know a half dozen different firms who lost a lot more than a single technician’s afternoon to do the upgrade (or less) due to ransomware events. Imagine if everyone in every company working on the project could only use their phone and the data stored local to it for an undisclosed time period. That is what you’re risking by not doing the upgrades to Revit and every other tool in your ecosystem.