-
-
February 21, 2020 at 6:01 pm
ansysuser
SubscriberHello,
I have a steady-state simulation that worked just fine. Then I changed one of the boundary conditions from velocity inlet to pressure inlet and re-solved. The solution converged just fine, but immediately after solving I get the error, as if Fluent tries to do something new after solving. I have no idea why simply changing boundary conditions and re-solving leads to this error. Here is a screenshot.
Â
Â
As I said, this error shows up before I try to do anything with the solution.  Note the solver says solution has converged.
What steps can I take to get rid of this error? It prevents me from updating the solution in WorkBench even though I have convergence according to the solver.
-
February 24, 2020 at 10:29 am
Keyur Kanade
Ansys EmployeeDid you have any commands used on 'velocity-inlet'? e.g. isousurface of mesh or contours or similar to that?Â
It looks like Fluent is trying to display something from here and it not getting that zone.Â
Regards,
Keyur
Â
Guidelines on the Student Community
-
February 24, 2020 at 9:52 pm
ansysuser
SubscriberHello kkandade,
No. I issued no commands. That is what is so puzzling about this. Anything else I should look for here?
-
February 25, 2020 at 5:05 am
Keyur Kanade
Ansys EmployeeIt must have something defined like report or contours etc. which Fluent is trying to update after solution is complete.
Can you delete cell 'C' in your workbench project, create a new 'Fluent' cell and connect to 'Mesh' cell. Set it up again from scratch and rerun.Â
If the project is big, you can test on a simple cylinder case.
Regards,
Keyur
Â
Guidelines on the Student Community
-
November 7, 2022 at 4:48 pm
Mahya Chavoshi
SubscriberHi everybody;
I got the same error after I set the outlet pressure for boundary conditions. Does anybody know how to fix it?Â
Thanks.
-
November 15, 2023 at 10:20 pm
Nikhil Varma
Subscriberhave the same problem. seems like a bug
-
November 16, 2023 at 2:25 pm
Rob
Forum ModeratorYou changed a boundary type, that can cause contour objects to reset and that could then give that error. Check reports and all graphics objects that use that surface.Â
-
- The topic ‘Error: display-object: No rendering surfaces have been set. Error Object: #f’ is closed to new replies.
-
3190
-
1024
-
962
-
858
-
798
© 2025 Copyright ANSYS, Inc. All rights reserved.