TomasJ

Update: The issue seemed to be SpaceClaim import options. Now everything works as expected.

Hello, Thank you for your reply. I am using the provided ACT app but I have also tried the one from WB app store as well as its older versions, none working. I am running the most recent caeses version as I have renstalled it yesterday in hopes of resolving the issue. The machine is running latest windows 11. As to the issue in workbench. The .sat file is being created in proper location. I have had some luck today to import the part correctly when I save my caeses project, export the .fsc file and make sure there have been no further changes (I believe that makes the project open in caeses standalone which interferes with ansys WB? So far I can import the part with colored faces but none are transfered as dedicated zone labels. This is something that I will have to look into.

Hello, I am atempting to load my caeses project into ansys workbench to carry out a parametric study however when I load in the .fsc file I get an error in command windows stating that the provided scope could not be found. Aditionally if I attempt to generate an .fsc script straight from Caeses and run the very same script from inside the app, it crashes. I am providing a very simple example of such script that alreadt throws errors. I would be happy to refer to the documentation, however I am unable to open it in the software (the button seems not to work for me). Thank you very much for any possible aid. test.fsc test.cdbc