Recent updates to Sesam status

Framework: update for version 5.1-00 : Reasons for update to version 5.1-00

19 May 2026 10:00:00 GMT

This version of Framework contains both new functionality and an important bug fix.

New functionality
<ul>
<li>Minimum SCFs for weld roots
This version of Framework introduces a new functionality for defining minimum SCFs for weld root
positions. Minimum SCFs defined through following commands for axial, in-plane and out of plane
bending are applicable to fatigue analysis for the selected structure in the previous versions,
DEFINE FATIGUE-CONSTANTS AXIAL-MINIMUM-SCF
DEFINE FATIGUE-CONSTANTS IN-PLANE-MINIMUM-SCF
DEFINE FATIGUE-CONSTANTS OUT-OF-PLANE-MINIMUM-SCF
From this version V5.1-00 of Framework, above commands will only be applied to positions other than weld roots. Minimum SCFs for weld roots could be defined through following commands,
DEFINE FATIGUE-CONSTANTS AXIAL-MIN-WLDRT-SCF
DEFINE FATIGUE-CONSTANTS IN-PLANE-MIN-WLDRT
DEFINE FATIGUE-CONSTANTS OUT-OF-PLANE-MIN-WLDRT
By default, minimum weld root SCFs have a value of 1. Note that weld root fatigue is applicable to parametric SCF calculations according to Efthymiou and Lotsberg.
<li>Fatigue analysis for weld roots only
If fatigue analysis only for weld root positions is desired, user can skip rest of the positions using command:
DEFINE FATIGUE-ANALYSIS-WELD-ROOTS-ONLY ON
</ul>

Bug fixes
<ul>
<li>Licence check error when running code-checks with device-locked licence
Fixed an error that would make code-checks fail due to an error in the licence check if the user had a device-locked licence.
</ul>

GeniE: error for version 9.1-00 to 9.2-00 : Member code checks - Geometry check values showing up as 0 when opening workspace generated by older version.

9 Jul 2026 10:00:00 GMT

When opening a workspace created in an older version, V9.0-00 or earlier,
some geometry check values can show up as 0 for the member code checks.
Executing the code check will make the values show the correct values.

This issue has been addressed in the upcoming V9.2-01 release.
We recommend upgrading to V9.2-01 once it is available for download.

GeniE: error for version 9.1-00 to 9.2-00 : Some instabilities in ISO 2020 code check have been found in V9.1-00 and V9.2-00. All identified issues are fixed in V9.2-01.

26 Jun 2026 10:00:00 GMT

If commentary A13 Axial compression is unchecked, resulting axial compressive strength for cones
results in very small value. This results in higher utilization ratio for cones checked as equivalent
tubes i.e., EqTubComb. Workaround in V9.1-00 and V9.2-00 is to use the option of commentary A13 Axial
compression checked in code-check properties (it is set on by default).

Representative column buckling strength according to commentary A.13.2.3.2 being computed by two
equations depending on the range defined by smallest axial compressive strength and elastic buckling
strength. Cases where the ratio of these two terms exceed 1.34, GeniE will most likely pick A.13.2-2.

RP-C202 checks for large diameter pipe members in ISO 2020 includes the hydrostatic pressure effects
even for members which are flooded. This might result in higher utilization for members without
hydrostatic pressure.

When checking the utilization of a conical transition (13.6-21), GeniE does not show a single result anymore,
it now shows the results for both cone and tubular side. If the code check is run in a version where single result
is calculated (V9.0-00 or previous), then opening the database in 9.1-00 or 9.2-00 will not display the results for
13.6-21. The workaround is to rerun the code check once.

All the reported issues have been addressed in the upcoming V9.2-01 release.
We recommend upgrading to V9.2-01 once it is available for download.

GeniE: error for version 9.1-00 to 9.2-00 : Some instabilities in NORSOK 2022 code check have been found in V9.1-00 and V9.2-00. All identified issues are fixed in V9.2-01.

26 Jun 2026 10:00:00 GMT

For saved report of NORSOK 2022 joint checks, all joints are classified as 100%YT. The GUI results
are still correct. The observed issue is in the report saving only.

Uf7_3 (Eq.7.3) for member check and ufHoop (Eq. 7.16) for cone check are switched to 0,
after a saved database is reopened. Work around in V9.1-00 and V9.2-00 is to re-execute the
code check.

All the reported issues have been addressed in the upcoming V9.2-01 release.
We recommend upgrading to V9.2-01 once it is available for download.

GeniE: error for version 9.1-00 to 9.2-00 : Inconsistent results for formula C202-3.1.1 due to hydrostatic pressure on flooded members

12 Jun 2026 10:00:00 GMT

Large-diameter pipes checked according to DNV-RP-C202, Section 3.1.1, may show higher utilization factors.
This inconsistency arises from the fact that when a member is exposed to hydrostatic pressure but is flooded, the contribution from hydrostatic pressure is still included, which may result in higher utilization for that member.
This issue will be fixed in the next GeniE version. Previous GeniE versions provide correct results.
Internal reference 765885

GeniE: update for version 9.2-00 : Reason for updates to version 9.2-00

12 Jun 2026 10:00:00 GMT

Enhancements and Bugfixes - detailed information is found in the release notes:

https://sesam.dnv.com/status/genie/status/GeniE_V9_2_00_Release_Notes.pdf (pdf document)

After installing GeniE you may also access the release notes from the online help pages.

Compatibility:

- Versions of other Sesam applications that should be used with this version of GeniE. See the release notes .pdf file link above.

- The database file format (GNX file) used for this version of GeniE is kept upwards compatible with subsequent GeniE versions.

- There is a feature introduced in GeniE V8.2 called Dual Assembly, which is available as an option when creating a new workspace:

* With the Dual Assemby enabled, old JS files are normally not compatible for stiffened shell models.

* Old GNX and XML files can be imported into a database with Dual Assembly enabled.

* New GNX and XML files created with Dual Assembly can also be imported into a database with Dual Assembly disabled.
However, any Plate Seams (and Plate Segments) will then be lost, since they are only available with Dual Assembly.

- The workspace export (GNX file) from V7.2-07 and later may be imported into this version of GeniE.

HydroD: update for version 9.0-02 : Reasons for update to version 9.0-02

22 Jun 2026 10:00:00 GMT

Release V9.0-02 is a cycle update of version 9.0 with dependency maintenance updates only.

Release notes:
https://sesam.dnv.com/status/hydrod/status/hydrod_releasenotes_9.0.2.pdf

HydroD: limitation for version 7.4-01 to 9.0-01 : Inconsistent State of Shared Components

19 Jun 2026 10:00:00 GMT

In certain upgrade scenarios, installing version 7.4-01 or 9.0-01 over a newer one may lead to inconsistencies within retained background components, potentially affecting system stability.
(US767247)

HydroD: error for version 9.0-01 : Loading GDF file is slow

15 Jun 2026 10:00:00 GMT

HydroD 9.0 is very slow when reading .gdf files generated by Wadam for the control surface method. While loading a .gdf file, HydroD and File Explorer may appear frozen.
(BUG766637)

HydroD: error for version 6.0-00 to 9.0-01 : HydroD crash for automatic generation of pressure area elements

15 Jun 2026 10:00:00 GMT

HydroD may crash during automatic generation of pressure area elements. This may happen in cases where two beams are overlapping and included in the Morison model.
(BUG720423)

HydroD: error for version 9.0-01 : Several columns in LoadingCondition compartments .csv file are incorrect

15 Jun 2026 10:00:00 GMT

The table in the LoadingCondition compartments .csv file contains several columns that have incorrect titles or are misaligned. To be more specific, the "bug" is that the columns "FreeSurfaceCenter", "CenterOfGravity", and "CenterOfVolume" are included in the csv file. These results are covered by the columns CenterOfGravityX, CenterOfGravityY, etc.
(BUG720191)

HydroD: error for version 7.3-01 to 9.0-01 : Infinite error message loop when loading SectionModel with unsupported file type

15 Jun 2026 10:00:00 GMT

If a user attempts to load a SectionModel with an unsupported file type (e.g. .FEM), the application enters an infinite loop that continuously outputs error messages to the output window, preventing it from exiting and causing a constant "Updating.." state. The user cannot exit the application gracefully.
(BUG715483)

HydroD: error for version 5.0-06 to 9.0-01 : Inaccurate failure message during compartment fluid adjustment

15 Jun 2026 10:00:00 GMT

When the option to adjust filling of compartments is in use and the program is not able to find the equilibrium, an inaccurate message is given to the user. For example, if the number of adjustable compartments or groups is specified as 3, the program will report that at least 4 adjustable compartments/groups must be specified. This may not be correct. Actually, the program is unable to find filling fractions of the adjustable compartments that balance the loading condition. The solution may be to mark other compartments as adjustable or increase the number of adjustable compartments.
(BUG690780)

HydroD: error for version 6.1-01 to 9.0-01 : Sets do not work with exported FEM from CombinedElementModel

15 Jun 2026 10:00:00 GMT

If the option to export to FEM is used from a CombinedElementModel, and then a new ElementModel is created based on this FEM file, the program will report an error message that the list of sets does not exist in the FEM file.
(BUG626388)

SesamConnector: update for version 2.2-00 : Reason for updates to version 2.2-00

18 May 2026 10:00:00 GMT

Reasons for update:
Dependency updates.

SesamCore: update for version 5.3-00 : Release of Sesam Core 5.3-00

20 May 2026 10:00:00 GMT

This version of Sesam Core contains both new functionality and other important improvements.

*** IMPORTANT CHANGE ***
<ul>
<li>Sestra must be installed separately
For workflows requiring Sestra finite-element analysis, Sestra 11.2-00, or later, must be installed separately on the system. Sestra is no longer bundled with the Sesam Core installation.
</ul>

New functionality
<ul>
<li>Improved performance and reduced memory consumption
In a Response Reconstruction workflow performance and memory consumption are improved by the use of optimized storage of precomputed data in .bin-files. The program also has backward support for any existing precomputed .SIN files. The new convert command enables conversion from .SIN to .bin. See the user manual for further details.
<li>Support for "smart" load combinations in ULS analyses
Sesam Core now supports smart load combinations (RDRESCMB, generated by GeniE) when performing ULS analysis (bucking or yield) based on a Sesam Results Interface File (-p option)
</ul>

Bug fixes
<ul>
<li>JNL file path resolution error handling
When an UlsCommandFile path was specified in the input JSON but the file did not exist, Sesam Core silently fell back to a default RUN BUCKLING-CHECK command, masking the user's intent. Sesam Core now fails with a descriptive error message when the specified JNL file cannot be found. The default command behaviour when no UlsCommandFile is given is preserved.
<li>[RP-C201] Method 2 effective width — transverse stress zeroing for stiffener check
When ASSIGN EFFECTIVE-WIDTH-METHOD 2 was active, the transverse design stress Sigmay,Sd was incorrectly propagated to downstream stiffener criteria (plate resistance, torsional buckling, interaction formulas, laterally loaded plate), causing double-counting of transverse effects. Sesam Core now zeroes all transverse stress quantities when Method 2 is active, ensuring consistent results across all criteria and output channels. A pre-existing numerical trap (division by zero in torsional buckling when all stresses are zero) has also been resolved. The Method 2 slenderness parameter has been corrected from stiffener length to stiffener spacing per DNV-RP-C201.
</ul>

SesamWindManager: update for version 8.1.0 : Reasons for update to version 8.1.0

27 Oct 2026 10:00:00 GMT

It is recommended to use the following Sesam versions (or later) with this version of Sesam Wind Manager:

Waja V8.0-04
Splice V9.1-00
Sestra V11.1-00
Framework V5.0-03
Xtract V7.0-01
Wasim V8.0-06
Sesam Core V5.2-00
Wadam V11.0-05
Application Version Manager 4.1.0
Windows 11 is being supported.

Highlighted features:

Acceleration Loads from Mass Matrices:
The analyses in Sesam Wind Manager will now, by default, include acceleration loads from the mass matrices due to acceleration fields (e.g., gravity).
If these loads are in the load vectors, then they will be included twice in the analysis.
The user should either remove the corresponding loads from the load vectors or remove the ELOP command from the Sestra input file.

New features introduced in this release:
User Story 737883: Start Floating Result accumulation Only from command line
User Story 737884: Start Fixed ULS Result generation Only from command line
User Story 739515: Added gravity constant to Wajac input template files
User Story 740553: Allow whitespace in folder name for FOWT workspaces
User Story 742467: Supporting acceleration loads on mass matrices

Bug fixes associated with this release:
Bug 660961: Parallel number of analyses is limited cannot be changed.

This version of Sesam Wind Manager (V8.1) uses the new licence system.
For detailed instructions and further information visit: https://mysoftware.dnv.com/knowledge-centre/sesam/licence-support/ Licence support My DNV Software is DNV’s online portal for our latest software products and downloads, comprehensive user documentation, and support and training information.

Issues and limitations known to exist in this release:
Limitation: All models and input must be in SI base units.
Limitation: In Fixed OWT workspaces FLS and ULS results will only be calculated for beams. Conversely, in Floating OWT workspaces FLS results will only be calculated for plates. In all cases the structural model may include beams, shells and solids.
Limitation: No support rigid links can be included in the model when superelement conversion is performed. In case of an integrated design approach, the Sesam to Bladed converter will also ignore the support rigid links. In both cases, a bicycle wheel approach can be used instead, i.e. to model the rigid connection using stiff, massless beams.
Limitation: The maximum length of a file path in Microsoft Windows is limited to 255 characters. This also applies to runs uploaded to the cloud. Due to additional folders present on the cloud, runs may fail due to too long filepaths. Sesam Wind Manager will notify the user about this before it occurs. A workaround is to shorten the load case name(s) and/or T1.FEM file prefix before starting a cloud job.
Limitation: Specific characters in the file path can cause issues opening files or running some Sesam modules. Therefore, we suggest avoiding the following characters in the workspace path: ~^()[];,
Limitation: There are no applied (line) loads written to the R1.SIN file by the Bladed to Sesam converter (and these are not output by Bladed either), which may cause inaccurate results in Framework for FLS/ULS checks for positions that are not at node locations. A workaround to this is to use a denser mesh in Bladed to make sure that a node exists at locations of interest that would otherwise have been along the element, so that results are output at those locations too.
Limitation: For superelement generation in Bladed or BHawC format, DLCs with different water depth than defined in the Global Settings and/or Wajac input different than default (i.e. any other file than Wajac.inp) will generate wave load files that are not strictly based on the superelement matrices as obtained in the SuperElementData.dat file. If desired, an additional SuperElementData.dat file per other depth and/or Wajac input file can be generated by changing the default depth (on the Global Settings tab) and Wajac input file and running a superelement conversion.

Sestra: limitation for version ALL : Multiple INRF cards are not supported by Sestra 11

19 May 2026 10:00:00 GMT

Sestra 11 do not support multiple INRF cards. If multiple INRF cards are provided in sestra.inp, the system processes only the latest INRF card.
(764162)

Sima: update for version 5.2.0 : Reasons for update to version 5.2.0

8 Jul 2026 10:00:00 GMT

Release notes:
https://sima.sintef.no/docs/5.2/releasenotes/sima52/release_notes_520.html

Wadam: new feature for version NEXT : Expose several WAMIT options

21 May 2026 10:00:00 GMT

HYDPOTT card is extended to accommodate the following WAMIT options
which users can control. Previously, these options were decided
internally in Wadam and not exposed to users.

IHASK, 17th field of HYDPOTT. Option to use Haskind formulation for
excitation force or integral of diffraction pressure.
= 0 - Default, Wadam will decide
= 2 - Excitation force in G file evaluated from Haskind formulation
(from WAMIT_5S.2)
= 3 - Excitation force in G file calculated from integral of
diffraction pressure (from WAMIT_5S.3)

ISOR, 18th field of HYDPOTT card. Option to control if source strength
will be solved. This relates to ISOR input given to .POT.
= 1 - Enforce ISOR to be 1 in .POT, so that source strength will be
evaluated.
= 0 - The default value, let Wadam decide if source strength needs to
be evaluated.

ISCATT, 19th field of HYDPOTT. Option if scattering potential will be
solved. This relates to ISCATT input given in config.wam (to POTEN).
= 1 - Enforce ISCATT to be 1 in .POT, so that scattering potential
will be evaluated.
= 0 - The default value, let Wadam decide if scattering potential
needs to be evaluated. In most cases, scattering potential is NOT
needed. Instead, the total diffraction force (integral of
scattering + FK pressure) is calculated which is more numerically
beneficial.

IOBPK, 20th field of HYDPOTT. Option to solve offbody point
kinematics. This relates to IOPTN(6) and IOPTN(7) given in .FRC input
file. Conflict could occur if the input is not 0.
= 1 - 1 will be given to IOPTN(6:7) with potential formulation.
= 2 - 2 will be given to IOPTN(6:7) with source formulation. This
requires ISOR=1.
= 0 - The default value, let Wadam decide which value to be used.

(FEATURE 694579)

Wadam: new feature for version NEXT : Z offset for reference point in multibody analysis

21 May 2026 10:00:00 GMT

ZB of HYDSTRID card for multibody analysis (22nd field) has always been
zero (hard-coded from HydroD). It is now possible to specify the z
level from the waterline, and the forces and matrices will be output in
the G file with respect to a reference point at this z level, rather
than at z=0.

(FEATURE 750305)

Wadam: error for version ALL to 11.0-05 : Wadam run stops when many wave frequencies are combined with quadratic damping

21 May 2026 10:00:00 GMT

Wadam stops with the following error message in the list file when
there are 48 wave directions and 100 wave frequencies.

*** TRYING TO READ NONEXISTING DATA
CALL TO PGHYD WITH OPERATION CODE 2
FOR DATATYPE 110
OFFSET IN POINTER ARRAY 1400
KEY 1 SPECIFIED = 1 MAX= 100
KEY 2 SPECIFIED = 15 MAX= 48
KEY 3 SPECIFIED = 1 MAX= 1
CALLED FROM SUBROUTINE MN1462

Wadam can run through with reduced number of wave directions or
frequencies.

The bug is related to the data storage handling with legacy code
(PGHYD in Wadam). This has been replaced with modernized code using
modules and dynamic allocation.

(BUG 752535)

Wadam: error for version ALL to 11.0-05 : Restoring from W1MATRIX not considered in list file

20 May 2026 10:00:00 GMT

User defined restoring matrix can be given for a single body analysis
with HYDREST card. It can also be given by using W1MATRIX card
(with IMTYP=33 in the 6th field) for both single body and multibody
analysis. However, when W1MATRIX card is used, the HYDROSTATIC DATA
in the list file does not include the contribution from the data from
W1MATRIX card.

The printing is fixed with the following improvements.
1) Number of each user defined matrix type of HYDDMP, HYDREST, HYDCRDM
and W1MATRIX (IMTYP=33, 34 or 35) are printed
2) The restoring matrix for each body defined by W1MATRIX (IMTYP=33)
is printed

It should be noted that the bug is only relevant to the printing in
the list file. Motions are handled correctly.

(BUG 761854)

Wadam: error for version ALL to 11.0-05 : Four node integral for restoring matrix in Poten/Force

20 May 2026 10:00:00 GMT

The restoring matrix due to hydrostatic pressure on panels is calculated
using panel centroid quantities in Poten/Force. It is relevant to second
order problems (difference, sum frequencies or wave drift damping) or
when flexible modes are included, as the motions are evaluated in Force
rather than in Wadam. This is not consistent with the restoring matrix
calculated by Wadam for the first order motions where 4-node Gauss
integral is applied.

With this fix, 4-node Gauss integral is used for both linear and second
order motions.

(BUG 763060)

Wadam: new feature for version NEXT : Prescribed motion with diffraction

20 May 2026 10:00:00 GMT

HYDMOTI is extended to include the index for wave directions. With this
update, diffraction (with unit wave amplitude) is enabled with the
prescribed motions. The index to wave directions is given in the third
field of the card which was previously unused.

In addition, the ERROR message is changed to a warning when the option
of eigenvalue is combined with prescribed motion/fixed.

(FEATURE 759662)

Wadam: new feature for version NEXT : Handle multi-body cases with only one body

20 May 2026 10:00:00 GMT

It is now possible to define a "multibody" analysis with only one body.
This allows for creating results for a body with a location offset from
the global origin and with the results in its local coordinate system.

(FEATURE 119211)

Wadam: new feature for version NEXT : Vertical walls

20 May 2026 10:00:00 GMT

WAMIT has the option to account for images of the body in the presence
of one or two vertical walls (which intersect at a right angle). This
function is now exposed in Wadam by using the 21st field of the HYDPOTT
card (IWALL). The value is passed on as the symmetry indices ISX and ISY
in the GDF file(s):

IWALL=0: No wall (default)
IWALL=1: Wall at x=0 (ISX=-1)
IWALL=2: Wall at y=0 (ISY=-1)
IWALL=3: Walls at x=0 and y=0 (ISX=-1, ISY=-1)

A wall may be combined with the existing IS body-symmetry option, in
which case the GDF symmetry index becomes -2 on the affected axis. This
combination is only valid when BOTH of the following hold:

1) The body-symmetry plane is defined in the body-local coordinate
system and is distinct from the global wall plane. The symmetry
plane and the wall plane must not coincide.

2) The whole body lies within the valid region, with no wall/hull
crossing: for IWALL=3 the body must be entirely in the first
quadrant (x>0 and y>0 in the global system); for IWALL=1 entirely
at x>0; for IWALL=2 entirely at y>0. No panel may straddle a wall
plane.

If these conditions are not met, the wall and symmetry options should
not be combined.

(FEATURE 677812)

Xtract: update for version 7.0-03 : Reasons for update to version 7.0-03

20 May 2026 10:00:00 GMT

This version of Xtract contains bug fixes for license related items.

Bug fix
<ul>
<li>759353 – [License] Device-Lock License Not Working
In Xtract v7.0-01, the Device‑Lock license under the new licensing system did not function correctly.
</ul>
<ul>
<li>705396 – [License] Unable to open "T#.FEm + G1.SIF" and Animation Not Available with “XTRACT + XTRACT__ANIM” License
From Xtract v6.2 to v7.0-01, users were unable to view results or run animations for the condition “T#.FEM + Wadam G1.SIF”, even when the “XTRACT + XTRACT__ANIM” license was available.
</ul>
<ul>
<li>705400 – [License] Unable to Open “#.VTF” Files from Wasim or Stofat
From Xtract v6.2 to v7.0-01, users could not view #.VTF files generated by Wasim or Stofat when only the “XTRACT + XTRACT__ANIM” license was available.
</ul>
<ul>
<li>705423 – [License] Unable to Open “#.VTF” Files from Shell Design
From Xtract v6.2 to v7.0-01, users could not view #.VTF files generated by Shell Design when using only the “XTRACT + XTRACT__SHDS” license.
</ul>