OUTDATED VERSION. Follow the link for the latest version: https://www.hexagonmi.com/MSC-Apex-Generative-Design/help
Warning & Error Codes
In this section you find information about occurring warnings and errors. As we are still 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 Meshless Generative Design Status or in the log files in the result folder in your workspace (log_error.log & log_warning.log).
Information regarding the “Analysis Readiness” checks can be found here.
Warning/Error Code | Description | Explanation & Action Steps |
|---|---|---|
“Probable reduction of the model is more than …% of the starting model.” | This is just a notification that the predicted reduction of the model is very high. Further information here. | |
Wf06bfce1 | A material name was not set. | If you are using the Command Line execution execution, please make sure a name for the material is set in the Configuration File file. Please contact MSC Apex Support. |
W86a76001 | The Start Space volume is magnitudes smaller than the Design Space. | Check the unit system of your Start Space. When using a Start Space the STL-file needs to be available in the same unit system as the optimisation was setup. Further information about a Restart here. |
W1c05e9e6 W1c075d08 W1c7b96c7 W1c0aad3a W1c102ca3 | Result data couldn't be projected onto the result geometry for certain polygons (black). The stresses and displacements cannot be viewed in certain areas. | Please contact MSC Apex Support. |
W1cc18b49 W1ca9b0d5 | No Solver IP was found in the configuration file. | The set up for GPU and/or Remote Solving is not complete. The optimisation will fall back to local CPU solving and continue running. The solver settings can be changed in the Application Settings - Generative Design Solver. If you are running a Command Line optimisation, make sure the appropriate Solver IP is included in the Configuration File. If further issues occur, please contact MSC Apex Support. |
W1cc213b7 W1caa0e09 | No Solver Port setting was found in the configuration file. | The set up for GPU and/or Remote Solving is not complete. The optimisation will fall back to local CPU solving and continue running. The solver settings can be changed in the Application Settings - Generative Design Solver. If you are running a Command Line optimisation, make sure the appropriate Solver Port is included in the Configuration File. If further problems occur, please contact MSC Apex Support. |
W39fed060 | The Matrix is too large for the GPU solver. | The GPU memory is too small for the model. The optimisation falls back to CPU calculation. Continue calculating on CPU or reduce the matrix by adjusting the model ( e.g. reduce the |
W7004d2f0 | Inexact match for space/mask …'s file name - this feature is deprecated and will be removed in future releases. | If you are using the Command Line execution, please make sure the full file name including the extension is written correctly into the Configuration File. The optimisation will continue but might not run in future releases. If you have used the GUI to setup the model, this will be handled automatically. |
W61379840 | Meshfix warning … | Internal error. Please contact MSC Apex Generative Design support. |
W8637fb82 | Cannot check out GPU features. | 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. The optimisation will fall back to local CPU solving and continue running. |
Wbd1ee66a | Solving on GPU solver failed for a non-fatal reason (solving on CPU can continue): Either due to W39fed060, W1cc18b49, W1cc213b7, W1cc2b4cd or W8637fb8 or as a result of a GPU solver failure / communication issue. | If any of the other warning codes were reported, refer to them. Otherwise check GPU solver log and its service status (C:\Windows\Temp\cudaSolver). |
We96f8e1 | GPU solution was not requested - running on the CPU only | This is an information regarding the usage of GPU solving. The GPU solving was not activated and the optimisation will be carried out on CPU. |
We97672e | GPU solution is enabled - attempting to solve on GPU | This is an information regarding the usage of GPU solving. The GPU solving was activated and the software will use GPU solving if there aren’t any other issues. |
We97dfe0 | GPU solution was requested but is not installed - running on the CPU only | This is an information regarding the usage of GPU solving. If you wish to optimise using GPU solving, make sure you have installed the GPU service. Further information regarding the installation and usage here. |
W1ce059fa | One or more of the boundary conditions (Load, Moment, Acceleration, Pressure or Displacement) could not be found in the configuration file. Please see which boundary condition in the explicit warning message! | The optimisation will continue without the unspecified boundary condition. Review the result as well as your input and adjust the model setup if necessary. Please contact MSC Apex Support for further information. |
W1cc2b4cd | The software versions of the local MSC Apex Generative Design and the remote MSC Apex Generative Design program do not fit together.
| If you are using the Command Line execution, make sure to install the same release versions locally and remotely. All release versions are available at the Solutions Download Center. The optimisation will fall back to local CPU solving and continue running. For further information, please contact MSC Apex Support. |
W1c3051d8 | Mass calculation is incorrect. | If you are using the Command Line execution, make sure you have set a Density for all spaces in the Configuration File. Please contact MSC Apex support. |
W6e4e5290 | Empty mesh in input file … . An input file contains no geometry. | If you are using the Command Line execution, make sure that only valid input files are considered in the optimisation. Check your input files and start the optimisation again. |
W5c2f1240 | Unable to compute centroid for Space/Mask … - 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. Please contact MSC Apex Generative Design support for further help. |
W1cb255fc | Unable to find file for optimisation space … . | If you are using the Command Line execution, add an STL-file that’s set as the optimisation space to the folder and start the optimisation anew. Please contact MSC Apex Generative Design Support. |
W1c88afc8 | No defined value for the complexity was found in the configuration file. | The optimisation continues with the default value for the Complexity. If you want to change the value go to the Application Settings - Generative Design Solver and adjust the value. |
W1c89362a | No value regarding the detail of the elements was found in the configuration file. | If you are using the Command Line execution, the detail was not set in the Configuration File. The optimisation will continue with the default value for the detail. Please contact the MSC Apex Support. |
Wb22daeb0 | Fall back to CG Solver. | Connection to GPU solver was not possible. Falling back to CPU solving. This can happen in different situations:
|
W1ca0d86b | The setting for Shape Quality is missing in the configuration file. | If you are using the Command Line execution, make sure a Shape Quality is set in the Configuration File. Supported are the types Preview, Balanced and Fine Tune. The optimisation will continue with the default option Balanced. If you would like to use another Shape Quality please define this in the Studies Tab/configuration file. Please contact the MSC Apex Support. |
W1ca4a4c1 | The setting for Strut Density is missing in the configuration file. | If you are using the Command Line execution, make sure a Strut Density is set in the Configuration File. Supported are the types Dense, Medium and Sparse. The optimisation will continue with the default option Medium. If you would like to use another Strut Density please define this in the Studies Tab/Configuration File. Please contact the MSC Apex Support. |
Wc4fe85e2 | BF15844446026 is deprecated, please remove in the configuration | Big Non-Design Spaces are considered correctly in the optimisation and have no influence. The additional Code is no longer necessary, please leave the code out of your models. |
W3c2bc158 | There are not as many GPUs available on the license server … as are recommended for this optimisation … . | There are multiple Events in the optimisation setup and equally many GPUs are recommended to enhance the calculation time. Adjust the number of GPUs or make more licenses available for the optimisation. |
W3c2bc541 | It is not possible to check out at least one GPU license. | There are no GPU license available . If you have GPU licenses, make sure they are available. If this problem is occurring although your having the required licenses please contact the MSC License support. If you would like to get GPU licenses please contact your MSC sales representative. The optimisation is falling back to CPU solving and will continue. |
W3c2bc540 | The available number of GPU licenses could not be checked out! The system is trying to checkout one less GPU license. | The System cannot find the defined number of GPU licenses. You can only use GPU solving if you have GPU licenses. Please contact your MSC Sales Representative for more information on how to get GPU licenses. |
We7ec7c46 | The number of maximal used GPUs (solverUsedGpuMax) is higher than the number of available GPUs. | If you are using the Command Line execution, adjust the number of solverUsedGpuMax and Restart the optimisation. Otherwise the optimisation will continue with less GPUs. |
W1c9c8673 | Not enough memory available. The model is too large, complexity is too high for this optimisation model. | Adjust the Complexity and try a new optimisation run. |
W1d175302 | No volume greater than 50% found! The optimisation model is insufficiently designed. The solver cannot find a satisfactory solution. | This can be a hint that the STL-file format is incorrect for a Restart or Start Space optimisation. It’s also possible that the input STL-file is defect. Please check the unit system and the quality of the input STL-file. Another reason for this error can be an unsupported filename. There cannot be spaces, parenthesis and accents in the names – except for the SolidWorks STL-files. SolidWorks produces a specific name which our engine supports and is able to read. The software supports binary STL-files and almost all ASCII files but not faultless. For further questions please contact MSC Apex Support. |
W1cbb4449 | There is not enough memory (RAM) available for the optimisation to continue. | Please close other applications to free memory. The optimisation will retry to allocate the memory and continue running if enough memory could be allocated. Otherwise, reduce the Complexity of your optimisation model (Application Settings - Generative Design Solver). |
W175a5d37 | Unable to meet requested detail level. Minimum level: … The model is too large, complexity is too high for this optimisation model. | The input level of detail cannot be reached. Adjust the detail value and try another optimisation run. If you have added Advanced User Settings with adjusted iteration levels and stress goals, these are not chosen very well. Please adjust your model set up and try another optimisation run. Please contact the MSC Apex Support. |
W175bd3ad | Unable to meet level of detail. The model is too large, complexity is too high for this optimisation model. | If you have added Advanced User Settings with adjusted iteration levels and Stress Goals, these are not chosen very well. Please adjust your model set up and try another optimisation run. Please contact the MSC Apex Support. |
We6f8522a | Config line is not UTF-8 encoded | The input of the configuration file doesn’t meet the required coding standard. If you have entered wide-characters, please change these and try to start the optimisation again. Please contact MSC Apex Generative Design support for further help. |
W17419b31 | Configuration file does not exist. | If you are using Command Line execution, make sure a Configuration File is available in the optimisation folder. Please contact the MSC Apex Support. |
W17421f47 | Missing configuration name or ending. | If you are using Command Line execution, make sure a Configuration File with a valid name and file-ending is available in the optimisation folder. Please contact the MSC Apex Support. |
(former W8b7af774) | “The Mask … was removed.” The Design Space has lost the connection to a Non-Design Space on which no boundary conditions are applied. | |
E86b9657 | “Start space volume is magnitudes bigger than design space. You might want to check start space scaling”
| The Start Space STL-file is in a wrong unit system Only the SI-Unit system is supported for a Restart |
“No fixed knots found.” The Design Space has lost the connection to one or more of the fixation(s). The model is no longer fixated and it doesn’t make sense to continue with the optimisation. | ||
“The … was removed and the applied boundary constraints 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. | FAQ: Tearing off of Non-Design Spaces In case you are using the symmetry option, have a look at your model setup. The forces and constraints must be applied in the direction of the positive coordinate system of the model. | |
Ec9140297 | Please don't overlay different Coordinate Systems that have fixation constraints. | Check your fixation constraints which refer to the local coordinate systems. |
Missing iteration level … in config | The input of the Advanced User Settings is incomplete. | |
E1cbd48f4 | Error setting b1/b2/x1/x2 to zero. Memory allocation error. | There is not enough working memory available. Adjust the complexity to a lower value and restart the optimization. |
GPU Solving CUDA Solver Warnings & Errors
Warning Code | Description | Explanation & Action Steps |
|---|---|---|
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. |
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.
Copyright (C) 2020, MSC Software Corporation and its licensors. All rights reserved.