TAGGED: cad-import, fluent, spaceclaim
-
-
September 16, 2025 at 10:36 am
fsae.unitn
SubscriberOur aerodynamics department has been facing some issues with Spaceclaim.
Our workflow is usually the following: we design all geometries in Inventor, then export them in STEP format to SpaceClaim, where we create the fluid volume before moving the geometry into Ansys Fluent.
The issue we are encountering is the following:
When we generate more complex geometries in Inventor using the loft function (which connects two sketches following a defined curve), some parts of the component—or sometimes the entire component—are lost after importing the geometry into SpaceClaim in STEP format.
The first picture shows the file in Inventor, and the second shows it in SpaceClaim. As you can see, the rear wing presents problems, and sometimes the geometry even disappears completely.
Can someone tell me how to fix the problem?
We were considering going back to the 2023 version, but we’re not sure if that would help.Â
Thank you in advice for your support
-
September 16, 2025 at 12:20 pm
peteroznewman
SubscriberI don’t know that this will help, but it is worth a try. Export a Parasolid file from Inventor and open that in SpaceClaim 2025.
- SpaceClaim 2025 uses a Parasolid kernel. When opening a Parasolid file, no translation of shape takes place.
- If you export a Parsolid from Inventor, only one translation of shape is done to open in SC2025: Inventor > Parasolid.
- Currently, you are seeing two translations: Inventor > STEP > Parasolid (in SC2025).
SpaceClaim 2023 uses an ACIS kernel, while Inventor uses a kernel that was forked from ACIS in 2001. If you have SpaceClaim 2023 installed, you can try opening the Inventor file directly. You can also try exporting an ACIS file (*.SAT) from Inventor and opening that in SpaceClaim 2023. There is reason to believe that this may result in a cleaner translation.
-
September 16, 2025 at 12:51 pm
fsae.unitn
SubscriberThank you for the answer. We've just tried with the same CAD, just by loading the '.x_t' file into Spaceclaim some parts are corrupted as we've already seen in previous images. We've tried to repair these with split edges function and also with inexact edges, some parts are correctly repaired, other instead are even worse. Another issue that we have, that may be correlated to this problem, is that when we try to create the enclosure some parts are excluded.
And also, when we use the split edges tool for repairing sometimes the geometry changes as shown in the pictures.Â
Â
Thank you for supporting, we wait for a response.
-
- You must be logged in to reply to this topic.
- FSAE CFD – Lesson 1 Preparation question (Using Discovery)
- Script for subtracting models
- Project lines/edges into a face with the direction normal to the face
- Spaceclaim file reference error
- No preview in explorer with scdox file
- Multiple Instances of SpaceClaim taking multiple licenses
- Issues after installing new service pack 2024R1 (sp5)
- Add-in Error Excel
- Problems with loading my Discovery Mesh into Fluent
- Missing SubDivWrapper.dll
-
3867
-
1414
-
1241
-
1118
-
1015
© 2025 Copyright ANSYS, Inc. All rights reserved.