
Wed, 07/30/2025 - 12:54
Forums:
The ShapeUpgrade_UnifySameDomain does not work properly, but after saving the shape as a STEP file and then re-reading it back in, ShapeUpgrade_UnifySameDomain produces good results.
The shape was obtained by using BOPAlgo_Splitter on several faces and a solid. Is there any issue with this shape? (What method should I use to identify these potential problems?) Could the process of saving it as a STEP file have reconstructed the shape, resolving these issues and enabling ShapeUpgrade_UnifySameDomain to work properly?What happens during the process of saving to STEP?
Attachments:
Wed, 07/30/2025 - 16:44
Hello. The difference is: during STP export AND step Import you perform list of ShapeHealing operations.
For most of the OCCT Modeling operations, we expect that model are valid and fixed. So, please check the validity of the model and apply ShapeFix on your shape before using them into the Modeling algorithms.
Intefaces for shape healing: ShapeFix_Shape
interfaces for topology validation: BRepAlgoAPI_Check
Best regards, Dmitrii.
Thu, 07/31/2025 - 08:10
Thanks.But it seem not work.ShapeFix_Shape、BRepAlgoAPI_Check、ShapeUpgrade_UnifySameDomain,These classes don't seem to have many interfaces available to modify. Or am I using them incorrectly?
Thu, 08/07/2025 - 12:27
Please report a bug in Github with file sample and C++ code to reproduce.https://github.com/Open-Cascade-SAS/OCCT/issues/new/choose
Best regards, Dmitrii.
Mon, 08/11/2025 - 06:46
I filed a bug here:https://github.com/Open-Cascade-SAS/OCCT/issues/666
Thanks for taking a look.