Hi @PavelNedviga - thanks for putting the effort and time into this. It probably has to do with the parser we’re using, namely web-ifc.
Beyond sending us the model, can you let us know if it loads up fine in the demo app from ifc.js peeps here: IFC.js?
If yes, we’ll need to look into it closer on our end. It means the problem is in getting all the elements’ metadata (this is something the demo app doesn’t do upfront, as we do, but only does on selection).
If not, do report this to the ifc.js community, as they’re always up for finding and fixing edge cases!
ffs ifc files are pain in the proverbial place to deal with. it seems that the exception is when they work as expected :/
I guess I have same problem. All ifc models I try to load gives an error message except the model containing only space objects. But it seems that spaces cannot be displayed (maybe transparency settings?). Appears text saying “No displayable objects found in object e71c1ca…”
Whole model loads up perfectly in the demo app from ifc.js (except spaces)
I’m new with Speckle so it’s possible that i’m doing something wrong
The update is live. But, as always SIGH things work wonderfully on my computer but not on our kube cluster - there are files that locally go through fast but fail in production.
Cautiously, do give it a try. In the meantime, I’ll have steal @iainsproat and @gjedlicska (i hope they don’t hate me too much already) to debug remotely and see what deal is. I hope it’s a simple matter of resource allocation for the converter node, but you never know.
I’ve just checked the upload function with 14mb IFC file. It finished with error status, but much more faster. 30x anyway seems to be great gap on the opposite to what we had before. Hope your investigation @dimitrie will be finished soon)
Hi @PavelNedviga, PLEASE GIVE ME THAT FILE if you can!!! The funny thing about IFC file sizes is that they’re are not a good indicator of processing speed/efficiency - see @ElsaK’s 95mb file smoothly working (PS: happy it works for you now, @ElsaK & thanks for sending the file earlier!).
We’ve solved partly some problems of running the parser in production, but we might need to allocate more resources to it. If I have your file, I can test to see if it processes locally and benchmark memory consumption to understand better the production environment needs.
I’ve noticed that too Does the previous file you’ve sent me have spaces? If so, I can use it to debug. If not, will happily take a small IFC file with some spaces that i can iterate fast on I only have a revit derived one that’s quite fat and cumbersome to work with.
That is a weird error, and does look more like a server misconfiguration issue. It’s going to be tough to debug. Can you let us know how your local server is set up?