Professional Documents
Culture Documents
d52541 PDF
d52541 PDF
d52541 PDF
*1 Please note that a Windows Platform Update (Windows 7 SP1 and Windows Server 2008 R2 SP1) is a pre-requisite for accurate 2D rendering (for
example Text graphics) in the 3D canvas (http://support.microsoft.com/kb/2670838 ).
*2 AVEVA does not support the installation of AVEVA E3D 2.1 software and\or Projects on to disk volumes with Short\8.3 file name format disabled.
Please ensure that Short\8.3 file name format is enabled on all relevant volumes before installation. Please refer to Knowledge Base item 5702 for
further details.
*3 AVEVA E3D 2.1.0 has been tested with Microsoft .NET Framework 4.0 with the following fix: http://www.microsoft.com/en-
us/download/details.aspx?id=3556. This fix is mandatory for the use of the Design in Context Feature.
Microsoft .NET Framework 4.5 Fix 2 has been tested with AVEVA E3D 2.1.0. The fix release is required to ensure the correct visualisation of the
AVEVA E3D Draw 2.1.0 print dialog.
For further information please contact your local AVEVA support office, which can be found at support.aveva.com
File: d52541
Last saved: 6-Oct-2016 Copyright 2016 AVEVA Solutions Limited Page 1 of 37
Product Release Letter
Please note that recommended/supported hardware and software configurations are constantly subject to
review; please consult the AVEVA support web pages for the latest recommendations.
Microsoft® Software
AVEVA E3D 2.1.0 has been verified with Microsoft® Office 365.
Microsoft Office 2010 (and later) is required for some functions:
1. Optimum operation of the AVEVA Design Platform GUI requires Arial Unicode MS font, supplied with
Microsoft Office and also with Microsoft Office Visio.
2. Microsoft Office Excel import requires “.NET Programmability Support” enabled when Office is
installed. This can be found under “Advanced customization of applications” and installs the
Microsoft.Office.Interop.Excel.dll; without this, Excel import will not work.
Microsoft Office Visio 2010 (Standard edition, 32-bit) is required for AVEVA Schematic Model Viewer.
Compatibility
For full compatibility details, and for information about AVEVA E3D 2.1.0 compatibility with any later
versions, please refer to the compatibility matrix.
The following AVEVA products are compatible with AVEVA Everything3D™ 2.1.0.
The following LFM products are compatible with AVEVA Everything3D™ 2.1.0:
LFM Server™ 4.4.0.
Supersedes
This release supersedes Release 52531– AVEVA Everything3D™ 2.1.0.5.
Install
Please download the release (52541.zip) and run the product install (Folder E3D2106, E3D2.1.0.6.exe)
following the instructions.
Sample Data
Sample projects are available here: AVEVA Everything3D™ - Projects.
The AVEVA sample projects are regularly revised and have been updated with AVEVA E3D – Projects 2.1.0
Fix.4 being released to provide sample data for the Terrain application and Supports features available in the
Documentation
The AVEVA E3D 2.1.0 documentation includes the AVEVA Administration, AVEVA Catalogue and AVEVA
Global product user guides.
Documentation is available online so that it may be continually updated and remain current for any new
functionality introduced through the life of the product. AVEVA Documentation 2.1.0 may also be
downloaded separately for local installation here: AVEVA Documentation 2.1.0.
First Release
This product release is first available on the AVEVA support website support.aveva.com as AVEVA
Everything3D™ 2.1.0.6, release number 52541.
List of Enhancements
AVEVA Everything3D™ (E3D™) is the primary 3D design product from AVEVA covering the needs of Plant
industries. The release also introduces the capability to interact with Hull models produced in AVEVA Marine.
AVEVA E3D 2.1.0 provides a platform to enable lean construction principles to be adopted, increasing quality
and speed of execution throughout the entire project. This is achieved through advanced usability for all
design tasks, improving productivity by utilising latest technologies and best in class User Experience to
enable innovative and ever more efficient project execution processes.
The product includes optimal integration with AVEVA Engineering & Schematics and new innovation with
Laser data, utilising the Living Point Cloud capability of AVEVA HyperBubble™. Powerful 2D drafting also
allows the inclusion of Laser data, driving down the need to remodel existing Digital Assets.
The AVEVA E3D 2.1.0 release includes the following general functional enhancements:
General Model Interactions e.g. the PowerWheel, PowerCompass and Properties Grid.
Integration with AVEVA E3D Insight™ and the ability to Comment a design.
Please refer to the AVEVA Everything3D™ 2.1.0 User Bulletin for extensive information on features introduced at
AVEVA E3D 2.1.0.
Where migrating to AVEVA E3D 2.1 from AVEVA PDMS or Hull & Outfitting 12.1.SP4 please consult the AVEVA
Everything3D™ 2.1.0 Migration & Interoperability Guide for guidance on specific data considerations.
SpaceMouse Support
This release introduces support for a 3D SpaceMouse®(3Dconnexion) to enable navigation in the 3D View of
the Model and Draw modules (the mouse may only be used for navigation purposes).
Please note: the provided capability is not currently compatible with the 3Dconnexion software 3DxWare®
where settings have been applied for AVEVA E3D 2.1. Users are advised to ensure that any previously set
options are deactivated (as per the default state).
Terrain Application.
AVEVA E3D 2.1 Fix.5 introduces the Terrain application within the Model module. The Terrain tab is prompted
via the selection of Terrain from the Discipline options list and facilitates the definition, modelling and
modification of terrain data.
AVEVA E3D – Projects 2.1.0 Fix.4 provides sample data for the new Terrain application.
Terrain Surface
A terrain surface is imported and created by the Import (IMP) command and is formed by a Terrain
Surface (TRNSUR) with a GENPRI holding the imported geometry.
The following import formats are supported initially: IGES, STEP, STL and XYZ.
A Terrain Definition (TRNDEF) is used to define a terrain and may be restricted to a specific area of the
imported Terrain Surface by a rectangular restriction (TRNRR). In addition, standard primitives and
negatives (stored below a Terrain Primitive element TRNPRI) can be used to add or remove material
from the terrain model at creation or as a modification.
The resulting Terrain Solid (TRNSLD) is formed from the Terrain Definition with the terrain geometry
stored as a GENPRI.
Terrain Model
With reference to a Terrain Definition (TRNREF), the Terrain Model (TRNMOD) is used by Model users
during design activity.
Each Terrain Model can be further split by a cell structure that is defined by a collection of dividing
planes obtained from a Reference Grid (REFGRD).
Terrain Contours are associated to a Terrain Model with sets of contours (TRNCLS) holding groups of
contours (TRNCLG) at the same height.
To enable contours to be added to the Drawlist for a given terrain cell, a terrain curve collection
(TRNCUC) groups all curves that belongs to a cell and in turn contains a terrain curve set (TRNCUS) that
groups all curves defined by a particular contour line set (reference CLSREF points to the contour line
set). A terrain curve (TRNCUR) defines the portion of the contour line group that is within the cell.
For further detailed information on the forming of a Terrain Definition and Model please refer to the AVEVA E3D
2.1 Terrain User Documentation.
For further detailed information on the use of Terrain data in Draw please refer to the AVEVA E3D 2.1 Draw User
Documentation.
User-defined Trunnions may be defined via the Component Selection tab of the Supports Trunnion Data form
in the Paragon module (AVEVA Catalogue 2.1.0). The user is able to pick compatible components and apply
them as possible user selections for items in the make-up of a Trunnion.
Valid components are available in the Components for Trunnion lists and may be set as being active as
required. Items that appear as valid inactive selections are collected by support class from the range of
available components. A default active component exists for each component category and may be changed
via a right-click menu.
On creating a Trunnion type in the model, the user is presented with the support type information in addition
to tabs for each component. The user is able to select a component tab and dynamically change it to one of
the available component options as defined in Paragon.
In the example here the XAC18A tab has been selected and the
Reselect Ancillary Type button clicked to prompt the Ancillary
Selection form. The selections in the prompted form are limited to
the available types as specified in Paragon for this support type at
the given bore.
The new trunnion functionality requires the latest ACP catalogue databases for the supports
application. These are provided in AVEVA Everything3D™ - Projects 2.1.0.4 and above.
Users wishing to create user defined trunnion ancillary components (AC500 – 700) may need to
upgrade their existing MDU project to include these items.
The upgrade process can be completed within the Paragon module via the ‘Check Supports
Application Defaults’ tool. It is important, however, that the user updating the MDU database has
appropriate write access to make any changes.
For further detailed information on the setting and administration of user-defined trunnions please refer to the
AVEVA E3D 2.1 Supports User Documentation.
The Carpenter and Patterson Witch-Hanger interface software is now available for use within the Supports
application in AVEVA Everything3D 2.1.
Use of the software is administered in the Supports Admin Data form within the Paragon module.
For further detailed information please refer to the AVEVA E3D 2.1 Supports User Documentation.
In regards to the setup of the Witch-Hanger interface, specific file paths are set up within a new file called
hangerInterfaceConfiguration.xml in the default AVEVA E3D 2.1 install directory.
In contrast with older versions of the software there is no longer a need to setup project specific evars within
evars.init for the hanger interface executable file or input/output folders in the project.
AVEVA E3D 2.1 Fix.4 introduces the Mining application within the Model module. The Mining tab is prompted
via the selection of Mining from the Discipline options list and allows the creation and modification of mining
conveyors and equipment.
AVEVA E3D – Projects 2.1.0 Fix.3 provides sample data for the new Mining application.
As required of all Model data, Mining elements may be incorporated into drawings and intelligently
annotated to form project deliverables.
For further detailed information please refer to the AVEVA E3D 2.1 Mining User Documentation.
This release introduces Vessel Framework Supports to the Supports application in the Model module. The
Vessel Framework Supports are used for supporting pipework associated to Vessels. A default set of Vessel
Framework support templates are supplied with the Supports application (accessed via Supports tab >
Framework gallery).
A user may create Vessel Framework supports using a combination of framework types and ancillaries;
guided throughout the creation process by a series of prompts.
Some vessel framework supports require the creation of support brackets on the vessel before creation.
In most cases, support brackets can be created as box primitives.
For further information please refer to the AVEVA E3D 2.1 Supports User Documentation – Section
6.5 Vessel Framework.
For further information please refer to the AVEVA Catalogue User Documentation- Section 10.13.19
Vessel Framework Supports for Pipes.
The IsoDraft module is now able to produce isometrics containing multiport valves and instruments. Such
valves are typically used in the dairy and food industries.
There are 18 SKEY variations available – the below illustrates an example of a Three-Level Multiport Valve.
For further information please refer to the IsoDraft Reference Manual: INST Symbol Keys and Symbol
Key Reference Index.
The AVEVA Bocad Steel Interface is an integral part of AVEVA E3D 2.1. The interface facilitates the transfer
of structural steel data between AVEVA E3D 2.1.0 and AVEVA Bocad Steel (2.1.1 onwards). The interface
makes allowance for the introduction of the new Structural Catalogues at AVEVA E3D 2.1.0 and the use of
GENSEC elements.
The AVEVA Bocad Steel Import and Export tools are located within the Import and Export groups in the
TOOLS tab.
New mapping files have been made available; one for each standard of the new AVEVA E3D 2.1 Structural
Catalogue, to be used with the most recent AVEVA Bocad Catalogue (2.2.1 and 2.3 onwards). These mapping
files are required to be customised where the AVEVA Bocad Catalogue has been altered or a differing
standard has been used in a project.
The standard P-lines that exist for the profiles within the new AVEVA E3D 2.1 Structural Catalogue are
sufficient to use the AVEVA Bocad Steel Interface - additional P-lines previously used are no longer required.
It should be noted that within the new Structural Catalogue ANGLE profiles have a new orientation
convention in line with other products in the market. This is managed by an internal orientation mapping
file.
It is important to note that the AVEVA Bocad Steel Interface provided within AVEVA E3D 2.1 is compatible
with the ‘old’ Profile catalogue and P-lines as long as the specific P-lines have been installed.
In regards to the import process, it should be noted that only GENSECs will be created at import due to SCTN
elements being no longer used by the AVEVA E3D 2.1 Structural application.
Please refer to the AVEVA E3D 2.1 User Documentation for further information regarding the
administration and use of the AVEVA Bocad Steel Interface in AVEVA E3D 2.1.
The AVEVA SDNF interface facilitates the transfer of structural steel data between structural applications
using the SDNF neutral format file. The interface makes allowance for the introduction of the new Structural
Catalogues at AVEVA E3D 2.1 and the use of GENSEC elements for linear structural elements.
This SDNF interface is available in the Import and Export group of the TOOLS Ribbon tab.
A new mapping file format has been introduced (BLOCK). This will increase the speed of search within the
mapping file. As seen with AVEVA Bocad Steel Interface, a new tool is available to create or customise
mapping files with this new format – the AVEVA Structural Map File Converter. The tool is available from
the SDNF Import and Export forms via the Control menu option Map Converter.
Existing customised mapping files will be required to be updated where the intent is to use the new
AVEVA E3D 2.1 Structural Catalogue. Sample mapping files are provided with the installation.
The standard P-lines existing for profiles in the new AVEVA E3D 2.1 Structural Catalogue are sufficient to use
the SDNF interface. It should be noted that within the new catalogue ANGLE profiles have a new orientation
convention in line with other products in the market. This is managed by the orientation mapping file.
In regards to the import process it should be noted that only GENSECs will be created at import due to SCTN
elements being no longer used by the AVEVA E3D 2.1 Structural application.
Please refer to the AVEVA E3D 2.1 User Documentation for further information regarding the
administration and use of the AVEVA SDNF Interface in AVEVA E3D 2.1.
Title: Supports – unable to add additional PIPE, TRAY or HVAC on a Special Support.
Symptoms: Unable to add additional PIPE, TRAY or HVAC on a Special Support.
90266 193512 Supports
Previous/Known workaround: None.
Solution: Fixed.
Title: A Draw Collection can not be used as a REME via the DRAWLIST Manager.
Symptoms: A Draw Collection can not be used as a REME via the DRAWLIST
97783 209608 Draw Manager.
Previous/Known workaround:
Solution: Fixed.
Title: VSCAN aborts with database error 10 when the Drawing is outdated.
Symptoms: VSCAN fails.
92196 197969 Draw
Previous/Known workaround: None.
Solution: Fixed - VSCAN now skips elements that have been deleted.
Title: Ladder - Error message while creating Standards and Defaults Ladder module
Symptoms: ‘Error 24/06/2015 10:23:06 (2,891) An invalid zero direction has been
81293 175605 SLH obtained’ is presented.
Previous/Known workaround: -
Solution: Fixed.
Title: Several HULL parts were not displayed in E3D model module.
Symptoms: Incorrect generation of plates due to arbitrary notch NOT4.
90227 195825 Everything3D
Previous/Known workaround: None.
Solution: Fixed – notch is handled and Hull plate is displayed.
Title: Dimension attribute values are not scaled once exported to AutoCAD.
Symptoms: Dimension attribute values are not scaled once exported to AutoCAD.
93974 200785 Draw Previous/Known workaround: None.
Solution: Fixed - Dimension and overshoot are scaled once SHEE is exported to
dxf/dwg.
Title: ABSI - GENSEC with Spec Ref including special UTF8 Character are not mapped
(import or export).
Symptoms: GENSECs with a Spec Ref including special UTF8 Characters are not
196700 Everything3D mapped (import or export). The issue principally concerns the provided Russian
Standard where the mapping file requires further amendment.
Previous/Known workaround: None.
Solution: Fixed.
Title: Modify Properties form for standard equipment does not update to CE
selection.
Symptoms: The Modify Properties form prompted from the Standard Equipment
207135 Mining form does not update to match the selected current element.
Previous/Known workaround: The Modify Properties form is correctly updated for
the current element on being prompted via the main application Properties form.
Solution: Fixed.
Title: Not possible to add labels to PIPE elements via the Autotagging process.
Symptoms: -
90492 193989 Draw Previous/Known workaround: Manual labelling or by Autotagging alternative
(owned) element with PIPE annotation via appropriate intelligent text.
Solution: Fixed - PIPEs may now be labelled via the Autotagging process.
Title: Whole equipment added when adding within clip box volume.
Symptoms: Part of equipment added - leading to graphical selection issues.
91298 196275 Equipment Previous/Known workaround: Add whole equipment using Model Explorer.
Solution: Fixed – where part of an Equipment is within the clip volume it is replaced
by the owning Equipment.
Title: On prompting the Login form, the MDB is restored to the previous selection.
Symptoms: When a user is logging in and MDB selection is not the last action, the
90440 193842 Everything3D MDB may be restored automatically to the chosen MDB in the previous session.
Previous/Known workaround: -
Solution: Fixed.
Title: Autotagging: Removing redundant label may destroy local tagging definition.
Symptoms: On removing redundant Tags the referenced GLAB is deleted – the local
90493 193992 Draw rule defined is thereafter lost.
Previous/Known workaround: None.
Solution: Fixed.
Title: ‘Not all bypass loops are closed’ error for coincident Trunnions.
Symptoms: Cluttered Text.
92647 198616 Supports
Previous/Known workaround: Separate trunnions by 2mm.
Solution: Fixed.
Title: TUBI and ROD elements not required on reorder hierarchy form.
Symptoms: Unnecessary elements within form.
93704 200287 Piping
Previous/Known workaround: None.
Solution: Fixed - TUBI and Rod not shown on reorder hierarchy form.
Title: ABSI: Question mark symbols are appearing in Bocad if we provide Unicode
characters in Project header and User Data.
Symptoms: Substitute symbols (question mark) are visible in AVEVA Bocad where
Unicode characters are used in the project header or user data.
196401 ABSI
Previous/Known workaround: In order to exchange Unicode characters in AVEVA
Bocad Steel files, a user may edit the BocadUni.map file to replace ENCODING:ASCII
to ENCODING:UTF8BOM.
Solution: Fixed.
Note that the PmlRevisionControl object only operates on the Sheet that is currently
active and displayed in the canvas.
import 'Aveva.Pdms.SDInteraction.UI'
using namespace 'Aveva.Pdms.SDInteraction.UI.Gui.RevisionControl'
- 190229 Draw !revisions = object PmlRevisionControl()
Methods:
COMPAREREVISIONS(STRING, STRING)'
COMPAREREVISIONS(ANY, ANY)'
CREATESNAPSHOT(STRING)'
CREATESNAPSHOT(ANY)'
DISPLAYREVISION(STRING)'
DISPLAYREVISION(ANY)'
HASSNAPSHOT(STRING)'
HASSNAPSHOT(ANY)'
Title: Changing Rotation angle to 90 degrees causes problems with limits volume box
& Section plane Grips.
Symptoms: The 3D View in Draw does not currently respect an applied View rotation
angle.
83826 178445 Draw
Previous / Known workaround: The Edit in 3D View button is disabled where a View
Rotation angle is not equal to zero.
Solution: Fixed – 3D View can now be used for Views where the View Rotation angle
is not equal to zero.
Title: Enhancement - Provide PML access to the entities selected in the 2D canvas
Symptoms: Currently there is no PML access to the 2D canvas selection as the
existing Selection object only operates on the 3D view.
Known workaround: Use of the ID syntax.
Solution: The new CanvasSelection object has been provided that is more generic
than the Selection object and allows the user to interact with the graphical selections
set for the current document in both 2D and 3D. For example it provides PML access
to the selection in both the 2D Draw canvas and the 3D canvas in Model and Draw.
Note that it only operates in graphical mode, not in TTY mode.
Unlike the Selection object, the CanvasSelection object allows PML access to the 2D
canvas. This does not replace the Selection object for 3D which continues to provide
more specialist and powerful access to the selection set in the 3D canvas.
Methods:
.canvasselection()
Creates an empty CanvasSelection object
.getselection()
Returns all the elements currently selected in the canvas as an ARRAY of DBREFs
.add(DBREF)
Selects the passed element if it corresponds to an entity
.remove(DBREF)
Deselects the passed element if it corresponds to an entity selected in the canvas
.clear()
Deselects all entities selected in the canvas
Title: Graphics Performance while manipulating Laser Data and creating Assemblies
with Laser Data in View.
Symptoms: Reduced graphical performance on manipulating laser data.
90314 193680 Everything3D
Previous / Known workaround: Remove laser data from 3D view.
Solution: Fixed - improved performance of graphical rendering with laser data in the
View.
Title: Stairs with Pitch Validation Value default - problem with configurations.
Symptoms: When a Stair Flight is modelled using a default where the pitch validation
Stairs, value is used to calculate the optimum stair rather than the pitch angle,
86848 185242 Ladders & configurations which meet the required default validation value are highlighted
Handrails amber (with a warning that they DO NOT meet the optimum pitch validation value).
Previous / Known workaround: None.
Solution: Fixed.
Title: Walls & Floors - Connections > Tidy > Joints form deletes JLDATUs
Symptoms: Connections > Tidy > Joints form deletes JLDATUs.
91773 197206 Structures
Previous / Known workaround: -
Solution: Fixed – tidy function applies to only Joint of Walls e.g. STWALL
Title: New labels inherit LAYE justification and alignment overriding template.
Symptoms: When creating new labels from PML (or auto-tagging), the default tends
to be incorrectly JUST LEFT and ALIGN BBODY.
Previous / Known workaround: Manual modification.
189224 Draw
Solution: Default values for Alignment and Justification attributes on LAYE and SLAB
elements are set to ‘By Template’. Note: that when creating new LAYE elements from
the Autotagging form values are overwritten by the default file PDMSUI\dflts\dra-
gen-taglay. This file is customisable by the user.
Title: Length of GENSEC doesn't include the cut when a negative is inside.
Symptoms: The length of GENSEC doesn't include the cut when a negative is inside.
184280 Structures
Previous / Known workaround: None.
Solution: TCTL now accounts for negative primitives for straight GENSECS.
Title: Split command will not split GENSECs where not created in plane of member.
Symptoms: When attempting to split a GENSEC with another GENSEC when the
GENSECs have not been created in the plane in which they lay, the split does not
88572 189582 Structures work.
Previous / Known workaround: None.
Solution: Fixed.
Title: Require current radius to be displayed when changing a curved GENSEC radius.
Symptoms: Current radius feedback is not shown.
86764 185072 Structures
Previous / Known workaround: Reference to Properties Grid.
Solution: Fixed – feedback provided.
Title: Detail mode initial rise stairs have incorrect length extension / landing panels.
Symptoms: When an initial rise configuration stair flight is created which has an
Stairs,
extension and/or a landing, the panels on the extension and landing are not allowing
87415 186456 Ladders &
for a tread overlap.
Handrails
Previous / Known workaround: -
Solution: Fixed.
Title: Stair Flight - Rise position altered while modifying Detail Mode Stair flight with
Initial Rise configuration.
Stairs,
Symptoms: It has been observed that Rise Above\Below tread alters while modifying
186751 Ladders &
Stair flight.
Handrails
Previous / Known workaround: None.
Solution: Fixed – check has been added.
Title: Stair Flight using default with pitch validation presents warning.
Symptoms: When modelling a stair flight which is using a Default where the pitch
Stairs, validation rather than angle is used to calculate the stair, a warning message is
87605 186886 Ladders & displayed when picking the required configurations.
Handrails Previous / Known workaround: Issue reproducible for the pitch Validation Value in
the range of 600 to 660.
Solution: Fixed.
Title: Open item browser dialog is slow to appear with large projects.
Symptoms: Open item browser dialog is slow to appear.
Previous / Known workaround: None.
Solution: The open and admin hierarchy browse dialogs, as well as all 'create
element' dialogs, now start up faster as the database is read as and when the
- 178093 Draw hierarchy is expanded. To support this development element name searches in the
browser are based upon a database name search. Note that the search finds any
elements of the appropriate type with a name containing the search fragment
anywhere in the name, as before. However, searching for elements with a name
beginning with a search fragment is faster and can be performed by prefixing the
search text with a forward slash '/' to indicate this is the start of the name.
Title: Error presented when using check support in Clasher where the Supports
application is not loaded
- 185520 Supports Symptoms: Error: Aborted !!findSupports.addPickedElement(!this.re turn[1], FALSE)
Previous / Known workaround: Open Support application prior to clashing.
Solution: Fixed.
Title: Exception when setting an ENDATU POSL attribute using the Properties Grid.
Symptoms: Exception experienced on the system attempting to find the plines for
187619 Everything3D the ENDATU.
Previous / Known workaround: Set attribute via the command window.
Solution: Fixed – system checks ENDATU owner for a list of allowed Plines.
Title: Incorrect Isometric for a Pipe containing a PIPCA connection at a TEE where
Hyper Plant is on and weld numbers from Database.
- 186032 IsoDraft Symptoms: Incorrect Isometric for described scenario.
Known workaround: None.
Solution: Fixed.
Title: The default bend selection form does not reload available bending machines.
Symptoms: Available bending machines are not reloaded on opening the default
bend radius form and an error occurs when a wall thickness cannot be obtained.
Previous / Known workaround: Restart E3D to reload the bending machines but no
- 187009 Piping workaround for described wall thickness error.
Solution: Fixed - the form now reloads the available bending machines each time the
form is opened. The form also handles the case where a wall thickness cannot be
obtained.
Title: Compound joints (SCTN > SNOD > SCOJ > SUBJ) are omitted during SCTN to
GENSEC conversion
- 181832 Structures Symptoms: As described above.
Previous / Known workaround: -
Solution: Fixed.
Development Testing
Developers have carried out unit testing of each enhancement and/or fix in the development environment
to verify that any new functionalities have been correctly implemented and identified defects have been
corrected.
Regression tests have been run in the development environment to verify that enhancements and/or fixes
have not adversely affected the integrity of the product.
System Testing
Independent system testing has been carried out on this product, as released, to verify that it installs
correctly in all supported configurations that any new functionalities have been correctly implemented and
identified defects have been corrected.
Acceptance Testing
AVEVA’s Training and Product Support group is satisfied that the System Testing for this release is sufficient
to assure product quality.
Any exceptions found during Acceptance Testing or after release will be reported in the Product Release
Latest Update Note on AVEVA's support web site http://downloads.aveva.com/52541/w52541.pdf.
Laser. The Box and Cylinder primitives (only) are fully compatible with the Highlight and Mask laser data
features. The Box primitive (only) is fully compatible with the forming of a Demolition package volume.
Supports (TFS-183921). It is not currently possible to set the Support joint justification to a Pline of the
Column.
3D View Selection (TFS-174778). Pipes with no component cannot be selected via a window selection in
the 3D View.
Install (TFS-186636). AVEVA E3D 2.1 currently does not support a Project installed on a Windows 8.1 D:\
partition where the file path contains spaces. The issue is linked to the install of AVEVA E3D 2.1 to a
volume with 8dot3naming disabled referencing projects installed to a volume with 8dot3naming enabled.
An installation error is presented on first running AVEVA E3D 2.1 and on subsequent occasions the login
form is presented but without Project tiles for selection.
Terrain (TFS-200037). A Line Style with a Text String (TXTSRI) defined does not export correctly to DXF,
DGN or PLOT formats. This prevents the export of contour annotation to these formats.
AVEVA Global. All extract database FLUSH and ISSUE commands must be undertaken from within AVEVA
E3D 2.1 when accessing a globalised project with both AVEVA PDMS / Hull & Outfitting 12.1.SP4 and
AVEVA E3D 2.1.
For the latest list of exceptions and other updates, please see the Product Release Latest Update Note on
AVEVA's support web site http://downloads.aveva.com/52541/w52541.pdf.
Please refer also to the Product Release Latest Update Note for the original full release,
http://downloads.aveva.com/52421/w52421.pdf.