In this section you find information about occurring warnings and errors. As we are continuously gathering information on how/when warnings and errors occur and under which circumstances this site will constantly be updated with new information.

You can find Warning & Error codes displayed in the Studies tab by double clicking on the Generative Design Status or in the log files in the result folder in your workspace (log_error.log & log_warning.log).

Please contact the MSC Apex Support (mscapex.support@mscsoftware.com) if a warning or error occurs which is not yet listed here or cannot be averted by applying the compiled help.

Information regarding the “Analysis Readiness” checks can be found here.

W5754bb78

GPU solver was not requested, using CPU solver only.

This is an information regarding the usage of GPU solving. The GPU solving was not activated.

W75eebb60

GPU computation was requested but is unavailable due to license limitations, using CPU solver only.

This is an information regarding the usage of GPU solving. To use GPU Solving an additional license is necessary. Please check your licenses in Options → License Manager or deactivate GPU solving in the Options → Application Settings - Generative Design Solver.

W7c60aa30

GPU computation was requested but no devices were found, using CPU solver only.

W03bfd378

GPU computation was requested, using up to … GPU(s).

W255de448

Found … voxels outside of valid design space … removed them.

Optimization run continues.

Please contact MSC Apex Support.

W244ff728

Cannot map voxel …

The loads and boundary conditions could not be mapped to the voxel model and might not be considered in the optimisation anymore. LBCs should always be applied to Non-Design Spaces. These ensure a correct consideration of the LBCs during the optimisation.

W6df456e8

Carve intersection is disabled. The fallback intersection method will take place instead.

We8bf37f1

Remeshing failed, mesh was not changed. The optimisation will continue without creating a remesh.

W1511c540

Sewing resolution … exceeds rasterization resolution … adjusting threshold from … to …

The model is very big (galactic size) and cannot be imported in the software. Check you unit system and dimensions.

W62b92548

Conflicting local coordinate systems at symmetry boundary.

The symmetry plane is too close to a Non-Design Space which experiences LBCs which refer to another local coordinate system. The symmetry or the local coordinates might not be taken into consideration.

W2641b610

Symmetry causes all remaining DOF … to be fixed

The optimisation has reduced nearly all material which is not a fixation or part of the symmetry plane. All remaining elements are fixated. The applied force might be too small in comparison to the stress goal which ensures the reduction of almost all the material. Please reconsider your model set up.

W6bef1a88

Low memory, reducing preallocation amount … attempts left.

Memory storage is checked. If not enough memory is available, less memory storage is checked. If there isn’t enough memory storage available to do the allocation an Error (Eb20f3210) will be occur.

W644693f8

Time estimation has become inconsistent, expect inaccuracies.

W5cfd1878

Solving matrix … via extern solver … failed.

Using CPU solver only

W4ebe0a20

… Projected memory requirement exceeds available memory - complexity … is too high. Theoretical limit: complexity … recommended: …

This is a feasibility check regarding the input complexity value. The chosen complexity value is too high to be calculated on this machine. A certain maximum complexity value is recommended.

W76bd49a8

Unable to compute centroid for geometry … using bounding box center instead

A “corrupt” STL/PLY file was supplied for a Mask named in the warning text. Depending on other mask settings (whether the surface is to be used / filled), different centroids / centers of gravity are computed. This warning indicates all those attempts have failed and instead the bounding box center is used.

This can happen if the input has degenerate triangles or is not a closed surface. Please check the input files or replace these if possible.

W2e4e8b88

boundary condition is dislodged - no active elements …

A boundary condition was disconnected. A reconnect and other connection strategies were unsuccessful. Please check you model set up and make some adjustments for a feasible model.

W33559448

License feature(s) have become invalid, checking out again in … seconds.

They will be checked out again in … seconds.

W5b09c550

event … has no connected boundary conditions.

The Event … has no connected boundary conditions. The Event will be ignored from now on.

W5b820290

geometry … is not used by anything

The geometry … is not used by anything in the configuration file and will not be considered in the optimisation.

W244ee728

coordinate system … is not used by anything

The defined coordinate system … is not used by anything in the configuration file and will not be considered in the optimisation.

W41d43530

Missing density for space … setting to …

The density is set to the value listed in the warning message.

W1fb6cc10

Config entry 'calculationType' is deprecated, please use 'shapeQuality' instead.

W384d5280

Config entry 'designType' is deprecated, please use 'strutDensity' instead.

W74060730

fullPivHouseholderQr failed, attempting next solver

Different methods for solving FE equation systems are being used. This one did not work so continuing to the next method.

W760bf120

colPivHouseholderQr failed, attempting next solver

Different methods for solving FE equation systems are being used. This one did not work so continuing to the next method.

W777a0bc8

completeOrthogonalDecomposition failed, attempting next solver

Different methods for solving FE equation systems are being used. This one did not work so continuing to the next method.

W041b3b18

CG failed

Different methods for solving FE equation systems are being used. This one did not work so continuing to the next method.

E7f716c48

This Error is only produced after another Error was encountered. The optimisation algorithm tried to continue despite the previous Error but could not continue. The optimisation fails with this Error although the primary Error is the reason for the terminated optimisation.

W6493a120

The configuration file entry 'solverMaxMemory' is deprecated, please use 'complexity' instead.

EE4ebe0a20

Projected memory requirement exceeds available memory - complexity … (detail …) is too high. Theoretical limit: complexity … (detail …), recommended: complexity … (detail …)

The chosen complexity value is too high to be calculated on this machine. A certain maximum complexity value is recommended. Have a look here.

Eb20f3415

boundary condition is missing elements

A Non-Design Space was removed and the applied boundary conditions are not considered

The Design Space has lost the connection to the force/constraint application point. The model is no longer complete and it doesn’t make sense to continue with the optimisation.

Make sure that the Keep Non Design function is activated. Increase the Complexity or decrease the Stress Goal.

GPU Solving CUDA Solver Warnings & Errors

W5c7572a0

No operational GPU found for solving input (insufficient free memory).

Check the memory status of your GPU and terminate other programs that might affect the GPU memory.

W24850de8

Error Closing worker thread socket.

CUDA Solver is terminated although the optimisation is still running.

The optimisation will continue and fall back to local CPU solving.

Check the status of your CUDA Solver.

Please contact MSC Apex Support.