-
Notifications
You must be signed in to change notification settings - Fork 134
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
OpenCascade Exception when Creating Grids #135
Comments
yes the same issue... at BRepOffsetAPI_MakePipe.{ctor}(BRepOffsetAPI_MakePipe* , TopoDS_Wire* , TopoDS_Shape* ) |
Do we have a test file to confirm this fix? |
kikootwo can you provide a file for this please. Just removing the Conversion based unit line seems odd, why do you want to do this? I suspect if you do so the units and the model precision will mismatch. i.e. The model will default to millimeters and everything will be approx 3 times smaller but you precision will still be the same. |
I am having the exact same issue with an IFC file. It loads with errors and warnings in Explorer but when in debug mode it crashes. The error is System.StackOverflowException ` var model = IfcStore.Open(dlgFileName);
I have tried in XbimXplorer & Xbim.Presentation the following packages I can share the IFC file if need be. I have searched the Internet up and down and cannot find a solution!!!! Please help. |
Hello,
If you have instantiated an IFCGRID type, and have not defined these lines:
#43= IFCDIMENSIONALEXPONENTS(1,0,0,0,0,0,0);
#44= IFCMEASUREWITHUNIT(IFCRATIOMEASURE(0.3048),#42);
#45= IFCCONVERSIONBASEDUNIT(#43,.LENGTHUNIT.,'FOOT',#44);
XbimXplorer will throw this exception

To recreate this bug, remove your reference to IFCCONVERSIONBASEDUNIT from unit assignment in any file with an IFCGRID. Please let me know if you need any additional information.
EDIT: Forgot to mention, the grid must have at least one grid axis.
The text was updated successfully, but these errors were encountered: