Closed balrobs closed 7 months ago
I can't reproduce the problem, for me moving the object using the gizmo works fine. Is there any error message in the output window?
About the gizmo being placed at (0,0,0), that's normal, because that's where the placement of the object is (entity #42). Does it happen differently in BlenderBIM? (I can't test right now, need to recompile it)
No, unfortunately no error in the report-view. But changing the z-value of the Position freezes FreeCAD with errors:
About gizmo problem you are right. Blender shows gizmo at (0,0,0) too.
That's weird... I can change the position without errors. I don't understand what's happening :astonished: Can you try with an updated version of NativeIFC? I just tried a fix...
That's really weired ... in order to narrow down the problem I tried this:
Result:
I did another test that maybe can help:
Here I see this error:
11:30:32 Imported IFC_Test1.ifc ( 0.0 Mb ) in 00:00
11:30:52 Traceback (most recent call last):
File "C:\Users\Robert\AppData\Roaming\FreeCAD\Mod\FreeCAD-NativeIFC\.\ifc_objects.py", line 58, in onChanged
self.edit_placement(obj)
File "C:\Users\Robert\AppData\Roaming\FreeCAD\Mod\FreeCAD-NativeIFC\.\ifc_objects.py", line 178, in edit_placement
result = ifc_tools.set_placement(obj)
File "C:\Users\Robert\AppData\Roaming\FreeCAD\Mod\FreeCAD-NativeIFC\.\ifc_tools.py", line 866, in set_placement
scale = ifcopenshell.util.unit.calculate_unit_scale(ifcfile)
File "C:\Users\Robert\Downloads\FreeCAD_weekly-builds-33236-2023-05-18-conda-Windows-x86_64-py310\bin\lib\site-packages\ifcopenshell\util\unit.py", line 453, in calculate_unit_scale
units = file.by_type("IfcUnitAssignment")[0]
<class 'AttributeError'>: 'NoneType' object has no attribute 'by_type'
Can you try again now? I just added a line that would print more info if the same problem happens again...
At first glance I can't notice any difference with the new update.
I did this other test that maybe can help:
Hi Yorik! I have seen the latest progress in the development of the IFC add-on and I am very happy about it. So I tried to reproduce this problem with the latest updates (FreeCAD weekly bundle for Windows ver. 2024/03/11 and NaitiveIFC add-on ver. 2023.10.27). The problem seems to have been solved in the meantime, so I think the issue can be closed. Best regards and thank you for your work!
The best bugs are those that fix themselves ;) Thanks for confirming!
Hi Yorik! I found another strange behaviour:
PS: BlenderBim handles the file without problems