-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.3.1 not exporting #43
Comments
I will add a catch for that, there is no support for the entity IfcPreDefinedPointMarkerSymbol, or send to be on your model somewhere. |
Hi, here is the test model I use... |
and here is the .ifc that I wasable to export using v3.5.0 |
Thanks, that confirms my suspicion. |
Hi Jan, thanks for that feedback ! Do the folks at Trimble realise that you have single-handedly saved their Sketchup from BIM oblivion ? Without you plugin we could not pretend to keep up, we'd be obliged to go learn Rev(olt)it ! or some other big and expensive stuff. I mean the possibility of creating and importing correctly structured ifc files is the ABC... Anyway, many thanks and keep up the good work ! |
Just one slight niggle... I just checked, and whilst I can now export without the crash, the layers still do no transfer into the exported ifc despite the option being ticked in the preferences... what am I doing wrong ? |
Well, not in the ifc from 4.3.1 |
Maybe it's an import problem with eveBIM ? But that would be odd as eveBIM interprets the 350 file correctly. |
I found it. In recent versions I attach the layer to the mapped shaperepresentation instead of the direct shaperepresentation, it seems that eveBIM doesn't recognize that. It might be better to revert that change, I will look into that. |
...does the 431 version export "ifc.zones" ? it didn't seem to, but again, this might be an eveBIM issue. |
I just tested zones by creating a couple of spaces and nesting those within a zone component and it showed up, even in the eveBIM version I just downloaded. |
oh, right, great news, although one nice thing about eveBIM is that you can create zoning strategies even on ifc files without them from SU. Well, as soon as a 4.3.x version remaps the layers, I'll give it a go :) |
Jan, bad news I'm afraid... v4.3.3 was working fine til I updated to the latest SU2023 patch from 15th of March... & now I get messed-up ifc files. I checked there was no other plugin messing things up by disactivating all but IFC Manager... no improvement, & I went back to version 3.4.7 of IFC Manager & the export was perfect... Best regards, |
Hi I just installed the 4.3.1 via .rbz and when testing an export, this is what I got in the RubyConsole:
"Error: #<NoMethodError: undefined method
representation=' for #<BimTools::IFC2X3::IfcPreDefinedPointMarkerSymbol:0x000002cc9f0a1158>> C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/ObjectCreator.rb:343:in
create_geometry'C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/ObjectCreator.rb:125:in
create_ifc_entity' C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/ObjectCreator.rb:71:in
initialize'C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/IfcModel.rb:229:in
new' C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/IfcModel.rb:229:in
create_ifc_objects'C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/lib/lib_ifc/IfcModel.rb:133:in
initialize' C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/export.rb:60:in
new'C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/export.rb:60:in
export' C:/Users/VIVARCHI/AppData/Roaming/SketchUp/SketchUp 2022/SketchUp/Plugins/bt_ifcmanager/loader.rb:127:in
block in module:IfcManager'c:/users/vivarchi/appdata/roaming/sketchup/sketchup 2022/sketchup/plugins/!!fredo6_lordofthetoolbars/controller_lordofthetoolbars.rbe:133:in `block in new'"
Not sure what's going on here :(
The text was updated successfully, but these errors were encountered: