HyperWorks 12.0 Release Notes

DDVOPT,2 with SHAPEOPT,2
DDVOPT,2 (a continuous optimization phase followed by a discrete optimization phase starting from
the continuous optimum) is now automatically activated when SHAPEOPT,2 (alternate algorithm for
shape optimization) is used along with discrete design variables.
Long Data Format for the .grid File
The long data format can be used for increased accuracy and can be written out using the
PARAM,GRIDFORM,LONG data.
LTID and UTID for DRESP2 and DRESP3
LTID and UTID (table identification number of a TABLEDi entry that specifies the lower and upper
bound as function of a loading frequency) are now supported for DRESP2 and DRESP3 responses on
the DCONSTR and DOBJREF cards.
Back to top
12.0 Release Notes - Improved Error Handling and Messaging
• OptiStruct errors out when TMINPLY and the designable ply thickness are the same. TMINPLY
should be less than the designable ply thickness.
• For responses used in modal frequency response optimization, the ATTB field on the DRESP1 card
cannot be blank when used with FREQ3, FREQ4 or FREQ5 loading frequency cards, and when the
number of modes on the EIGRL card is not specified. A clear error message is printed if this is the
case.
• OptiStruct appropriately errors out when the normal velocity of grids referenced as responses,
cannot be calculated. This may occur due to the grids not being connected to any shell or solid
elements, or not being located on the surface of the model.
• Improved error message when an unreasonably large number of potential starting points is used
with the global search option.
• Improved error message when multiple sub-ranges are defined for the same response for
DCONSTR or DOBJREF.
• Improved checking for manufacturing constraints that cannot be satisfied because they do not
involve designable (or existent) plies, for composites optimization.
Back to top
12.0 Release Notes - Resolved Issues
• A global search option run would incorrectly use the design property values when run with the –
analysis run option. This issue has been fixed and the analysis property values are now used when
run with the –analysis run option
• When a frequency sub-range was used with DCONSTR or DOBJREF, the convergence criteria would
incorrectly take into account inactive responses that were not within the range of frequency.
This has been resolved and the active responses within the specified frequency sub-range are
considered for convergence