Just started testing Revit 2020 for basic understanding and working with ifc format.
Concerned about testing on a project file that was opened without any problem in a minute from a third party converter specialized for realtime visualization, opening on Revit appear to be a painful process with it working for more than half an hour and after that stalling and needing to close it.
My hardware it's not so bad even if not specialized for CAD, with 6 core 3.8Ghz CPU, 32GB RAM, old 3GB VRAM non professional series GPU that was anyway not stressed during the process.
There is any specific setting I need to define for ifc file import?
I've also experienced very slow import speeds in 2020 (and 2019) - 7 hours to import a 5 level but fairly modest footprint hotel architectural, and save as RVT for upload to BIM360 - I note that on my i7-7820X 8-core workstation with 32GB of RAM, the IFC import add-on is only using a single CPU thread - there are 15 other CPU threads twiddling their digit(al)s. I'm very surprised that import add-ons aren't multi-thread aware considering the ginormity of some IFC models.
No more answers on this thread? Im having same issue. Very slow import/link speed with ifc to Revit
(Computer is top of the line)
Same problem here...
And we have 18 workstations that needs to import every week a number of IFC to be assembled info a federated model, and further working on it before publishing the finished assembly to the main contractor...
Several hours of import time, every week, for at least a dozen workstation... I let you doing the math...
Autodesk shouldn't be so surprised when we tell them we are looking for alternatives...
Working with revit and tekla.
Revit hours , Tekla minutes (or seconds).
It's not your computer it's the software...
About Tekla, you may be right, but unfortunately Tekla has other issues modeling the data for BIM purposes... and many clients want Revit file format as long as IFC...
It's a standard-de-facto nowadays... like dwg has become a few decades ago... a shame, but this is a fact.
many visions for this and as a revit user (+10yrs fulltime) and tekla 2 years i do not agree.
The data is very difficult to manage ( or you must have extreme clean rules between company's) in Revit.
I can't find 1 clean ifc export ( multiple (identical named)parameters for different categories are mostly basic problems because of bad templates).
The settings for a Revit template are extreme hard to manage because every project starts with the template status on the beginning of a project (and you can't change a lot).
Tekla -> change template -> all the projects get the updates
Rebar in Revit is just a large struggle if it's difficult.
Tekla -> it's very very very very easy
Revit-> fulltime bim manager in a company (or mutliple)
Tekla -> low level bim management gets very good results (multiple projects in one action get all the updates )
...
Autodesk is killing it's own software because the code doens't get a 64bit architecture coding
But tekla is not fit for architecure (structure only)
Of course! the right tool for the right job!
I wouldn't never use Revit for structures!
Unfortunately we work with curtain walls and building envelopes... some of our sub-contractors even tried to use Tekla, since they already used it for structures, but results was very poor... insufficient precisions, export files needed to be fixed, IFC files didn't pass quality assurance, ...
Maybe in a few years... we are not Autodesk slaves, our CDE is Trimble Connect, not BIM360 ![]()
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.