Maxsurf 18B3 V8I Readme 29 March 2012 Release Note

Maxsurf 18b3 V8i ReadMe
Maxsurf 18b3 V8i

ReadMe 29 March 2012
This ReadMe file describes the changes in beta 3 of the Maxsurf 18 V8i suite of
software.
System Requirements:
 32-bit versions will run on Windows XP/Vista/7, and
 64-bit versions will run on Windows 7 64-bit.
Contents
Branding and Licensing changes ........................................................................................ 2
New Product Names ................................................................................................. 2
New Product Suites .................................................................................................. 3
Licensing .................................................................................................................. 3
Legacy Dongle Support............................................................................................ 3
Subscription Conversion .......................................................................................... 3
Trial Versions ........................................................................................................... 4
Splash Screens.......................................................................................................... 4
End User License Agreement................................................................................... 4
Installation Location Defaults .................................................................................. 5
Software updates ................................................................................................................ 6
Maxsurf Modeler...................................................................................................... 6
Cutting surfaces: Task – 5129........................................................................ 6
Library Changes: Task – 5091 ....................................................................... 7
New Marine Section Library: Task - 5218 .................................................... 8
Bug fixes and minor changes ......................................................................... 8
Maxsurf Stability (Hydromax) ................................................................................. 9
Partial Flooding: Task – 673 .......................................................................... 9
Cargo dropout: Task – 4798 ........................................................................ 11
Changes to Probabilistic Damage Analysis: Task – 5096 ........................... 12
Order of work in Probabilistic Damage ....................................................... 22
Planned changed to Probabilistic damage analysis ...................................... 22
Additional Graph features: Tasks– 4749, 5126 ........................................... 22
Criteria updates ............................................................................................ 23
Bug fixes and minor changes ....................................................................... 26
Maxsurf Structure (Workshop) .............................................................................. 27
Library Changes: Task – 5091 ..................................................................... 27
Maxsurf Resistance (Hullspeed) ............................................................................ 28
Maxsurf Link (Hydrolink)...................................................................................... 28
Maxsurf Fitting (Prefit) .......................................................................................... 28
Problem Reports ..................................................................................................... 28
Page 1
Branding and Licensing changes

This release is the first Bentley branded and licensed versions of the former FormSys
product Maxsurf. This section outlines some of the key issues related to this release.
New Product Names

Our product names have changed slightly to provide a clear hierarchy between the
products.
Old Name New Name

Maxsurf Plus Maxsurf Modeler
Maxsurf Pro Maxsurf Modeler Advanced
Maxsurf Stability/S Maxsurf Stability
Maxsurf Stability Pro Maxsurf Stability Advanced
Maxsurf Stability Ultimate Maxsurf Stability Enterprise
Workshop/S Maxsurf Structure
Workshop Pro Maxsurf Structure Advanced
Hullspeed Maxsurf Resistance
Seakeeper Maxsurf Motions
Prefit Maxsurf Fitting
Hydrolink Maxsurf Link
Span Maxsurf VPP
Multiframe3D Multiframe
Multiframe4D Multiframe Advanced
SectionMaker Multiframe Shape Editor
Page 2
New Product Suites

From April 1st we will be introducing 5 new suites of modules which combine together to
create a simpler portfolio of software. These will be available under the SELECT
licensing system only.
SELECT
Product Suites
Includes Modeler, Stability, Structure,
Maxsurf Suite
Fitting, Resistance, VPP and Link
Includes Modeler Advanced, Stability
Advanced, Structure Advanced,
Maxsurf Advanced Suite
Motions, Multiframe Suite, Fitting,
Resistance, VPP and Link
Includes Modeler Advanced, Stability
Enterprise, Structure Advanced,
Maxsurf Enterprise Suite
Motions, Multiframe Advanced Suite,
Fitting, Resistance, VPP and Link
Includes Multiframe, Shape Editor,
Multiframe Suite Non-Linear Analysis, Plate Analysis
and one Steel code region pack
Includes Multiframe Advanced, Shape
Multiframe Advanced Suite Editor, Non-Linear Analysis, Plate
Analysis and all Steel codes
Licensing
SELECT is Bentley’s subscription system which will supersede the FormSys
subscription system. When new users purchase Maxsurf, they will also purchase a
SELECT subscription. SELECT subscriptions have a number of advantages; including
no hardware dongle, simpler setup and floating network licensing.
Legacy Dongle Support

Version 18 of Maxsurf and Version 15 of Multiframe will continue to support our legacy
dongles. This will allow users to continue to receive the updates they are entitled to
under their existing subscriptions. These will be the last major versions to support
hardware dongles.
Subscription Conversion
From April 1st onwards, as FormSys users subscriptions expire, they will be offered a
migration option to convert to a SELECT subscription. A Bentley colleague will contact
you prior to your subscription expiration to explain your conversion options to you.
Page 3
Trial Versions
If no licences or dongles are detected, the application will run in trial mode for a period
of 15 days. During this period the application will run with full functionality however a
“Trial Use Only” watermark will be displayed on screen and on all printouts.
Once the trial period has expired, the application will no longer run.
We will no longer be supplying Demo versions and instead will supply full functionality
Trial versions.
Splash Screens
All Applications will now display a new Bentley splash screen as follows:
With the new splash screen, the first line indicates the SELECT Suite License that is in
use, while the second line indicates the Application that has been started. Legacy Dongle
users will only get the name of the Application and will not get a SELECT license
displayed.
End User License Agreement

Our End User License Agreement (EULA) has changed in this release, and is now the
standard Bentley EULA. A separate beta EULA is shown for the beta test versions.
Page 4
Installation Location Defaults

We’re now following the Bentley standards and our application is no longer stored in
C:\Program Files\Maxsurf 18\ like it was previously.
Instead we now install our applications alongside our other Bentley applications in:
 C:\Program Files\Bentley\Engineering\Maxsurf 18 V8i\ for 32-bit application

on 32-bit machines or 64-bit applications on 64-bit machines, or
 C:\Program Files (x86)\Bentley\Engineering\Maxsurf 18 V8i\ for 32-bit
version on 64-bit machines.
This change is also reflected in the Start Menu Group defaults, our applications are now
available by selecting:
Start -> All Programs -> Bentley Engineering -> Maxsurf 18 V8i
Page 5
Software updates
The following section describes the changes that have been made to the various
programs.
Maxsurf Modeler
Cutting surfaces: Task – 5129
To help facilitate designs with ever more complex surface configurations we have
introduced cutting surfaces to Maxsurf version 18. For each surface a list of “cutting
surfaces” is assigned. A cutting surface is a surface that is used to form regions to trim
to. By default each surface has all other surfaces in the design assigned as cutting
surfaces. This is traditionally how Maxsurf has worked. However the user can now
manually assign the surfaces used to trim each surface. This can greatly reduce the
complexity of trimmed designs with large numbers of surfaces.
Cutting surfaces are assigned from the Surface properties dialog or from the surface
property sheet by clicking on the “Cutting Surfaces” button.
This will load the Cutting Surfaces dialog box from which the user can check which
surfaces will be used as cutting surfaces:
Page 6
As a simple example the main hull surface (blue) in the following diagram would
traditionally have been divided into 4 trimming regions:
However if the hull surface has only the Transom surface assigned as a cutting surface
then the hull will be divided into two trimming regions only.
Library Changes: Task – 5091
To help facilitate better transfer of design data between all Marine and Multiframe
applications Maxsurf and Workshop and will no longer be using the Workshop Library
File. Instead they will now be using the Sections Library. There are a number of
advantages to this:
Page 7
1) Design information will be easily transferrable between all applications.

2) Common library editing interface across all applications.
3) Existing Section Maker application can be used for creating complex sections.
The default library is called WorkshopLibrary.slb and contains all sections and materials
in the old Workshop Library file. It is also located in the same directory. When opening
Maxsurf the default sections library will be automatically loaded. When a material is
assigned to a surface in Maxsurf, any plates added on this surface downstream in
Workshop will now be automatically assigned the surface material.
New Marine Section Library: Task - 5218
The workshop library is expanded, adding standard marine grade materials for steel,
aluminium, grp, wood, etc. to ABS, AS, ASTM, BV, DIN, EN, GL, IRS, JIS, KRS, LR,
NKK, TIS and ISO.
Bug fixes and minor changes
 Task 5157 – Importing Rhino files. As a result of the new Cutting Surfaces
functionality (outlined above) Maxsurf now defaults to no cutting surfaces for each
surface imported from a Rhino 3dm file. This makes the trimming much more
robust as the static trimming model employed by Rhino can be exactly replicated
in Maxsurf without the intersection lines of surfaces interfering with the static trim
region boundaries imported from rhino.
 Task 5134 – A third button, “select visible surfaces”, has been added to the select
surfaces dialog.
 Task 5139 – Export Moses file format has been added to the File | Export pop up
menu. This opens a dialog that allows the user to specify various variables
pertaining to the Moses file format.
 An additional option “Space evenly between perpendiculars” has been added to
the Grid Space options for sections. In addition, if the zero point is near the stern
of the vessel, default section labels will start from the stern; if the zero point is near
the bow, they will start from the bow. In both cases the station labels now start
from zero (instead of 1).
 The following menu items have been renamed in Maxsurf:
Renamed following menu items in Maxsurf:
"File|Import|DXF..." to "DXF Curves..."
"Assembly|Hide All Except Selected" to "Show Only Selected"
 A Wavefront mesh file can be exported from the rendered view in both Maxsurf and
Hullspeed. This can be used to bring the model into a rendering engine such as
Blender (www.blender.org)
Page 8
 Task 5148 – Import of the PIAS ascii text format has been added to Maxsurf. This
brings in sections of Markers which can be used to generate a Trimesh for
analysis.
 Issue 3577 – A problem which prevented files with more than 32768 markers from
being read has been fixed.
 Issue 3574 – A problem with the “Delete duplicate markers” command deleting too
many markers in some situations has been fixed.
Maxsurf Stability (Hydromax)
Partial Flooding: Task – 673
It is now possible to only partially flood a room in Maxsurf Stability. Partial flooding can
be enabled in the Case menu.
Enable Partial Flooding
With Partial Flooding enabled (and also for Water on Deck), the Damage case list
changes so that text data may be entered (rather than check boxes). Type “I” for intact
rooms, “D” for damaged rooms or specify the maximum fraction of the total room
volume that can be flooded:
Page 9
Specifying Partial Flooding
Note that:
1. the fraction specified is the fraction of the full room volume (not the fraction the final
damaged lost buoyancy).
2. The fraction specified is the maximum the room can flood, it is possible that due to the
trim and heel of the vessel that the room will not flood to this level -- remember that the
room cannot flood above the exterior waterline.
3. As with ordinary damage cases, partial flooding cases are still treated as lost
buoyancy, not as an added mass.
Remember that the lost buoyancy may be found in the Compartments results table:
Lost buoyancy volumes
Page 10
Here it can be seen that the lost buoyancy (red shaded areas) does not extend all the way to the external
waterline (yellow line)
Cargo dropout: Task – 4798
In all previous versions of Maxsurf Stability, damaged tanks were assumed to have lost
all their cargo and removed from the loadcase. It is now possible to select whether cargo
is lost or retained in damaged cargo tanks: Case | Empty Damaged Tanks menu.
In the case where “Empty Damaged Tanks” is selected, cargo is removed from damaged
tanks (as was the case with all previous versions of Maxsurf Stability). Now damaged
tanks are highlighted in Red in the Loadcase table:
However, if the option to Empty Damaged Tanks is turned off, the cargo masses of the
damaged tanks will be retained in the loadcase, but will be highlighted in red to indicate
that they are also damaged
Page 11
If the “Simulate fluid movement” option is selected, the cargo in the damaged tanks will
be shifted as the vessel heels and trims to maintain the cargo waterline parallel to the sea
waterline, as would be the case for the intact vessel.
Changes to Probabilistic Damage Analysis: Task – 5096
A range of modifications have been made to the probabilistic damage analysis in

Maxsurf Stability.
Definitions
It is useful to clarify some of the terminology used in the Maxsurf Stability
documentation:
The following definitions have been taken from MSC.216(82) and MSC.281(85):
Page 12
Room
Watertight space -- this would be a Maxsurf Stability Compartment or Tank. Note that in
Maxsurf Stability a complex tank geometry can be defined by a parent and a number of
Linked Tanks -- these Linked Tanks are considered to be joined allowing free movement
of water from one part to another (there is no requirement in Maxsurf Stability that the
individual linked parts be physically adjacent. Thu a tank made up of multiple linked
parts is considered that all parts flood (or fill) together and share a common waterline. It
should also be noted that the individual parts making up a Linked tank may have
different permeabilities (this differs slightly from the IMO definition above).
Space
We use the same definition as IMO “a combination of rooms”. Under most
circumstances, this would be a contiguous group of rooms (i.e. spatially adjacent to one
another -- though given that Maxsurf Stability linked tanks are not necessarily adjacent,
this spatial adjacency is not enforced.)
Damage
Again we use the same definition as IMO “3D extent of breach of the ship” but in the
Maxsurf Stability context the extent is always cuboid: defined by planar fwd, aft, port,
stbd, top and bottom limits. This may be a full longitudinal zone or may be limited in
transverse and/or vertical extent by longitudinal bulkheads and/or decks; there may also
be multiple adjacent zones damaged.
Damage Space
We use this definition in Maxsurf Stability to specify which rooms will be breached
when a given damage occurs.
Damage Case
A specific instance of flooded compartments for which the vessel GZ curve is to be
calculated. During the Probabilistic damage analysis in Maxsurf Stability, Damage cases
are assembled from the definition of the Damage Spaces for different combinations of
damage.
Renamed sheets
The “Zone Damage” table has been renamed “Damage Spaces” and a new table which
list all the Damage cases has been added.
Renamed “Zone Damage” table and new “Prob. Damage Cases” table
Changes form previous versions

There are two major changes from previous versions of Maxsurf Stability. These are the
way that damage is specified in the Damage Space table (previously Zone Damage
table); and automatic generation of lists of longitudinal bulkheads and decks for multiple
adjacent zones of damage. These are described in further detail below.
Page 13
Redefinition of Damage Spaces

“Damage spaces” are defined as the rooms that are wholly, or partially, contained within
a cuboid defined by three pairs of orthogonal planes: aft, forward; top, bottom; and port,
starboard. That is the rooms which will be breached if the vessel experiences damage to
the cuboid defined by the planes.
In previous versions of Maxsurf Stability damage spaces are defined:

 Longitudinally: between the fwd and aft extents of the longitudinal damage zone;
 Transversely: from the side-shell in towards the vessel centreline up to a defined
transverse boundary (longitudinal watertight bulkhead); and
 Vertically: from the baseline upwards to a defined horizontal boundary (watertight
deck).
In version 18 of Maxsurf Stability this definition has been changed so that both
transversely and vertically the damage space is defined between adjacent boundaries
(rather than in from the side-shell or up from the baseline). This will enable automatic
generation of alternative damage cases, particularly in the event where there are rooms
which span a longitudinal or horizontal boundary. However, this means that backward
file compatibility with earlier versions of Maxsurf Stability has been broken.
Due to the change of definition of the Damge Spaces, there is no case which gives the
full damage of the zone (ignoring transverse and vertical subdivision. For this reason it is
necessary to define two damage spaces: one that defines the damage due to full
transverse penetration; and a second for full vertical penetration.
Nomenclature change
A slight change in nomenclature has been adopted for Damage spaces limited by
transverse boundaries, these are listed b1, b2, etc as the penetration passes successive
transverse boundaries (longitudinal bulkheads) and the final case, for full transverse
penetration is labelled bx. Similarly, for vertical subdivision due to horizontal decks,
these are labelled H1, H2, ... Hx; where Hx it the final Damage space corresponding to
full vertical penetration.
Longitudinal bulkhead and deck definition
The generation of b-values and H-values due to transverse and vertical subdivision for
multiple adjacent zone damage from the single-zone definitions has been automated.
This means that it is necessary only to provide the single-zone values in the Long.Bhds
and Decks table.
Alternative damage for vertical subdivision: Task – 5096

Probabilistic damage requirements, as defined in Resolution MSC.216(82) and also
MSC.19(58), allude to the fact that different combinations of damage should be
considered.
Page 14
MSC.216(82) Regulation 7-2, Calculation of the factor si; p32:
This is expanded a bit in the explanatory notes:
MSC.281(85): Regulation 7-2.6; p26
The way this has been implemented in Maxsurf Stability is that alternative damage space
definitions may be made for a given damage occurrence. Maxsurf Stability will then test
the vessel under the different damage cases and select the one with the worst
survivability factor. Although it is envisaged that this will be applied to cases where
there is vertical subdivision due to horizontal watertight decks, the mechanism within
Maxsurf Stability allows for the definition of alternative damage for any damage space.
Some examples of the interpretation of this rule for single and multiple adjacent zone
damage are shown below.
Page 15
Single zone flooding to uppermost deck:

Consider damage of Zone1 up to deck H13. Then all the rooms below this deck should
be considered damaged:
But in addition, the lesser damage with C1 intact and also B1, C1 intact should also be
considered to see which gives the lesser s-factor.
Similarly, if Zone2 is considered damaged, the alternative damage cases of A2 and B2

damaged and A2 only damage should be considered to find the minimum s-factor:
Multiple adjacent zone damage

For multiple adjacent zone damage, the damage location and extent must breach both
zones. But the vertical extent may be varied. Zones 1 and 2 damaged up to deck H13
(=H22) gives four alternative damage cases that should be considered to find the
minimum s-factor.
Page 16
Definition of alternative Damage Spaces

The alternative damage cases due to vertical subdivision by horizontal decks is created
automatically. Should you wish for a certain damage case not to be evaluated, this can be
achieved by deselecting the appropriate row in the Damage Case sheet. If all alternative
damages should be excluded, this can be easily done with the option in the Global
Probabilistic Damage table:
Alternative damage results

In the results, the alternative damages tested are shown. The damage case which gives
the smallest s-factor is listed first and the alternatives shown below (in grey). The p, v, r
values which are the same, are not repeated; the A-factor is given only for the damage
case with minimum s-factor.
Page 17
Alternative damage cases tested
Probabilistic Damage Cases sheet

A new sheet which allows review of all the damage cases to be evaluated during the
probabilistic damage analysis has been added. Note that some damage cases may not be
evaluated for all load cases. This could be because of minimum probability or maximum
damaged length constraints or the fact that the watertight deck is below the upright,
intact waterline for a given loadcase. If desired, it is possible to prevent selected damage
cases from being evaluated. Because of the number of different damage cases, the data is
shown transposed compared with the normal damage case presentation with one row,
rather than a column, for each damage case.
The cases are generated from the damage space definition using the “List Prob.dam
cases” or by running the analysis.
Page 18
Log file changes

A number of changes have been made to the log file
Key points results
The Key points results table is now added to the log file just after the tabulated GZ data:
Alternative damage: min. s-factor

In the log-file the different damage cases within the zone-damage set will be listed if
there is more than one to be tested. The Maxsurf Stability will generate a GZ curve for
each of the damage cases and find the one that gives the minimum survivability factor:
List of damage sets that will be examined.
Once the s-factors of all the damage cases have been evaluated, the lowest is selected and
reported (all are listed in the log file):
Page 19
The minimum survivability factor is found from the different damage sets tested.
Because of the reuse of previously calculated GZ curves, analysis of all the extra cases
does not necessarily increase the overall computational time too significantly.
Reuse of results:
Maxsurf Stability now checks to see if it has already calculated a GZ curve for the
required loadcase and damage combination, this speeds up the calculation since repeat
calculations of the GZ curve for the same conditions are avoided.
In the log file a summary of all the conditions tested are listed at the end of the analysis
of each loadcase:
Normally in the log file, the GZ curve data is given after it has been calculated, followed
by the evaluation of the s-factor criterion:
However, if the condition has already been evaluated, just the summary data are given:
Page 20
Key point results table included in log file: Task – 5156

The key points results table giving downflooding angles of key points and key lines is
now included in the prob.dam log file.
Displacement at subdivision draft: Task – 5128
For passenger vessels, the “Displacement at subdivision draft” automatically updates to
the displacement at the current prob.dam. loadcase (and is updated in the criterion
automatically) and cannot be specified directly. The current prob.dam loadcase can be
changed by clicking in the corresponding cell:
Automatic updating of “Displacement at subdivision draught”
Probabilistic Damage References

Resolution MSC.216(82) – MSC 82/24/Add.1 ANNEX 2: ADOPTION OF
AMENDMENTS TO THE INTERNATIONAL CONVENTION FOR THE SAFETY
OF LIFE AT SEA, 1974, AS AMENDED. IMO. December 2006.
Page 21
Resolution MSC.281(85) – MSC 85/26/Add.1 ANNEX 22: EXPLANATORY NOTES

TO THE SOLAS CHAPTER II-1 SUBDIVISION AND DAMAGE STABILITY
REGULATIONS. IMO. December 2008.
MSN 1715 (M): Subdivision and Damage Stability of Cargo Ships of

80m in Length and Over. Marine and Coastguard Agency, UK. March 1999.
Order of work in Probabilistic Damage
Because of the various dependencies of the setup for the probabilistic damage analysis, it
is helpful (and will reduce rework) to follow a reasonably structured approach to setting
up the analysis.
Damage space definition
It should be remembered that the parent damage spaces are generated automatically as
the damage zones, longitudinal bulkheads and decks are defined.
Damage Case generation
The “List Prob.dam. cases” function deletes all existing probabilistic damage cases and
regenerates the list based on the new Damage Space definitions and all damage cases
will be turned on for evaluation. For this reason, if some modifications have been made,
it is worth copying the existing table to a spreadsheet before using this command.
Planned changed to Probabilistic damage analysis
There are a number of planned modifications and updates to the probabilistic damage
analysis which have not yet been completed. These are features that are currently under
development and will be implemented in the coming months.
Progressive flooding and Intermediate stages of flooding
We are currently working on implementing analysis of intermediate stages of flooding
(where rooms can be partially flooded: i.e. the damaged waterline in the room is below
that of the exterior sea-surface). As with current damaged analysis, the lost buoyancy
method will be used. Progressive flooding analysis will allow the flooding from one
room to another; when the intermediate flooding has been implemented, it will be
possible to fully or partially flood rooms sequentially for progressive flooding analysis.
Currently there are no immediate plans for time-domain simulation of flooding which
account for the rate of inflow into damaged rooms.
Additional Graph features: Tasks– 4749, 5126
The right-click pop-up menu in the Graph view now allows graph labels and annotations
to be turned off:
Page 22
Visibility of graph labels and annotations can be toggled
A Graph options dialog has been added, this allows some control over the number of
gridlines displayed (Right-click | Graph options):
Gridline density can be controlled
Furthermore, “Show Legend” has become a single toggle menu item, rather than two
separate menu items.
Criteria updates
Freeboard at Equilibrium with heeling arm – Task 5220

A new criterion which looks at the freeboard of any type of key-point or key-line at the
equilibrium angle of heel with a heeling arm has been added. This is available as a cross-
referenced heeling arm criterion; a stand-alone heeling arm criterion and a multiple-
cross-referenced heeling arm criterion:
New freeboard criterion
Page 23
Angle of Immersion criterion

A new generalised “Angle of Immersion” criterion has been added. This criterion allows
the immersion angle of any type of key point (downflooding, potential downflooding,
etc) to computed; auto-complete is used to specify which type of key point should be
used:
New Immersion Angle criterion
MSC.19(58) s-factor criterion

Two optional checks have been added to the MSC.19(58) s-factor criterion. These allow
for checking of immersion of key points and or key lines at equilibrium. Auto-complete
is used to specify which type of point / line should be used. The check of “immersion at
equilibrium” is done by checking that damaged equilibrium heel angle (as found by the
first up-crossing of the GZ=0 axis by the GZ curve) is less than the angle of immersion
of the selected point / line types; should this test fail, the s-factor is set to zero.
Additions to the MSC.19(58) criterion
Page 24
MSC.216(82) Survivability criterion

The MSC.216(82) Survivability criterion for passenger ships has had some minor
modifications. This means that if "intact displacement at subdivision draught" is zero,
then use loadcase displacement will be used. Also the criterion now, where possible,
extract Heeling Moments directly from the cross-referenced heeling arms; this means
that there the Heeling Moments listed for the s-moment calculation are more transparent.
Intact displacement at subdivision draft = zero, indicates that loadcase displacement should be used
Where possible, heeling moments are obtained directly from the cross-referenced heel arm calculations and
depend on neither the loadcase displacement nor the displacement specified in “intact displacement at
subdivision draught. This displacement is, however, used to evaluate the s-moment survivability factor.
Range of positive stability checks: Task – 5135

When required, Maxsurf Stability now performs more thorough checks to ensure that GZ
is positive in the determined range of positive stability.
Page 25
 Probabilistic Damage Space (zone) boundaries can now displayed in the rendered
view.
 Task 5189 – The loadcase type (Loadcase or Loadgroup) can be accessed through
the COM automation interface.
 The tank loadings in loadcases can be now be specified by ullage and sounding
through the COM automation interface.
 Task 5183 – The KN draft range can now be accessed through the COM automation
interface.
 Task 5179 – The graph tracker hair is hidden when copying graphs using the COM
automation interface.
 Task 5127 – Survivability criterion: if "intact displacement at subdivision draught"
is zero, then use loadcase displacement. Also "moments" are extracted directly
from heeling arms where possible (rather than calculating from HA*disp.
 Task 1445 – The Loadcase and Compartment Definition tables now "Add" items
below current selection.
 Issue 3719 – Correctly calibrate Compartments which contain NLCs due to
intersections with tanks. Previously (for calibration analysis of compartments only)
the NLC volume was being added rather than subtracted.
 Issue 3717 – KN calculations at specified drafts and non-zero trim now calculated
the KN values for the vessel at the requested drafts (previously KNs were correct,
but at drafts different to those specified, if the vessel was at non-zero trim).
 Issue 3714 – A problem with the calculated waterline length and coefficients of
form if hull surfaces were not visible has been fixed.
 Some issues with the number of x-axis gridlines in the GZ curve have been fixed.
 The “Damage Conditions” table, where normal damage cases are defined has been
renamed the “Damage Cases” table
Page 26
 Maxsurf Stability is more tolerant when loading a GHS file with missing data
 If a design is already open , it is possible to load just the tanks from a GHS file in to
Maxsurf Stability; the Compartment definition window should be active to do this.
 Some minor issues with the COM interface in to the probabilistic damage results
have been fixed.
 Task 5153 – It is now possible to set “Flood from” and “Linked to” for Potential
Downflooding, Immersion and Embarkation points as well as Downflooding points.
Points that are “Linked to” a room (tank or compartment) are ignored it that room
is already damaged in the current damage case; points that are “Flood from” are
ignored if that room is intact in the current damage case.
 New damage cases are now inserted after the current selection. Ctrl+A can be used
as a short-cut to add damage cases.
 Issue 3576 – A problem which inverted the top/bottom and port/starboard tank
limits when using the “Add tank from surfaces” command has been fixed.
 A problem which sometimes occurred when reading a model containing WoD data
and negative linked compartments has been fixed.
 Make non-ultimate versions not remove Probabilistic Damage data from files.
 An error in the 216(82) criterion input table for "displacement at subdivision
draught" being parsed as a moment, and not a mass, has been fixed.
Maxsurf Structure (Workshop)
Library Changes: Task – 5091
To help facilitate better transfer of design data between all Marine and Multiframe
applications Maxsurf Structure and Maxsurf Modeler will no longer be using the
Workshop Library File. Instead they will now be using the same Sections Library used
by Multiframe. There are a number of advantages to this:
1) Design information will be easily transferrable between all applications.

2) Common library editing interface across all applications.
3) Quick and easy addition of new standard sections and materials to the library.
4) Existing Section Maker application can be used for creating complex sections.
5) Removal of Library window from Maxsurf Structure.
When an old design is opened up in version 18 the user will be asked to locate the
workshop library file the design was created with, sections or material not in the
currently open sections library will be automatically merged in. This will only occur
once when the file is upgraded. If a user has a Maxsurf Structure library file with custom
shapes and cutouts this can be upgraded to a Section Library file using the Convert
Library function from the File menu.
The default library is called WorkshopLibrary.slb and contains all sections and materials
in the old Workshop Library file. It is also located in the same directory. When opening
Maxsurf Structure the default sections library will be automatically loaded.
Page 27
 Task 5210 – When adding a plate the default material and thickness will be set to
that of the underlying surface
 Task 5077– Multiple stringer points can now be dragged in design views. To do
this select all the points you wish to drag (via a section rectangle or holding the
shift key down) then click and hold the left mouse button on the “parent” stringer
point and drag.
 Task 5086– On exporting parts to a Multiframe design, only currently visible parts
will now be exported.
Maxsurf Resistance (Hullspeed)
 Issue 3718 – The “Render transparent” option has been removed as this caused a
crash under some circumstances.
 Task 5101 – Only relevant columns in the slender body group data dialog are now
visible.
Maxsurf Link (Hydrolink)
 Task 5148 – Export to the PIAS ascii text format has been added to Hydrolink. Also
ensure that the PIAS export always uses "." as decimal delimiter (independent of
regional settings).
Maxsurf Fitting (Prefit)
 Issue 3734 – A problem of scaling the Inset Section-Control Box in the Body-Plan
view has been fixed. In addition section ordering for Prefit now starts from the
stern rather than the bow.
Problem Reports
We greatly appreciate any bug reports or suggestions you may have. Please report any
bugs or anomalies you find to:
Email: support@formsys.com
Page 28

Maxsurf 18B3 V8I Readme 29 March 2012 Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maxsurf 18B3 V8I Readme 29 March 2012 Release Note

Uploaded by

Copyright:

Available Formats

Maxsurf 18b3 V8i ReadMe

Maxsurf 18b3 V8i

Branding and Licensing changes

New Product Names

Old Name New Name

New Product Suites

Legacy Dongle Support

End User License Agreement

Installation Location Defaults

 C:\Program Files\Bentley\Engineering\Maxsurf 18 V8i\ for 32-bit application

Cutting surfaces: Task – 5129

Library Changes: Task – 5091

1) Design information will be easily transferrable between all applications.

New Marine Section Library: Task - 5218

Bug fixes and minor changes

Maxsurf Stability (Hydromax)

Partial Flooding: Task – 673

Enable Partial Flooding

Specifying Partial Flooding

Lost buoyancy volumes

Cargo dropout: Task – 4798

A range of modifications have been made to the probabilistic damage analysis in

Changes form previous versions

Redefinition of Damage Spaces

In previous versions of Maxsurf Stability damage spaces are defined:

Alternative damage for vertical subdivision: Task – 5096

MSC.216(82) Regulation 7-2, Calculation of the factor si; p32:

This is expanded a bit in the explanatory notes:

MSC.281(85): Regulation 7-2.6; p26

Single zone flooding to uppermost deck:

Similarly, if Zone2 is considered damaged, the alternative damage cases of A2 and B2

Multiple adjacent zone damage

Definition of alternative Damage Spaces

Alternative damage results

Alternative damage cases tested

Probabilistic Damage Cases sheet

Log file changes

Alternative damage: min. s-factor

List of damage sets that will be examined.

Key point results table included in log file: Task – 5156

Automatic updating of “Displacement at subdivision draught”

Probabilistic Damage References

Resolution MSC.281(85) – MSC 85/26/Add.1 ANNEX 22: EXPLANATORY NOTES

MSN 1715 (M): Subdivision and Damage Stability of Cargo Ships of

Visibility of graph labels and annotations can be toggled

Gridline density can be controlled

Freeboard at Equilibrium with heeling arm – Task 5220

New freeboard criterion

Angle of Immersion criterion

New Immersion Angle criterion

MSC.19(58) s-factor criterion

Additions to the MSC.19(58) criterion

MSC.216(82) Survivability criterion

Range of positive stability checks: Task – 5135

Bug fixes and minor changes

Maxsurf Structure (Workshop)

Library Changes: Task – 5091

1) Design information will be easily transferrable between all applications.

Bug fixes and minor changes

Maxsurf Resistance (Hullspeed)

Bug fixes and minor changes

Maxsurf Link (Hydrolink)

Bug fixes and minor changes