Orcaflex 11.4D
New in version 11.4d
Bug fixes

    Spurious tracked changes would have appeared in the depth column of the profiled seabed data table when opening a text variation or restart file.
    An access violation error may have arisen when opening a data form after loading a variation model or restart analysis from a binary data or simulation file created by version 11.1.
    End B of a prescribed statics line could never begin a dynamics only restart analysis from its calculated position at the end of the parent analysis. Normally, this state would be inherited if the end B position data were unchanged between the parent and child analyses, but this was impossible to arrange for this particular case.
    Setting integer data items using variables in a text data file would sometimes fail, with an unexpected program error.
    Exported spreadsheet files with .xlsx format could sometimes contain sheet names that were not valid Excel sheet names. These files could not be opened by Excel. Excel sheet names must be no more than 31 characters long, must not start or finish with ', and must not contain any of the following characters: / \ ? * : [ ]. Any such sheet names are now normalised before being exported, with invalid characters being replaced by the _ character.
    Dynamics only restart analyses would not run for models with winches whose statics control mode had been changed relative to the parent analysis.
    Running a line feeding model with an open range graph could sometimes result in an access violation error.
    The default value of the vessel characteristic force (the value used when the characteristic force has been set to ~) was being calculated from the vessel type properties without correctly accounting for Froude scaling. This would only have affected vessels whose length was not ~.
    A small correction has been made to the stiffness Jacobian associated with vessel wind loading. This only affects frequency domain analysis and its influence on results is expected to be very small.
    Line contact force results were reported incorrectly for protected line nodes whose contact diameters are greater than that of the corresponding stiffener line node. In this scenario the contact force was always reported as zero, even if it was non-zero. The bug only affected the reporting of results. The contact forces used by the analysis were correct, even though they were reported incorrectly.
    Line seabed normal resistance and seabed normal resistance/D results did not account for the bespoke seabed contact properties of seabed sections. The bug only affected the reporting of results. The seabed contact forces used by the analysis were correct, even though they were reported incorrectly.
    In a restart analysis, connecting an existing object to a newly-added (i.e. added as part of the restart) constraint may not have worked as expected, and the existing object may have ended up in the wrong position.
    Models using expansion tables would sometimes raise an access violation error. This would happen if any line using an expansion table also used one of the following features: externally calculated applied loads, externally calculated stiffness data, stiffness external results or hysteretic bend stiffness.
    Results for restart chains, when using mid-simulation restarts, could sometimes erroneously include results for additional sample times. These additional results samples would be from the parent simulation, for times after the restart from time, and would overlap with times from the restart.