OrcaFlex 11.3

Release details

The latest release of OrcaFlex 11.3 is OrcaFlex 11.3a.

The new features introduced in OrcaFlex 11.3 can be viewed online:

The documentation can also be downloaded for offline use:

To upgrade to OrcaFlex 11.3a, download the install program from your company’s Orcina software download page. A link to this page was sent to your software administration contact when we released 11.3a. If you do not have access to this page, please contact us.

A more in depth discussion of the major new features introduced in OrcaFlex 11.3 is available in the news section.

Known bugs in version 11.3a


  • OrcaFlex could, in certain situations, stop responding when saving data or simulation files. This would require the OrcaFlex process to be terminated.
  • Constraints with variable data rotational stiffness might, in specific circumstances, have applied an incorrect rotational stiffness force when the angular displacement of the out-frame relative to the in-frame was between 120° and 180°.
  • The API functions which return modal mass and modal stiffness are documented as not returning values unless angles are reported as radians when calculating the modes. Previous versions did report values, erroneously.
  • Line end orientations calculated from end positions might have been calculated incorrectly if the line in question was connected to another line (directly or indirectly). This would only happen if the line statics step 1 policy was all lines included, and the result would be that the z-axis at each line end would point along the straight line between the two ends after step 1 statics had been computed on the parent line, rather than the straight line between their reset positions. A further consequence of this is that any end offset would have been applied incorrectly. Models using the none or parent lines excluded statics step 1 policy would not have been affected by this bug.
  • Running line step 1 statics with all lines included, but with step 2 and whole system statics suppressed, for a system in which two lines are connected via an intermediate constraint, might result in the child line solving its step 1 statics with the wrong boundary conditions.
  • Dragging end B of a line that used the calculated from end positions length and end orientations option may have resulted in end A moving too.
  • Dragging a mid-line connection may have dragged the wrong node or triggered an access violation error. This would only have happened if some rows of the mid-line connections data table were invalid.
  • The behaviour of the prescribed step 1 statics policy in conjunction with the calculated from end positions length and end orientations option was complex and unintuitive. This combination has no clear value, so is now ignored in reset and blocked once you try to run the model.
  • Saving a variation model or restart analysis as a text data file may have produced an unloadable YAML file if a new object (e.g. a vessel type) had been added (relative to the parent model) containing any sub-objects (e.g. a vessel type draught) whose names had been changed from their defaults.
  • Running a static state restart analysis from a parent dynamics analysis might have reported nonzero velocity and acceleration results for free constraints (or any object connected to a free constraint).

These bugs will be fixed in version 11.3b.