maxsurf connect edition v21.10.00 readme 26 july 2017connect edition: maxsurf v21.10.00 readme 26...

CONNECT Edition: MAXSURF V21.10.00 ReadMe 26 July 2017

MAXSURF CONNECT Edition V21.10.00 ReadMe 26 July 2017

This ReadMe file describes the changes to the Modules in MAXSURF CONNECT

Edition V21.10.00

Side-by-side installation – important changes:

Note that this version 21.10 will replace version 21.02 if already

installed on your computer. Side-by-side installation of versions 21.10

and 21.02 is not possible.

Bentley versions numbers are MM.mm.sv.bb where MM is the Major version number;

mm the minor version number and sv is reserved for special versions (and bb is the build

number). From version 21.10 onwards, side-by-side installations of MAXSURF are only

possible for different major versions. When you are signed in to the CONNECTION

client, you will be notified when minor updates are available (these are updates with

different minor version numbers. If you install a minor update, the previous version with

the same major version number will be replaced with the updated version. Thus,

installation of version 21.10 will replace 21.02 but would be installed side-by-side with

19.

System Requirements – 64-bit only:

Henceforth MAXSURF and Multiframe will be available in 64bit

versions only and will only work with 64bit operating systems.

64-bit versions of MAXSURF will run on Windows 7, 8, 8.1 and 10 64-bit

operating systems only.

Copyright © 2017 Bentley Systems, Incorporated. All Rights Reserved.


Contents

Software updates ................................................................................................................ 3 All Modules .............................................................................................................. 3

720151: Specification of decimal character on Windows10 ......................... 3 681842: License Configuration dialog – available licenses ........................... 4 658671: Improved render lighting with specular reflections ......................... 6 658416: Bentley CONNECT Advisor ........................................................... 6 Automatic Updates ........................................................................................ 8 CONNECT Licensing .................................................................................... 9 Bug fixes and minor changes ....................................................................... 10

MAXSURF Modeler .............................................................................................. 11 New Meshing Functionality ......................................................................... 11 572098: Structure functionality implemented in Modeler ........................... 17 Bug fixes and minor changes ....................................................................... 20

MAXSURF Stability .............................................................................................. 21 723298: Margin line deleted ........................................................................ 21 696042: Probabilistic Damage – damage case creation from damage space

definition ...................................................................................................... 21 660008: Exact windage calculation enhancements and fixes ...................... 30 Bug fixes and minor changes ....................................................................... 31

MAXSURF Motions .............................................................................................. 33 Bug fixes and minor changes ....................................................................... 33

MAXSURF Structure ............................................................................................. 33 572098: Structure functionality implemented in Modeler ........................... 33

MAXSURF Multiframe ......................................................................................... 34 216957: Create circular patches and/or openings precisely ......................... 34

Problem Reports ............................................................................................................... 35


Software updates

The following section describes the changes that have been made to the various

programs.

All Modules

720151: Specification of decimal character on Windows10

Under Windows 10, we have sometimes observed some strange behavior with some

systems when overriding the “Format” default for decimal character. The problem does

not appear to manifest itself in Window 7.

We have found it best to simply select the Format required in the Windows 10 Region

dialog and not to customize the individual options in the “Additional Settings…” dialog:

Just use the Format language to set the decimal character.


Under Windows 10, using the “Additional settings” to customize the format sometimes to cause problems in MAXSURF number formatting

681842: License Configuration dialog – available licenses

Many of the MAXSURF and Multiframe Modules can run under different licenses. In

order to prevent accidental selection of the wrong license, the licenses options that are

displayed now depend on which installer was used to install the Package:


If you installed Multiframe, with the Multiframe installer, you will only see the two

Multiframe licenses:

If you installed the MAXSURF Package (which also includes Multiframe), you will

not be shown the Multiframe license options:

These changes have been made to help prevent accidental selection of the wrong license.

However it is possible to always display all license options by setting the following flags

in the registry to “1”: _MFpack is for the Multiframe Package licenses; _MSpack is for

the MAXSURF Package licenses and _MSsaln is for the MAXSURF standalone licenses

for Modeler Advanced, Stability Advanced and Stability Enterprise.


658671: Improved render lighting with specular reflections

A specular component has been added to the material properties used for rendering; this

increases the shininess of the model.

Older (top) and new (bottom) rendering with increased specular reflection

658416: Bentley CONNECT Advisor

The “Bentley CONNECT Advisor” is now available from the Help menu in all

applications. The CONNECT Advisor can be used to search for help from a variety of

sources (you must be signed in to the CONNECTION Center to use the CONNECT

Advisor).

Bentley CONNECT Advisor is easy to use, just search using relevant terms, Boolean

expressions can be used to refine search results. Content is available from the resources

shown below, results can be sorted and filtered, favorites can be saved. Click on the help

icon at the top right for a comprehensive guide.

To find relevant Bentley learn videos, users can:

Filter by text;


Sort the contents by date or title;

Select certain content type to display etc.

Bentley CONNECT Advisor also has options to list additional categories including

future events:

To use Bentley CONNECT Advisor you must be logged into the CONNECTION Client.

This does not require a SELECT subscription, only registration as a CONNECTED User.

For more information on that please see the Bentley Cloud Services Overview.

https://communities.bentley.com/communities/other_communities/sign-in_assistance_and_web_services/w/wiki/24305.bentley-cloud-services-overview


The preferences for the CONNECT Advisor can be set in the CONNECT Advisor itself

(see below), the most useful are:

“Lunch CONNECT Advisor on startup” which controls whether the CONNECT

Advisor automatically launches with the application (or must be launched from the

Help menu).

“Keep window always on top” which controls whether the CONNECT Advisor is

always on top of the other applications.

Automatic Updates

If you have the Connection Client running and are logged-in, you can see if updates are

available for your software. You will only be notified of minor updates which can be

automatically installed by this method. In all cases update notifications will be posted via

the RSS News updates, in the Help | News dialog.


Available updates shown in the Connection Client

Important Note:

These minor updates will overwrite and replace existing versions of the

software with the same major version number. Thus update 21.10 will

overwrite an existing installation of 21.02, for example.

CONNECT Licensing

This version of MAXSURF has been tested with the new CONNECT Licensing

framework which enables real-time verification and updating of license usage. However

when using the CONNECT Licensing you may experience a slightly longer start-up time

for the application because it has to make a live, real-time connection to the license

server.

By default, the normal installation of this version of MAXSURF will use the same

existing Select licensing framework as used in previous versions of MAXSURF.


Bug fixes and minor changes

693490: The following CONNECTION functionality command names have been

changed:

“Personal Portal” is now called “CONNECTION Center”

Project Portal” is now called “ProjectWise Projects

691016: The curve-tracker cross-hair is now hidden when copying the graph

window.

681842: If you install only MAXSURF you will no longer see the Multiframe license

options; if you install only Multiframe you will no longer see the MAXSURF license

options in the License Configuration dialog.

651397: The “Service Request Manager” is available from the Help menu in all

applications (you must be signed in to the CONNECTION Center):

650562: The application name, edition and version number are now displayed in

the top of the “License configuration” dialog:

562634: Some changes have been made to improve the performance of mesh

generation.


MAXSURF Modeler

New Meshing Functionality

Significant upgrades have been made to meshing capabilities in this update. Below is a

list of new functionality:

“Weld” trimeshes function

Terminology: to “weld” two trimeshes is to ensure that the triangle edges (and hence

nodes) along the common trimesh edges are coincident. As an example, the two images

below illustrate two trimeshes, a deck and a hull trimesh, before (top) and after (bottom)

a weld operation:

This function is particularly useful for creating trimesh models for downstream analysis

applications that require the geometry to be “water tight” for analysis, for example in

MOSES. It is also useful for FEA analysis where element connectivity information is a

requirement.


A weld is usually performed on two trimesh surfaces and a curve. The curve defines the

line along which you would like the two trimeshes to be “welded”. As when generating

trimeshes a weld will ensure that the triangles from each trimesh share common verticies

(and hence triangle edges) along the contour. From the assembly tree select the two

trimeshes you wish to weld and the weld contour (holding the shift key down). The

selected contour defines the line along which the weld will occur. Next choose

“Weld…” from the trimesh menu. A dialog will appears asking the user to specify the

target edge length of the tri edges along the weld.

This function is particularly useful in cases where surfaces “just” or “almost” touch each

other and welding along the intersection line(s) doesn’t work as there is not one

continuous intersection line. An example might be a deck surface that joins the hull

surface below the gunnel, where the deck is not trimmed to the hull surface and doesn’t

form a clean intersection line (broken yellow line):

In this case a curve could be added to the deck edge by highlighting the edge and adding

a curve using the Curve | Fit Curve to Contour… command. Once the trimeshes have

been created we have th following (Note how the triangle edges to not match along the

apparent intersection):


If the weld command is then executed on the two trimeshes and the contour that was

added on the deck edge we will get triangle continuity across the weld:

A weld can also be performed on a single trimesh and curve. This generates a similar

outcome to a hotline with the main advantage being that only the triangles in the vicinity

of the weld will be altered.

“Join” trimeshes function

Two or more trimeshes can be joined into a single trimesh using the Join function from

the Trimesh menu. The function will be enabled when there is two or more trimehes in

the design:


“Delete Triangles” function

A triangle can be selected in non-rendered mode by clicking on the triangle or dragging a

selection rectangle over a group of triangles. Non-contiguous triangles can be selected

by holding the shift key down to add to the selection. Triangles can only be selected

when the trimesh is locked, when unlocked the trimesh vertices will take precedence for

selection. Selected triangle(s) may then be deleted. Either hit the delete key or select

Trimesh | Delete Triangles function from the menu.

“Remesh” triangle function

A selected set of trimeshes can be remeshed to produce a lower or higher density of

triangles. The function is executed by first selecting the triangles and then choosing

“Remesh Triangles” from the Trimesh menu. The user will then be asked to input the

desired target edge length for the remeshed triangles. This function is useful to increase

the mesh density in areas of high curvature (e.g. around bulbous bows) and decrease the

mesh density in areas of low curvature (e.g. flat of sides and bottom)

In the images below the selected triangles are remeshed from a target edge length of

1.0m to 2.0m:

“Project Curve onto Surface” function

A curve can now be projected onto a surface. This function is enabled when there is at

least one surface and at least one curve in the design. When the function is executed a

dialog will appear asking the user to specify which curve is to be projected onto which

surface and in which projection direction:


Above the deck curve is on the buttock plane offset 10m from the centerline. Below is

the curve projected onto the hull in the horizontal projection direction:

Changes to “Generate Trimesh” dialog

The user is now given finer control over which contours are used for welding:


572098: Structure functionality implemented in Modeler

From this version, all MAXSURF Structure functionality is now available in MAXSURF

Modeler. MAXSURF Structure will continue to ship with the MAXSURF Package but

will be deprecated for subsequent releases.

All functionality that is available in MAXSURF Structure is now available in

MAXSURF Modeler allowing users to generate structural parts, including plates, run

stringer paths and create frames, decks and longitudinal bulkheads.

Currently the Structure and Modeler manuals remain separate documents so help for the

Structure functionality in Modeler may be found in the Structure manual.

When opening a .msd file which has an associated .wsd file in the same directory,

MAXSURF modeler will now automatically load the associated structure. If the design

contains structural parts, MAXSURF will automatically save the parts to an associated

.wsd file (same name and directory).

New Structural parts now have an associated menu:

In addition Structure Data tables can be accessed from the Window/Structure submenu:


Export options for the structural parts are available from File | Export | Structure Parts

submenu:


The Structural part window showing plate developments, frame, deck, stringer parts and

associated functionality can be accessed via the Window | Part menu item:

The Plate development views as well as the plate strain viewing options can be accessed

via the Display menu:



730139: A Crash in the Grid Space dialog after defining 500 sections has been

fixed.

720151: A problem which sometimes occurred when editing Contour Tolerance

preference on a system with a comma as the decimal character has been fixed.

720063: A problem which could make the program unresponsive when calculating

the hydrostatics when selecting Length OA (or Beam OA) for form coefficients has

been fixed.

708640: A crash on undoing the delete operation on a trimmed rendered NURBS

surface has been fixed. Model specific.

667004: The drawing of the Diagonal grid with angle > 90 has been fixed.

651115: Option for displaying trimesh welds available from contour visibility

toolbar.

625791: Algorithmic changes to Rendering pipeline to increase performance of

large rendered models.

625139: A problem which sometimes prevented the surface material from being set

correctly in the Surface Property pane has been fixed.

571991: A problem in the Preferences dialog which sometimes changed the length

units has been fixed.


MAXSURF Stability

723298: Margin line deleted

A problem with the Margin line being deleted when recalculating sections with the

option of hiding specific sections has been fixed. The problem occurred when using the

Analysis | Recalculate Hull Sections command with the shift button held down which

gives the option of removing certain sections from the model. If this option was used the

margin line data was deleted.

The behavior has been modified so that points on the margin line on sections that have

been removed are also removed. This occurs unless the margin line data has been

modified manually; whereupon you will be prompted to recalculate the margin line or

leave it unaltered:

696042: Probabilistic Damage – damage case creation from damage space definition

I a number of problems relating to the automatic generation of the damage cases to be

tested have been addressed. These improvements are particularly related to intermediate

stages of flooding which have been added manually. In order to understand these

modifications and improvements, it is important to understand the logic behind the way

the “damage space” definitions are combined to create the damage cases to be tested.

These aspects are described in detail below.

Probabilistic damage – Review of automatic damage case generation

Because of the complexity of the way in which the damage cases are generated from the

damage space definition, it is worth reviewing the underlying procedure and logic in

some detail.

In order to complete the probabilistic damage analysis, the software needs to generate

many different damage cases corresponding to the different damage scenarios considered

during the analysis; this may involve:


combining different longitudinal zone damage in the case of considering damage

in adjacent zones;

damage in a single or multiple adjacent zones limited by transverse penetration

depth and longitudinal bulkheads;

damage limited by vertical extent of damage and decks;

alternative damage scenarios where lower rooms are not breached (damage only

above a certain deck);

intermediate stages of damage which may be defined by the user

In the following sections, we shall see how the rooms breached by a specified extent of

damage are defined in “Damage spaces” and how “Damage cases” are automatically

generated from the damage spaces.

Damage spaces

The software works by identifying “Damage spaces” which define which rooms are

breached when a certain extent of damage occurs. The extent of damage of a “Damage

space” depends on the zone, bulkhead and deck specification of the subdivision and is a

rectangular volume bounded by the single longitudinal boundaries, the adjacent

transverse penetration limits (b-values) and between adjacent vertical limits (H-values).

Longitudinal subdivision only (transverse bulkheads)

The damage cases are then generated by accumulating the damage specified in the

appropriate damage spaces. For instance, the damage case corresponding to zone 2 with

2 adjacent zone damage would have any rooms damaged if they are damaged in either of

the zone 1 or zone 2 damage spaces. We will define this as “Adding” damage spaces,

i.e. the result of adding 2 damage spaces is that a room is damaged if it is damaged in

either of the damage spaces being added.

Example of damage case for 2 adjacent zones starting with Zone 3 (i.e. “Z3, 2”) is shown

in the diagrams below:

Damage case “Z3, 2” (damage space “Z3” + damage space “Z4”) =

Damage case “Z3, 2”

Damage space “Z3” +

Damage space “Z3”




Or looking at the same thing in the Damage Space definition and resulting Damage

Cases which have been automatically generated:

(5zone-Box-Stbd-bH-sharedWL-noIntStages.msd)

Damage space definition: adding full zones with no intermediate conditions

Resulting damage cases

Transverse subdivision (longitudinal bulkheads) only within a longitudinal zone

When there are transverse limits to the subdivision (due to longitudinal bulkheads

specified by b-values) the damage spaces are between adjacent b-values. In this case

depending on the transverse penetration depth of the damage case of interest we need to

add the separate damage spaces from the side-shell to the inner longitudinal bulkhead.

Tanking the example for zone 2 with transverse extent of damage extending all the way

to the vessel centerline (damage case “Z2; bx”) the damage spaces “Z2; b1” and “Z2; bx”

need to be added together:

Damage case “Z2; bx” (damage space “Z2; b1” + damage space “Z2; bx”) =

Damage case “Z2; bx”

Damage space “Z2; b1” +


Damage space “Z2; b1”

Damage space “Z2; bx”

Damage space “Z2; bx”

Or looking at the tabulated Damage space and resulting damage case definitions

(5zone-Box-Stbd-bonly-sharedWL-noIntStages.msd)

Damage space definition with transverse subdivision and no intermediate conditions


Vertical subdivision (decks) only within a longitudinal zone

Damage limited by vertical subdivision (decks) works in a similar way. The deck heights

are specified by H-values.


In the following example the damage case for unlimited vertical damage “Z2; Hx” is

made by adding the damage in the “Z2; H1” and “Z2; Hx” damage spaces as seen below:

Damage case “Z2; Hx” =

Damage case “Z2; Hx”

Damage space “Z2; H1” +

Damage space “Z2; H1”

Damage space “Z2; Hx”

Damage space “Z2; Hx”

(5zone-Box-Stbd-Honly-sharedWL-noIntStages.msd)

Damage space definition with different numbers of intermediate conditions



Alternative “lesser” damage (undamaged below specified deck)

When dealing with the vertical extent of damage, there is also the requirement to

examine “lesser extents of damage” this is when damage does not extend all the way

down to the bottom of the deck – i.e. there are undamaged rooms below the deck in

question. These damage cases have “Alt n/N” added to the end.

In the example below, there are two alternative damage cases for “Z2; Hx” the first “Alt

1/2” is damage all the way down to the bottom of the ship and is the same as “Z2; Hx”

in the previous section. However the “lesser extent of damage” is “Alt 2/2” where the

damage does not extend below the deck at H1. Thus it contains only the “Z2; Hx”

damage space (since rooms in the “Z2; H1” are considered intact).

Damage case “Z2; Hx; Alt.2/2” = Damage space “Z2; Hx”

Damage case “Z2; Hx; Alt.2/2”

Resulting damage cases, double bottom (T-02-db) is intact because damage does not extend below H1

Combined transverse and vertical subdivision within a longitudinal zone

When combining the effects of transverse and vertical subdivision, that is the effects of

longitudinal bulkheads and decks, we need to generate damage cases which are limited

by specified b-values (longitudinal bulkheads) and H-values (decks).

To do this there are three steps:

Create a damage case for the specified b-value (limited by a longitudinal bulkhead) – see

the Transverse subdivision section described above


Independently, create a damage case for the specified H-value (limited by a deck) – see

the Vertical subdivision section described above; noting that this may also be affected by

the alternative “lesser” damage also described above.

Create the final damage case whereby damaging rooms only if the room is damaged in

both the transverse damage case (1) and the vertical damage case (2).

So in the following example we look at generating the damage case “Z2; b1; H1” i.e.

zone two, limited by b1 and H1.

Damage case “Z2; b1; H1” =

Damage case “Z2; b1; H1”

Damage case “Z2; b1” – i.e. transverse damage ignoring vertical subdivision

(in this case this is simply the damage space “Z2; b1”)

Damage case “Z2; b1”

AND

Damage case “Z2; H1” – i.e. vertical damage ignoring transverse subdivision

(in this case this is simply the damage space “Z2; H1”)

Damage case “Z2; H1”

(5zone-Box-Stbd-bH-sharedWL-noIntStages.msd)




Intermediate stages of flooding

For each damage space, it is possible to define any number of intermediate stages of

flooding; furthermore different numbers (or no) intermediate stages can be defined for

the damage spaces. When the damage cases are generated, if there are any intermediate

flooding damage spaces defined, corresponding intermediate stage flooding damage

cases will also be generated.

When considering a damage case, intermediate stage flooding damage cases will be

generated if any of the damage spaces under consideration also have intermediate stages

combined. When more than one damage space is required to generate the damage case,

the number of intermediate stage damage cases that are generate will correspond to the

maximum number of intermediate conditions defined for a single damage space. Thus the

damage case “Z2, 2” (zone 2 with 2 adjacent zones damaged) would have 3 intermediate

damage cases because there are 3 intermediate stages defined for damage space “Z2”

(and only one in damage space “Z3”). This is shown in the tables below.

(5zone-Box-Stbd-sharedWL-notSameIntStages.msd)




When the damage spaces define a shared waterline for the damage, then the flooding

level is the same in all rooms because it reffers to the total volume of all the damaged

rooms. If different partial flooding percentages are defined, then the value used is that in

the first damage space in the combination process (in the example the 75% partial

flooding in the first intermediate stage of damage space “Z2” overides the 50% partial

flooding in the intermediate stage for “Z3”.

Damage cases: corresponding intermediate stages used when defined.

A one-to-one correspondence is used when combining the intermediate stages; when

there are less intermediate cases defined for some damage spaces being combined, the

final stage flooding will be use:

Damage cases: final, fully-flooded stage is used when corresponding intermediate stages are not defined.


660008: Exact windage calculation enhancements and fixes

Some enhancements with the new exact windage calculation using specified surfaces

have been made to improve the performance. In addition, a problem which corrupted the

list of selected surfaces when a Tank Calibration analysis was run has been fixed.



730504: When running the Limiting KG analysis with fixed trim, the LCG is

irrelevant because there is no longitudinal balance during the GZ curve calculation.

However, with non-zero fixed trim, there was an error in the reported upright LCG

because it was not adjusted for the longitudinal change of CG due to trim CG

height at the final limiting VCG. This has now been fixed. (It should be noted that

the values of limiting VCG were correct and remain unchanged.)

720063: A problem which could make the program unresponsive when selecting

Length OA (or Beam OA) for form coefficients has been fixed.

708665: When exporting models in GHS format, compartments now have a fluid

labelled “COMPARTMENT” and with a s.g. of 1.0 associated with them (previously

is was “SEA WATER” with a s.g. of 1.025)

696837: A Crash which occurred under some circumstances when exporting a GHS

file with key points linked to a tank has been fixed.

662937: When running the application through the COM interface, calling

BentleyStability.Application.Exit no longer prompts to save modified files.

661586: The Auto-Ballasting command as well as multi-core analysis are now

available in MAXSURF Stability Advanced (previously these were only available in

the Enterprise version)

To use the Auto-Ballasting command, do not forget to turn on the Ballasting

column in the Loadcase view (from the Display | Data Format dialog)

661584: “Activate GHS Export” has been removed from the Edit menu since it does

nothing (GHS export is always enabled).

659424: A problem with the Tank Properties Sheet not always updating correctly

has been fixed.


559682: The convergence status can be shown in the results table for most

analysis types (using the Display | Data Format Dialog).


MAXSURF Motions


694070: A problem when setting the vessel gyradii kxx and kyy set via COM has

been fixed and the ability to set the yaw gyradius (kzz) has been added

643352: A problem which inverted the wave elevation trace in the Time History text

file (which can be saved when doing an animation of the vessel motions) has been

corrected.

MAXSURF Structure

572098: Structure functionality implemented in Modeler

The functionality available in the Structure module has been included in Modeler and

eventually Structure will be deprecated.


MAXSURF Multiframe

ISM v4.0 Upgrade

Multiframe can now export a frame in Bentley ISM version 4 format with additional

components such as curved members, curved surfaces etc. This can be used to import

the frame in to other Bentley analysis, design or detailing packages such as Staad.Pro,

Staad(x), Sacs & ProjectWise etc.

To export a frame saved in the ISM format

Choose ISM from the Export sub menu

Specify the name and location of the file to be exported using the Save File

dialog.

216957: Create circular patches and/or openings precisely

Multiframe currently allows circular patches and openings to be drawn in structural

designing. One new feature is added to allow users to draw a precise circular patch or

opening by holding the SHIFT key down.

To add a circular patch/opening precisely

Choose Add Circular Patch/Opening from the Geometry menu

Click on two points, one is for the circular centre and the other is for the

edge of the patch/opening. If SHIFT key is held down while clicking, the

below dialog window will be shown for user to modify the centre coordinate

and radius.

Click OK to create a precise circular patch or opening


Problem Reports

We greatly appreciate any bug reports or suggestions you may have. Please report any

bugs or anomalies you find through http://apps.bentley.com/srmanager/ProductSupport

http://apps.bentley.com/srmanager/ProductSupport

maxsurf connect edition v21.10.00 readme 26 july 2017connect edition: maxsurf v21.10.00 readme 26...

Documents