08-31-2016 03:52 PM
It is said that api_fix_check_problems attempts to fix the following problems:
"The insanity IDs for which a fix will be attempted are: CRV_BAD_FITOL, SURF_BAD_FITOL, CURVE_APPROX_OVERCLAMPED, CURVE_MISSING_DISC_INFO, and SURF_MISSING_DISC_INFO"
(I'm referring to the documentation:
The list is perhaps outdated. What's the current state of api_fix_check_problems, were some other insanities added?
I'm specifically interested in the following issues:
1. pcurve location != coedge location
2. internal position on coedge off face
Solved! Go to Solution.
08-31-2016 04:08 PM
This API is mostly a historical curiousity I think. I don't advise using it.
The errors you mentioned occur because the part is not tolerant but it should be. Use api_tolerize_entity for this.