Miscellaneous

Known Issue

Workaround or Solution

Applying SpaceClaim Constraints

When dimensioning between an assembled body (body with assembly constraints applied to it) and another entity, an entered value to move the body could be incorrectly applied while resolving the assembly constraint. It should be clear that the entered value is incorrect, as the triad does not follow the move of the Body, and the driving dimension can be refreshed to show actual distance, not the entered distance. (TFS 770889)

The suggested user action is to apply the dimension to the Component of the assembly tree as opposed to the Body. When doing any form of assembly modeling (spatial arrangement/placement), one should always act on the Component as opposed to the Body.
Speos does not support *.scdocx filenames and folder names with an end space. (TFS 921277 SF 64806)
When the Libraries panel is located in the same group as the Structure panel, if you click Material Libraries to hide the Libraries panel, the panel hides only after you stop hovering over the Material Libraries button. (TFS 601790)

Move the Libraries panel into a group that does not contain the Structure panel.

Optical Library: ANSYS_OPTICAL_LIBRARIES_202XRX_WINX64.zip may fail to be unzipped with the Windows standard zip function due to some filepath being too long. (TFS 883546 SF 63321)

Use 7-zip.

Speos Templates (*.scdot) are not supported. You can neither save as nor open a *.scdot file. If you try to save as *.scdot, the file will be automatically saved as *.scdocx instead. (SF 61626)
When using a SpaceClaim document that references an external document, if SpaceClaim is not opened the process to copy the external document into the "otherDocs" folder is not done. (810170) Make sure to open Spaceclaim (via Workbench) before saving the Workbench project. Then you can save the Workbench project.
Locked document are not supported. (TFS 812291 SF 56983)

Unlock document to modify your Speos project. Beware that unlocking must be performed in the same version as the version in which it has been locked.



General: Speos applications only support ASCII / ANSI / UTF-8 file formats for all input text files (*.spectrum, *.ies, *.bsdf, etc.). (TFS 784679)

Licensing Management: opening a version 2022 R2 then opening a version 2023 R1 does not work. (TFS 730734) First open the version 2023 R1, then open the version 2022 R2.
Axes are not exported when saving a project to another format than scdocx. (TFS 656985 - SF 38823)
When a project is added to a geometry in Workbench, the Output Files are not copied. (TFS 202762)
The following characters are not supported in Speos features' name: " < > | : * ? \ / (TFS 263147)
After opening a component (Open Component) from the Structure tree, Speos objects added this component are not displayed in the tree. (TFS 449252) Refresh the tree.
After a Speos tree refresh, the UV Mapping and Local Meshing sections may not appear at the same place in the tree. (TFS 449445)
Speos session closes when a Speos instance is opened from workbench.(TFS 372481)
Unwanted 3D view rendering artifacts can be seen with certain geometries when the distance from origin of the scene to the point of view is very far away. (TFS 435735 SF 32841)
If you import an external CAD part using the Open file command, no CAD Update link is created; then you cannot use the Geometry Update tool to update the part. (TFS 408007 SF 32027)

In some cases, a version upgrade might prevent Speos block from being correctly loaded in Ansys Workbench.

Delete or adjust the version of the following environment variables: SPEOSSC_BIN_PATH, SPACECLAIM_PATH. Then, reload the Speos block in Ansys Workbench.

When migrating a project created before 2021 R1 version, some features may appear in error "Invalid link context [...]" and may have lost their link to sub features.(TFS 326138)

When working with heavy projects, Speos might show a performance loss for Speos objects edition. (TFS 252829)

Importing models containing heavily faceted parts (parts containing a lot of small faces) may take a large amount of time and a size difference between the original model and the one imported can be observed.(TFS 259625)

In some cases, when defining sources, surfaces can only be selected from the 3D view and not from the structure tree. (TFS 202224)

In some case, importing Complex/heavy data in Speos might be lengthy. (TFS 202463 - SF 24742)

Moving a body through a copy/paste in the structure tree might break its relationship to Speos materials. (TFS 202463)

When importing a HUD feature from Speos for CATIA V5, the HUD elements fail to be imported with the geometry. (TFS 214218)