OrcaFlex 11.0

Release details

The latest release of OrcaFlex 11.0 is OrcaFlex 11.0c.

The new features introduced in OrcaFlex 11.0 can be viewed online in the OrcaFlex help file. The OrcaFlex 11.0 help file can also be downloaded:

OrcaFlexHelp.zip

To upgrade to OrcaFlex 11.0c from 11.0a or 11.0b, download the following ZIP file:

OrcaFlex-Patch-11.0a-or-11.0b-to-11.0c.zip

and execute the .msp patch file that it contains.

To upgrade to OrcaFlex 11.0c from 10.3 or earlier, 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.0a. 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.0 isĀ available in the news section.

Known bugs in version 11.0c

OrcaFlex

  • When copying objects between models via the clipboard, OrcaFlex copies associated type objects. For instance, if a line is copied from one model to another, any line types that the line uses are also copied. If the target model already contains type objects with the same names, then a decision must be made: use the data from the clipboard, or use data already in the target model? OrcaFlex is meant to ask the user to make this decision, but since 10.3a the mechanism to ask the user has been broken and the program always opts to use the data already in the target model.
  • Panel mesh import for Sesam .fem files was failing (reporting an invalid node number error) for some valid files that contain triangular elements (ELPTYP=25).
  • Embedded Python execution (e.g. external function, post calculation actions, user defined results, etc.) would sometimes fail for virtual Python environments.
  • Stiffener attachments protecting the ends of lines could make an unwanted Rayleigh damping contribution to the line end connection load if torsion is not included and the protected line end also has finite end connection stiffness.
  • Loading a static state simulation file could result in an invalid floating point operation if a summary results window was active.
  • Binary data files did not store information on whether constraint and turbine objects were locked in the model browser.
  • YAML fatigue files that use BaseFile were not being processed correctly in batch mode. The base file was being overwritten with the output .ftg file, and the output spreadsheet was being saved with the wrong file name.
  • Shaded graphics model import from panel mesh files was failing with an unexpected program error for very large mesh files.

OrcaWave

  • Panel mesh import for Sesam .fem files was failing (reporting an invalid node number error) for some valid files that contain triangular elements (ELPTYP=25).
  • Calculations which combined short waves with large, but finite, water depth could fail in some circumstances with a floating point overflow error message.
  • An OrcaWave calculation could fail with a floating point division by zero error message while processing interior free surface panels in a body mesh, i.e. panels for removing irregular frequency effects.

These bugs will be fixed in version 11.0d.