The latest release of OrcaFlex 11.6 is OrcaFlex 11.6e.
The new features introduced in OrcaFlex 11.6 can be viewed online:
The documentation can also be downloaded for offline use:
To upgrade to OrcaFlex 11.6e, 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 first released 11.6. 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.6 is available in the news section.
Known bugs in version 11.6e
OrcaFlex
- In a frequency domain analysis, the wave drift load (2nd order) results of a vessel whose low frequency motion is calculated (3 DOF) include the Lz force, Lx moment and Ly moment components. The wave drift load on such a vessel acts only on its three free degrees of freedom, so these components are never actually computed: the Lz force is reported as identically zero, and the two moments contain spurious values. They have been offered since version 11.6, despite the results being documented as available only for the free degrees of freedom of the vessel; they will no longer be available in a future release.
- Recent updates to the behaviour of the OneDrive client prevent the OrcaFlex spreadsheet from correctly interpreting relative file paths within a OneDrive or SharePoint folder synchronised to the local machine. The spreadsheet is unable to map the workbook URL to a local folder and so cannot resolve relative file names, such as the template file name on the pre-processing worksheet. In a future release, the OrcaFlex mapping code will be improved, and relative file names in a synchronised OrcaFlex spreadsheet are expected to work without errors.
- For very large models, typically those with many interconnected lines, an access violation or unexpected program error can occur in statics, or in another calculation that uses the sparse matrix solver. This happens when the decomposition of the model’s sparse matrix needs more than about 2.1 billion non-zero entries. In a future release, such a calculation will fail with an error message stating that the matrix is too large to decompose.
- Name labels in a pale colour, including the default white, cannot be seen when a wire frame view is printed, or exported as a metafile or PDF, because these are drawn on a white page. In a future release, such labels will be drawn in black.
- Modal analysis can give wrong or inconsistent results in three cases, mostly when the number of modes extracted is small enough for the iterative Lanczos eigen-solver to be used. First, a model with repeated natural periods, for example one with several identical lines, can omit some of the repeated modes without warning, and report other modes in their place. Second, a model whose static position is an unstable equilibrium can report modes as if the position were stable; only extracting all the modes reports the instability. Third, a statically indeterminate model, which can move in some way with nothing to resist it, for example a free 6D buoy attached to a line end with zero bending stiffness, either fails with the message that the static position is an unstable equilibrium, or reports a spurious mode with an enormous period. Which happens depends on rounding, and can change with the number of modes extracted. In a future release, the Lanczos eigen-solver will be replaced with a more robust implementation. All the repeated modes will be found, an unstable equilibrium will be reported whatever the number of modes extracted, and a statically indeterminate model will fail with a message saying so.
- In shaded graphics views, overlapping translucent surfaces can be drawn incorrectly, for example where a translucent seabed overlaps itself.
- Imported 3D models are drawn opaque in shaded graphics views, ignoring the opacity of their materials.