The latest release of OrcaFlex 11.0 is OrcaFlex 11.0d.
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:
To upgrade to OrcaFlex 11.0d from 11.0a, 11.0b or 11.0c, download the following ZIP file:
OrcaFlex-Patch-11.0a-or-11.0b-or-11.0c-to-11.0d.zip
and execute the .msp patch file that it contains.
To upgrade to OrcaFlex 11.0d 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.0d
OrcaFlex
- Video export for custom replays which include a static state stage failed with a floating point overflow error.
- Users could encounter an error with message “Attempt to read a variable that has not been logged” when requesting velocity or acceleration results for a shape object that was (directly or indirectly) held by a constraint. To trigger the bug, the constraint had to begin moving during simulation by use of the out-frame release stage data or release condition, and have only fixed degrees of freedom initially.
- When solving in the frequency domain at low frequency, the wave drift load process relies on interpolating the QTF data on wave direction relative to vessel heading. Previously the vessel’s heading in reset state was used to perform this calculation. However, the vessel’s heading after the static equilibrium has been calculated is more appropriate. This will most significantly affect vessels for which the static equilibrium has a large yaw disparity relative to the reset heading.
- Invalid floating point operation errors could be shown when performing calculations for models with lines using the slug flow contents method and that also specify the frequency domain dynamics solution method. The errors are thrown by the slug flow drawing code so a simple workaround is to disable slug flow drawing for each line that uses the slug flow contents method.
- A multithreading bug could lead to program crashes when opening multiple data files simultaneously. This has been observed when starting a batch run, but the issue could also occur when using the API to open multiple data files simultaneously.
- Slam force coefficients were not being saved to text data files for line types of the equivalent line category.
- Python post calculation actions which use user defined results previously failed with an unexpected error.
OrcaWave
- In previous versions the QTF data relating to the quadrature zone, outer circle and asymptotic zone were editable when no mesh file was supplied for the panelled zone. This was incorrect because, in models with no panelled zone mesh file, these data items are not used.
- Models that include sum-frequency QTFs may have raised a floating point overflow error message during validation. The error was most likely to occur in the first stages of model building, because it only affected models in which all the waves periods equal zero.
- Very large results files may have raised a file could not be read error when opened in OrcaWave or imported into OrcaFlex. The error occurred if an individual table within the results exceeded 2GB on disk, and therefore only affected extremely large files.
- Certain analyses of full QTFs could fail during a second-order frequency solve, while calculating the contribution of the asymptotic zone. An error message (the maximum number of subdivisions has been reached) was raised.
These bugs will be fixed in version 11.0e.