Release Notes

SAP2000 Version 14.2.
2
Release Notes
© Copyright Computers and Structures, Inc., 2010
Release Date: 2010-07-30
This file lists all changes made to the SAP2000 since the previous version. Most changes do not affect most users.
Incidents marked with an asterisk (*) in the first column of the tables below are more significant and are included in the
ReadMe file.
Changes from V14.2.1 (Released 2010-03-31)
License and Installation

Enhancements Implemented
* Incident Description
24929 The installation has been changed so that it is no longer necessary for users to use the command
"Run As Administrator" the first time they execute SAP2000 provided that older versions of the
program are uninstalled beforehand. This action was previously needed for Windows systems with
UAC turned on and for users with limited access rights, and will still be required for updates applied
as patches and by running the installation with an older version of the program already present.
Analysis
* 17754 The sign of all results for hyperstatic load cases has been reversed at the request of several users.
17828 There has been no change in the magnitude of the results, except as may occur due to the changes
19447 under Incident 20599. Hyperstatic load cases calculate the secondary forces due to the support
reactions present in another (parent) load case. With the new sign, the primary response can be
obtained by subtracting the hyperstatic response from the parent load case. Load combinations
containing hyperstatic load cases present in models saved in versions prior to v14.2.2 should be
modified by the user to account for this change in sign.
24902 An incident was resolved in which the use of edge constraints when joints are very close to each
other created numerical sensitivity and occasionally caused nonlinear static or time-history analysis
to fail to converge. This was specially noted in bridge area models when slight offsets in stepped
nonprismatic steel girder sections are present. When the joint to be constrained is very close to the
end of the edge, a rigid body constraint is now used instead of an edge constraint.
Frame Design
* 22850 An enhancement was made, adding the Eurocode National Annex parameters for Eurocode 3-2005
steel frame design and Eurocode 2-2004 concrete frame design, for Sweden, Finland, and Denmark.
* 24495 Steel-frame design has been implemented for the Australian design code "AS 4100-1998". This
covers the analysis methods and checking of members subjected to bending, axial compression,
axial tension, and combined actions.
26621 The calculation of the PMM surface used for design has been enhanced for unusual cases where the
surface becomes non-convex due to the effects of both the phi factor and the upper limit
(compression cap). Previously the upper limit was imposed before applying phi factors, now the
order is reversed. This only affects the region where the cap intersects the raw interaction surface at
SAP2000 V14.2.2 2010-07-30 Page 1

points below the balanced condition. In addition, the minimum phi factor is used where necessary to
eliminate areas of non-convexity. This removes kinks in the P-M curves. However, full removal of
non-convexity is not assured. These changes are slightly conservative, and affect very few practical
cases.
Database Tables
23141 Two new tables have been added to the database tables for the stiffness optimization data used in
steel frame design: "Steel Frame Design Lateral Displacement Targets" and "Steel Frame Design
Time Period Targets".
Application Programming Interface (API)

24595 Two new functions have been added to the Open API: GetModelFilepath and GetModelFilename.
These return the the filepath, filename, or combined path and name of the current model file.
26386 For the Open API, the functions SapModel.Analyze.SetSolverOption and
SapModel.Analyze.GetSolverOption have been superseded by the functions
SapModel.Analyze.SetSolverOption_1 and SapModel.Analyze.GetSolverOption_1. The new
functions include control over whether the analysis runs in the GUI process or as a separate process.
Documentation
26759 The database documentation manual (SAPDatabaseDoc.pdf) has been removed from the program
documentation. This manual is dynamic and changes with any change to the database tables. Users
can generate this manual or a portion of it from inside the program by using the Options menu >
Database > Documentation to Word command.
User Interface and Display

Incidents Resolved
20585 An Incident was resolved where a frame object could get deleted when it was divided using the
option Edit > Edit Lines > Divide Frames > "Break at intersections with selected Joints, Frames,
Area Edges and Solid Edges". This would happen in the very rare case when the intersection point
was closer to the end of the frame being divided than the automerge tolerance dimension.
23205 An Incident was resolved in which the edit box for the object or group name in the list of operations
for the staged-construction load-case definition form was not always showing the correct value
when an existing operation was highlighted.
24158 An Incident was resolved in which the new-model template for a circular plate with a circular hole
was using the specified inner radius R1 as the outer radius when generating the model.
24898 An Incident was resolved where certain line and area assigns were available through toolbuttons
when the model was locked, even though they were not available through the menus. If these were
used to make assignments, the analysis would automatically re-run. These functions are now
disabled when the model is locked.
SAP2000 V14.2.2 2010-07-30 Page 2

25252 An Incident was resolved in which an exception (runtime error) could be generated when trying to
delete a frame section property and there existed at least one built-up cover-plate section in the list.
25349 An Incident was resolved addressing two minor issues with certain models: (1) Displaying the
database table "Lane Definition Data" could generate an exception (runtime error). (2) Assigning a
named units set could generate an exception.
25401 An incident was resolved in which an exception (runtime error) was sometimes generated when
repeatedly adding and /removing functions to be displayed from the Show Plot Functions form.
25680 An incident was resolved in which an exception (runtime error) was generated when trying to
modify the lateral load settings for a notional load pattern when no valid dead or live load pattern
had yet been defined.
26580 A change was made on the Code Generated Load Combinations form to keep the multiple scrollable
columns in sync with each other. This is only a visual enhancement and does not affect any results.
Graphics
Incidents Resolved
25789 An Incident was resolved where the quick-view tool buttons “xy”, “xz”, and “yz” would not work
properly if there were no grids present in the current coordinate system. This was only a display
issue.
Modeling
Incidents Resolved
* 22732 An Incident was resolved in which the interaction surface for auto-generated steel FEMA hinges
was incorrect near the compression limit. The moment capacity did not decrease with increased
magnitude of compressive axial force as would be expected.
25398 An Incident was resolved in which the weight and mass may not have been correctly calculated for
the built-up coverplate frame section property in the unusual case where the weight or mass density
was not the same for the cover plate materials as for the base section material. The weight and mass
were previously being calculated for the entire section using the densities of the base section
material.
* 26180 An Incident was resolved that fixed two problems affecting built-up cover-plate frame section
properties that were imported from database tables (including .S2K and .$2K files): (1) The section
properties (areas, moments of inertia, etc.) were not properly calculated, but were obtained from the
base section alone without cover plates. This problem also affected built-up cover-plate sections
defined through the Open API. Properties would be correctly recalculated if the frame section
property was viewed in the graphical user interface and the OK button was clicked on the form after
viewing. (2) The values of the fy overwrites, when specified, were truncated to the nearest whole
value (e.g., 56.7 would be truncated to 56). Neither of these problems would occur if the frame
section property was directly defined in the graphical user interface.
* 26233 An incident was resolved where the width values for HSS16x4x3/16 and HSS14x6x5/8 sections in
the AISC13.pro file were incorrect. Section properties (i.e. area, moment of inertia, etc) were
correct. Design of members using these section sizes will have used the incorrect width values and
should be rechecked.
* 26373 An Incident was resolved in which the built-up coverplate frame section property was not properly
accounting for different material properties when calculating certain section properties: (1) The
minor moment of inertia I22, minor section modulus S22, and minor radius of gyration r22 were not
corrected for the ratio of E values. (2) The torsional constant J and the minor shear area As3 were
not correctly considering the ratio of G values. (3) The plastic moduli Z22 and Z33 were not
correctly considering the ratio of fy values. (4) However, the area A, major moment of inertia I33,
major section modulus S33, major radius of gyration r33, and major shear area As2 were all correct.
SAP2000 V14.2.2 2010-07-30 Page 3

Section Designer
Incidents Resolved
23214 An Incident was resolved that corrected two problems with double-angle sections in Section
Designer: (1) When material was added that fit exactly within the separation between the double
angles, Section Designer sometimes reported incorrectly that overlapping materials existed. (2)
When fibers were generated for double angles, they were sometimes located incorrectly for one of
the angles, in the location of the single angle mirrored about its local 2 axis.
23431 An Incident was resolved for Section Designer in which the calculation of overlapping areas and the
results of polygon operations were not always correct for pipe and tube sections when they
overlapped each other or other solid shapes. The errors were visually obvious when they occurred.
23840 An Incident was resolved for Section Designer in which the idealized Caltrans moment-curvature
relationship shown for a fiber discretization may be incorrect if the exact-integration moment-
curvature relationship was not also being displayed at the same time. The actual curve displayed
depended upon the order in which the plotting options were checked in the display form. This was a
display issue only, and did not affect the generated moment-curvature relationships used for
idealized Caltrans frame hinges.
* 26126 An incident was resolved in which the mass and weight calculated for certain Section Designer
sections could be incorrect, even negative. This happened in rare cases where overlapping objects
were drawn of different materials or an opening was drawn in a particular order. There was no error
in the normal case where included objects were drawn after the containing object was drawn.
26194 An Incident was resolved for Section Designer in which the torsional constant J was calculated as
zero for unusual cases where the cross-sectional mesh used to compute J was too small in local
regions because the X or Y coordinates, but not both, of two points differed by less than the auto-
merge tolerance. This was creating invalid elements that caused the calculation to fail. These
elements are now removed from the mesh to prevent this problem, without adversely affecting the
results. This issue was introduced in version v14.2.0 with the implementation of faster and more
accurate calculation of J.
26374 An Incident was resolved in which the plastic moduli Z33 and Z22 calculated by Section Designer
for sections containing multiple materials did not account for different values of fy, but were instead
based on the fy of the base material.
Bridge Modeler
Incidents Resolved
23420 An Incident was resolved in which an unnecessary rigid-body constraint was being created by the
bridge modeler across the entire bridge superstructure section at the down-station side of an in-span
hinge. This constraint was equivalent to an infinitely rigid diaphragm at that location. It had the
side-effect causing non-zero girder moments at the hinge when the deck was in torsion, even though
the overall section moment was zero, and the girder moments on the other side of the hinge were
zero.
23429 An Incident was resolved in which groups created in the Bridge Modeler for cross diaphragms were
being located using their distance within the span, rather than by their station. The form indicated
that station was to be used.
23504 An Incident was resolved for the Bridge Modeler in which the bearing (orientation) specified for an
in-span hinge was not always correctly applied in the generated linked model. This was occurring
because the modeler was trying to adjust for quick changes in skew angles, a change that had been
introduced in version 14.2.0. This correction is no longer being applied and the behavior has
reverted to that of version 14.1.0.
23522 An Incident was resolved in which analysis and bridge superstructure design results were lost when
certain bridge related items ("LayoutLines", "Deck Sections", "Bridge Diaphragms", "Restrainers",
"Bearings", "Foundation Springs", "Abutments", "Bents", "Parametric Variations", "Bridge
Objects", and "UpdateLinkedBridge Model" commands under Bridge menu) were reviewed without
any changes and the file was saved and re-opened.
SAP2000 V14.2.2 2010-07-30 Page 4

* 24730 An Incident was resolved for the bridge modeler in which, for steel-girder or precast-concrete-girder
deck sections, setting the fillet dimension f1 and the corresponding overhang L3 both to zero, or
setting the fillet dimension f2 and the corresponding overhang L4 both to zero, could result in an
invalid linked model being created for the top deck slab. In some cases the edge would be
disconnected from rest of the deck, and in other cases duplicated elements would be created that
made the deck overly stiff. Now restrictions are placed on the overhangs so that they remain outside
the exterior girder widths.
24779 An Incident was resolved in which a model containing standard H or HS vehicles that was imported
from database tables or a .S2K file could not be analyzed, but would instead generate an error
message. Other vehicles types were not affected.
* 24783 An Incident was resolved in which bridge temperature loading on steel I-girder bridge deck sections
was not being applied during analysis in any bridge span that had skewed supports and/or non-
prismatic girder sections when the steel girders were modeled as area objects. This did not affect
spine models or area models of the deck when the steel girders were modeled as frames.
24905 An Incident was resolved for the Bridge Modeler in which the orientation of the ends of the flanges
for steel I girders modeled as areas was not correct at the bent locations when the layout line was
curved. The orientation of the ends of the flanges at the end of the span was parallel to that at the
end abutment, and the orientation of the ends of the flanges at the beginning of each span was
parallel to that at the start abutment. This orientation is independent of the skew. The effect of this
could be to reduce the bending stiffness of the steel girders at the bent locations for continuous
girders, since continuity of the flange may be lost.
25294 An Incident was resolved in which the Bridge Modeler would sometimes generate an exception
(runtime error) when updating a linked model with grade beams present at the abutments.
25397 An Incident was resolved for the Bridge Modeler in which the orientation of frame elements used to
model steel or precast-concrete girders in superstructures modeled as areas could have, in some rare
cases, become reversed when updating the linked model. This affected the section-cut forces plotted
for the bridge response display and used for superstructure design, since the wrong end of the frame
element was used to get the girder forces and moments. The effect of this was visible as unexpected
jumps when plotting the bridge response display. This did not affect spine models, or area models
when the girders are also modeled as areas.
25492 An Incident was resolved for the Bridge Modeler in which temperature-gradient loading used with
flat slab deck sections could cause unexpected problems, such as exceptions (runtime errors) when
viewing the deck-section definition, or generation of linked models with bearing elements located
improperly.
26433 An Incident was resolved in which the display of stresses was not available for bridge objects with
deck sections of type flat slab or T beam. This problem was introduced in v14.2.0.
26545 An Incident was resolved for the Bridge Modeler in which the station assigned to the diaphragm, if
any, located at the start abutment was actually the station for the end of the first span. This only
affected the inclusion or exclusion of this diaphragm in staged-construction groups created for the
bridge object. It had no effect on the analysis model, and no effect on any analysis results not
affected by such staged construction groups.
Loading
Incidents Resolved
22461 An Incident was resolved in which the HL-93S standard vehicle was using the axle type "Fixed
Line Width" of 10 feet rather than type "Two Points" at 6 feet as do the other HL vehicles (HL-
93M, HL-93K, HL-93LB, and HL-93F). This could be seen by using the command to display the
standard vehicle as a general vehicle. Now all HL vehicles use the axle type "Two Points" at 6 feet.
SAP2000 V14.2.2 2010-07-30 Page 5

Analysis
Incidents Resolved
* 21895 An Incident was resolved in which the P-delta moments calculated for link elements sometimes
included the effect of joint rotations. This did not affect the results for two-joint links with non-zero
length when the P-delta moment was carried with a shear couple (the default case). It did affect the
following cases: (1) One-joint link supports that carried some or all of the P-delta moment at the j-
end (the default is for half of the moment to be at the j-end). (2) Zero-length two-joint elements,
which always carry the P-delta moment at one or both ends. (3) Two-joint link elements with non-
zero length if the advanced P-delta parameters were specified to carry some or all of the P-delta
moment as moments rather than a shear couple.
* 23251 An Incident was resolved in which creep for transverse shear strain was not being correctly
calculated for the bending behavior of thick plates and shells, causing time-dependent staged-
construction analyses to give obviously inaccurate results or to fail to converge. Membrane (in-
plane) behavior was not affected. The thin plate/shell formulation for bending was not affected. The
problem was introduced with version 14.2.0, and did not affect prior versions.
24277 An Incident was resolved in which nonlinear static load cases using displacement control were not
always able to run when the loading was applied only on shell elements. This was because the load
was not being applied in the first iteration, and the displacement control algorithm could not
perform the necessary scaling. However, loading was always properly applied if the load case was
able to proceed, whether using displacement or load control, so there was no affect on the accuracy
of the results.
* 24373 An Incident was resolved in which temperature and membrane-strain loading could be significantly
in error when a shell element was warped, i.e., it did not lie in a flat plane. The induced
displacements, or stresses in a restrained case, could have been significantly too large. This affected
the thin and thick homogenous shell elements, but not the layered shell. Gravity, self-weight,
uniform, temperature-gradient (through the thickness), and curvature-strain loads were not affected.
Surface-pressure loads acting on the edges of the element were affected, but not the more common
case of surface-pressure loading on the top or bottom faces. This issue was introduced in v14.0.0
and did not affect previous versions.
25256 An Incident was resolved in which target force iteration with cable elements would not always
converge when using the 64-bit analysis engine in cases where it would converge with the 32-bit
solver.
* 25328 An Incident was resolved that fixed several problems with the results for hyperstatic load cases.
These tended to particularly affect bridge models: (1) The support reactions that constitute the
loading in a hyperstatic load case were not being converted from joint local coordinates to the
global coordinate system. This affected any support having joint local axes, as is common in many
bridge models. (2) The small internal stiffnesses used to stabilize the structure during a hyperstatic
analysis were too large in some models, thereby reducing the hyperstatic response. This tended to
affect models where large stiffness values were used for supports, as is common in bridge models.
(3) Joint reactions and base reactions reported for hyperstatic load cases were and are not
meaningful, and are now set to zero. (4) Note that the sign of the results for hyperstatic load cases
has been reversed at the request of several users. This latter change is further described under
Incident 17828.
Frame Design
Incidents Resolved
20904 An Incident was resolved for steel-frame design using code "AISC360-05/IBC2006" where the text
on the form for Steel Frame Design Preferences that described the various parameters that derive
from the ASCE 7-05 code incorrectly referenced code "AISC 7-05" instead of "ASCE 07-05". This
was a text error only. No results were affected.
21933 An incident was resolved where, in rare cases, Section Designer sections were being tagged as
rectangular sections, resulting in incorrect design-section classification and incorrect section
SAP2000 V14.2.2 2010-07-30 Page 6

capacities. This affected all steel-frame design codes.
22860 An incident has been resolved for steel frame design using code "AISC360-05/IBC 2006" where the
reported value of Cw was incorrect when the display units were different from the base units (i.e.,
the units chosen when the model was created). This error only affects the reported value of Cw
itself. Calculations using Cw were not affected. The documentation was also corrected to indicate
the correct units.
23254 An incident was resolved for steel frame design using code "AISC 360-05/IBC2006" where the
warning message reported for tension members having l/r exceeding 300 was referencing AISC
360-05 section B7 instead of section D1.
* 23582 An incident was resolved for steel-frame design in which the design details sheet accessed by right-
button click for auto-select sections was presenting design results for the current analysis section
instead of the current design section when the two sections were of different sizes. The tables
accessed directly from the right-button click results also had the same problem. However, database
tables accessed from Display > Show Tables were correct, as were the tables for export and for
printing. This problem was introduced in version 14.0.0.
24159 An incident was resolved for steel frame design where the lateral factor was not always being
considered when calculating demand/capacity ratios. The factor was being applied only if a lateral
load was present as the last load listed in a combination. Otherwise the factor was not applied.
When it occurred, the error was conservative as the permissible increase in the allowable stress was
not being considered for combinations with lateral wind or seismic loading. This affected all design
codes that use this lateral factor. This issue was introduced in v14.2.0.
* 24384 An Incident was resolved for steel frame design using code Eurocode 3-2005 in which the
calculated values of Nb33.Rd and Nb22.Rd were not correct. These were being computed as if the
slenderness (Kl/r) was too small, which led to using full plastic capacity. This could have resulted in
an unconservative design.
26381 An Incident was resolved for steel frame design using "Eurocode 3-2005" in which an error
message was generated when performing design for members with framing type set to EBF, and no
results were produced.
26495 An incident was resolved in which an exception (runtime error) was sometimes generated during
steel-frame design using code Eurocode 3-2005. This problem was load dependent and only
occurred for certain models when using “Method 1 (Annex A)” for the “Interaction Factor Method”.
* 26649 An incident was resolved where large demand/capacity ratios were being reported for the Eurocode
3-2005 steel frame design when using Method 1 (Annex A) for computation of the K factors. This
could occur on members with end moments and would result in overly conservative results.
26683 An Incident was resolved for concrete-frame design in which the design check of nonprismatic
reinforced concrete sections was resulting in an error, preventing the check of these sections from
being completed. This problem did not affect sections for which the rebar was being designed rather
than being checked.
Bridge Design
Incidents Resolved
* 23401 An Incident was resolved for bridge design of multi-cell prestressed concrete box girder
superstructures where the live-load distribution factors (LLDF) calculated according to code
equations were incorrect as follows: (1) The factor for interior beam moment for two or more lanes
loaded was too small by a factor of up to 4.18, and (2) The skew correction factors for interior and
exterior beam moment and shear were incorrectly calculated for any non-zero skew angle. Flexure
and shear design checks using code-based LLDF for multi-cell box girder superstructures that were
run with versions 14.0.0 to 14.2.0 should be re-checked with the new version. Design checks for
composite precast-concrete I- and U-girder superstructures were not affected. Design checks that
did not use code based LLDF were not affected. Design checks for the segmental (non-multicell)
concrete box girder do not use LLDF and are not affected.
SAP2000 V14.2.2 2010-07-30 Page 7

23445 An Incident was resolved in which an exception (run-time error) was generated when creating
default load combinations for bridge design after changing the bridge design code from AASHTO
to JTG or vice-versa after running an analysis and bridge design.
23572 An Incident was resolved for bridge seismic design in which the automated pushover load cases
created for Seismic Design Category D would not always run to completion due to instabilities in
the generated model for the case of integral bearings at double-bearing bents when the bent cap was
centered on the girder rather than being located beneath the girder. This would result in the capacity
not being calculated. Other support conditions at the bents did not have this problem.
* 23700 An Incident was resolved for bridge superstructure design of multicell concrete box-girder deck
sections and precast-concrete girder deck sections in which the stress-check results were incorrect
when the design check was performed while the current length units shown in the graphical user
interface were different from the database length units (the database units are the units chosen when
the model was created). The effect of the different length units was to affect the location of the
points used to calculate the stresses in the section. This did not affect any other design checks, nor
did it affect the stress or principal-stress checks for the non-multicell box girder.
* 23703 An Incident was resolved for bridge design of precast-concrete girder deck sections in which the
stress-check results for the girders were incorrect if the concrete material used for a girder had a
different modulus of elasticity (Egirder) from that for the slab (Eslab). The reported girder stresses
were incorrectly multiplied by the square of the ratio Egirder/Eslab when the live-load distribution
factors (LLDF) are calculated from analysis (SAP), and were incorrectly multiplied by the ratio
Egirder/Eslab otherwise. For the common case where EGirder > Eslab, the reported stress values
were too large. Design stresses reported for the slab were correct for both cases.
24122 A check has been added to the definition of the concrete box-girder bridge deck sections for the Top
and Bottom Slab Cut Line Distances used for design such that these values are neither too large nor
too small. Each value must be at least 25% of the slab thickness, and their sum must be less than the
total depth of the section. Previously the user could define values that would sometimes cause the
design check to fail.
Results Display and Output

Incidents Resolved
24016 An incident was resolved where the graphical display of analysis results enveloping all stages in a
Staged Construction case would only show the elements that were present in the first stage. This
was a display issue only.
24065 An incident was resolved where drawing Section Cuts in models containing line, area or solid
24586 surface springs could generate an exception (runtime error).
24958
24538 An Incident was resolved in which an exception (runtime error) was generated when trying to
display the bridge response for a slab or girder of a composite deck section when objects in the
linked model had been deleted by the user after updating the linked model from the bridge object.
* 23816 An Incident was resolved where section cuts specified using a quadrilateral cutting plane were
25220 reporting the results based on the nodes nearest to the cut and were ignoring the “side”
specification. This could result in incorrect values being reported. This issue was inadvertently
introduced in v14.2.0 and did not affect prior versions. The section cut algorithm for quadrilateral
cutting planes has also been enhanced to capture discontinuities. Using a cutting plane at a
discontinuity will now report different results based on which "side" is chosen. This is achieved by
moving the cutting plane back by a tolerance if the positive "side" is chosen and forward by a
tolerance if the negative "side" is chosen. The automerge tolerance specified for the model is used
for this purpose.
SAP2000 V14.2.2 2010-07-30 Page 8

* 24909 An Incident was resolved in which the bridge response (superstructure forces, moments, and
stresses) for steel I-girder deck sections could be incorrect in the case where all of the following are
true: (1) The steel girders are nonprismatic, (2) The steel girders are modeled as areas, and (3) The
bridge object is updated as a linked model more than once without changing geometry. When a
duplicate linked model was created, the elements were being replaced with identical elements, but
the new elements did not get added to the section cuts used to calculate bridge response.
25026 An Incident was resolved in which displaying tables for section-cut forces or base reactions for a
moving-load case would never finish if the Section Cuts option had not previously been selected
using the command Bridge > Moving Load Case Results Saved. This has been resolved as follows:
(1) If the Section Cuts option is not selected before running the analysis, all section-cut forces and
base reactions for moving-load cases will be reported as zero in the database tables. (2) If the
Section Cuts option is selected before running the analysis, section-cut forces and base reactions for
moving-load cases will be calculated and displayed in the tables. The force and moment values are
calculated with vehicle response components set to "Do Not Use". This means the response is
calculated as if it is NOT a superstructure moment (positive or negative), and NOT a reaction at an
interior support.
26326 An Incident was resolved in which the labeling of the stress-point locations for U-girders was
incorrect in the Bridge Object Response display form if the U-girder is modeled as frame objects. In
particular, the stresses shown for the top-right, bottom-right, and bottom-center points actually
corresponded to the bottom-left, bottom-center, and bottom-right points, respectively, and the
bottom-right point always produced zero stresses. This only affected the stresses plotted from
analysis results. Design results were not affected.
Database Tables
Incidents Resolved
24405 An Incident was resolved in which an error message was generated and a blank table was produced
when displaying or exporting the table "Bridge Super Design 22 - AASHTOLRFD07 -
PCCompFlexure".
24558 An incident was resolved where database tables of results for Power Spectral Density load cases
that were reported per frequency had the StepNum field blank or missing.
25686 An Incident was resolved where importing a bridge model containing multicell-concrete box
superstructure design requests for AASHTO LRFD 2007 would reset the live-load distribution
factors (LLDF) to default values regardless of the settings that were present in the exported model.
These default settings are to use LLDF based on the design code, with particular numerical values
for the input parameters that can be seen by defining a new superstructure design request of this
type.

Incidents Resolved
25790 An Incident was resolved for the Open API function SapModel.File.New2DFrame where it would
generate an exception (runtime error) when used to define an eccentrically-braced frame. Other
framing types were not affected.
External Import/Export
Incidents Resolved
22993 An Incident was resolved in which the import of GTStrudl models was unable to handle more than
10000 joints with spring or restraint conditions. The limit has been increased to 50000 supported
joints.
SAP2000 V14.2.2 2010-07-30 Page 9

23330 An Incident was resolved in which the import of GTStrudl models was unable to handle triangular
shells.
24390 An incident was resolved in which the Perform-3D Structure export would generate an error if there
were more than 12 load patterns defined in the SAP2000 model being exported.
Documentation
21909 A spelling error in the steel-frame design manual for "CSA-S16-01" was corrected: "bonding" was
corrected to say "bending".
22086 An incident was resolved where the cover specification for concrete columns on the frame section
property form and in the Help description were inconsistent. The form specified "clear cover for
confinement bars" and that is how it was used in the calculations. However, the Help defined it as
the cover to the center of the longitudinal reinforcement. The Help has now been corrected. In
addition, the drawn section now shows the rebar and cover to scale; previously it was showing a
schematic. Note that this does not apply to beams, where cover is measured to the centroid of the
longitudinal rebar at the top or bottom of the beam.
24338 An Incident was resolved in which page 119 (PDF page 139) of the "CSI Analysis Reference
Manual" was blank. Only the information on this single page was missing. All previous and
subsequent pages were unaffected.
25059 The Matlab example in the API documentation was updated to correct errors that prevented the
example from running.
25760 The documentation for steel frame design using Eurocode 3-2005 has been corrected and clarified
for the description of how the parameters alpha and psi are calculated and used to determine the
section classification.
26093 An incident was resolved for the steel-frame design manual for "CSA-S16-01" where the equation
for Fez (Cl. 13.3.2) was incorrect. This was a documentation error only and did not affect the results
produced by the software.
26384 An Incident was resolved where the header was incorrect for Table 4-1 in the concrete frame design
manual for Eurocode 2-2004. The columns for Medium Moment and High Moment were
incorrectly labeled as Low Moment and Medium Moment.
26759 The database documentation manual (SAPDatabaseDoc.pdf) has been removed from the program
documentation. This manual is dynamic and changes with any change to the database tables. Users
can generate this manual or a portion of it from inside the program by using the Options menu >
Database > Documentation to Word command.
Miscellaneous
24809 The version number has been changed to 14.2.2 for a new minor update.
SAP2000 V14.2.2 2010-07-30 Page 10

SAP2000 Version 14.2.1
Release Notes
ReadMe file.
Version 14.2.1 is identical to version 14.2.0, except for minor changes made strictly for the Chinese release that do not
affect any other users.

Incidents Resolved
20255 An Incident was resolved in which Chinese and other double-byte characters did not display
correctly on some forms.
Bridge Design
Incidents Resolved
20270 An Incident was resolved in which the superstructure bridge design check for flexure using the JTG
design code would not run.
Miscellaneous
20254 The version number has been changed to 14.2.1 for a new update. This version is identical to
version 14.2.0, except for minor changes made strictly for the Chinese release that do not affect any
other users.
20265 The Chinese language localization has been updated for the graphical user interface.
SAP2000 V14.2.1 2010-03-31 Page 1

Release Notes
ReadMe file.

18247 The location of the arrows used to display area load assignments has been changed for clarity. This
does not affect any results.
20679 An enhancement has been made to the graphical user interface so that the view no longer zooms out
after certain operations, such as showing selection only, performing editing operations like deletion,
and returning from the Bridge Modeler.
22572 The forms for defining Eurocode 8 seismic response-spectrum functions and automated lateral loads
have been clarified so that it is clear that the input of the horizontal ground acceleration specified is
in terms of gravity (g).
Drafting
15749 Three new options are now available for dividing frame objects using the command Edit > Edit Line
> Divide Frames. They are (1) Divide at a specified distance from the I-end of the frame, (2) Divide
at the intersection with a coordinate plane in the current coordinate system, and (3) Divide at the
intersection with visible grid planes in the current coordinate system.
Modeling
19120 User-defined frame hinges can now be assigned to any frame section or any material. Previously,
hinges could only be assigned to certain known section types, such as rectangular and circular
concrete sections; steel pipes, tubes, and wide-flange sections; and Section-Designer sections. Now
hinges can be assigned to other section types provided that: (1) The scale factor for the horizontal
(displacement/strain/rotation/curvature) axis is user-defined; (2) For non-interacting (single DOF)
hinges the vertical (force/stress/moment) axis is user-defined; (3) For interacting hinges, the
interaction surface is user-defined. For all concrete sections, condition (1) always applies, as it did
previously. Note that these restrictions do NOT apply to any of the standard steel shapes available
in the frame section definition since the program is able to calculate the yield force/moment and
yield displacement/rotation based on section properties, if requested.
19481 The internal mesh used to calculate the torsional constant J for bridge deck sections, precast-U
sections, and precast-I sections has been changed slightly. The new meshing adapts to sections of
different sizes and to thin-walled sections, providing a more efficient solution with an error less than
about 1% for the calculated value. There should be little change in the results from version 14.1.0,
SAP2000 V14.2.0 2010-03-23 Page 1

where the meshing had been improved for larger bridge deck sections.
Section Designer
12050 Minor changes were made to improve the cosmetic appearance of the PMM Interaction Surface
form displayed for frame design.
19480 The definition of the relative mesh size used in Section Designer to calculate the torsional constant J
has been changed. Previously this was called “Max. Mesh Size/Overall Dim.”, and represented the
ratio of the mesh size in the X and Y directions relative to the maximum dimension in each
direction, respectively. This is now called “Max. Mesh Size (Relative)”, and represents the ratio of
the mesh size relative to the square-root of the area. The smaller of the absolute mesh size (if non-
zero) and that calculated from the relative mesh size will be used. This creates square rather than
rectangular elements. The new approach produces better results for thin-walled and complex
sections, and has little effect on simpler, solid sections.
Loading
18695 The handling of distributed and concentrated span loading on frame objects with insertion points
has been changed. Previously the load was applied as specified based on the actual length and
orientation of the frame after cardinal points and joints offsets were applied. Now the direction and
magnitude of the total load are computed based on the length and orientation of the frame located
along joint line i-j as if no insertion points were specified. This is how the loads were and still are
being displayed in the graphical user interface. If cardinal point assignments to a non-prismatic
frame or non-parallel joint offsets are applied so that the offset frame is not parallel to joint line i-j,
loads applied in the frame local directions will be transformed to the new coordinate system. This
means, for example, that a load specified in the local-2 direction will now have an axial component.
Loads applied in the global or other fixed coordinate system are not affected. In addition, non-
parallel offsets and/or axial offsets can change the length of the offset frame. In this case, the
magnitude of distributed loads will be scaled such that the total force or moment applied to the
offset frame is the same as computed for a non-offset frame along joint line i-j. See also related
Incident 14924.
Analysis
14113 More useful error messages are now printed when the analysis fails due to insufficient memory
during equation solution. Previously this was reported as an internal error.
18436 The documentation of the link element in the CSI Analysis Reference Manual has been updated to
describe the correct use of fixed degrees of freedom (DOF): (1) Links with fixed DOF should not be
coupled with other fixed links or connected to constrained joints. (2) Fixing fewer than all 6 DOF
can lead to loss of mass coupling between rotational and translational DOF, which can affect the
dynamics of the structure if large mass or rotational inertias are present at the connected joints. (3)
When all six DOF are fixed, the translational and rotational inertia is handled with no loss of
coupling.
18918 The log file (.LOG) file is no longer deleted when the model is unlocked. This enables the user to
review the results of the last analysis while editing the model.
20461 The error message produced in the analysis log when a shell element is overly distorted from the
plane has been improved to give the actual label of the element.
20464 An enhancement has been made to the handling of inertia for link elements with all six degrees of
SAP2000 V14.2.0 2010-03-23 Page 2

freedom (DOF) set to fixed. This will now generate a rigid-body constraint that uncouples the
translational and rotational inertia. Previously generalized constraint equations were being used that
could generate coupling between translational and rotational inertia, which was then discarded
during analysis. This could significantly change the dynamics of a structure that has large inertia at
the joints connected to the link element. Generalized constraint equations are still being used when
fewer than all six DOF are fixed. In such a case, it is recommended that large stiffnesses be used
instead of fixed DOF when ALL of the following conditions are present: (1) Any of U2, U3, R2, or
R3 is fixed, (2) The length of the element is not zero, and (3) Significant inertia is connected to the
link element for a dynamic analysis.
22645 Two improvements have been made to nonlinear direct-integration time history analysis: (1) Line
search is no longer used for the zero iteration. For most problems this was not useful and was taking
unnecessary time. (2) The internal reference force used to compare convergence errors has been
changed slightly to avoid cases where this could be too small, which could prevent convergence in
otherwise stable problems. Because of these changes, analysis results may differ slightly from
previous versions. In particular, two comparison values in verification Example 6-005a, "Damper
Element Under Harmonic Loading", differ in the fifth significant figure from the published results
for Version 14.0.0 due to this change. The reported maximum difference is -0.00113% and this is is
considered acceptable.
* 22674 The CQC3 method of directional combination has been added as an option for response-spectrum
load cases. When identical spectra are specified with different scale factors for loading in the two
horizontal directions, this method determines the critical angle in the horizontal plane for which this
loading will produce the maximum response, and reports that response. If the scale factors are
identical, this reduces to the SRSS method of directional combination, which is independent of the
angle of loading. The CQC3 directional combination can be used in conjunction with any method of
modal combination, and both the amplified and the rigid response are considered. The CQC3
methodology can also be applied using different spectra in the two horizontal directions, and a
critical response will be calculated, however the user must carefully interpret the meaning of the
results.
Frame Design
12079 The frame design procedure will now be set to NONE when a material overwrite is assigned to a
frame object and the overwrite material is of a different design type than the material in the assigned
frame section. This is done as a precaution and will affect very few models.
13064 The design load combinations created by the program for steel frame design code "CAN/CSA-S16-
01" now include notional loads, if any have been defined.
13716 The identification of lateral load cases (seismic or wind) has been improved for nonlinear cases
which may contain these loads. This affects the increase in allowables for some design codes.
17524 Snow loads are now included in the automatic load combinations that are created for concrete
design using codes "ACI318-02/IBC2003" and "ACI318-05/IBC2006". The documentation has
been updated accordingly.
17600 The design preferences for concrete, steel, cold-formed steel, and aluminum design have been
enhanced to provide new control for the creation of design load combinations involving nonlinear
static load cases. Previously the control for combinations involving time-history loads was also
being used for this purpose. The possible values for this new option are "Envelopes", "Step-by-
Step", "Last Step", "Envelopes - all" and "Step-by-Step - all". The "Envelopes", "Step-by-Step” and
"Last Step" options apply to time-history and multi-step static cases whereas for static nonlinear
cases only the last step is used in the combination. The "Envelopes - all" and "Step-by-Step - all"
also include all steps of the static nonlinear cases. The default value for new models is "Envelope".
When opening models saved in earlier versions of the program, the default value for multi-step
nonlinear load cases will be set to the value previously selected for "Time History Design".
* 19436 Eurocode 8 seismic provisions have been comprehensively implemented for concrete frame design
SAP2000 V14.2.0 2010-03-23 Page 3

using code “Eurocode 2-2004”.
* 19437 Eurocode 8 seismic provisions have been comprehensively implemented for steel frame design
using code “Eurocode 3-2005”.
20073 Steel frame design has been enhanced so that errors are now classified as those for which
calculations can be completed and those for which further calculation is not possible. The detailed
report now includes more results when calculation is possible, even if the design has failed due to an
error. Similarly, the on-screen and database tables have been updated for all steel frame design
codes to improve error reporting and calculation results.
20262 Concrete frame design has been enhanced so that the detailed report provided by the right-button
click on a member now displays more calculation results when a warning is generated. The detailed
report has not been changed for cases when an error occurs during design.
* 20661 The Singapore National Annex to Eurocode 2 (NA to SS EN 1992-1-1 : 2008) has been
implemented for concrete frame design using “Eurocode 2-2004”.
20702 The shear design for “Eurocode 2 2004” has been enhanced to optimized for angle “theta” in
Section 6.2.3 of the code. An optimal value is now used for any load combination that does not
require which torsion design and in which seismic loads are not present. Theta is conservatively
assumed to be 45 degrees for any load combination that does requires torsion design or that does
contain seismic loads. Previously the “theta” angle was conservatively assumed to be 45 degrees for
all cases.
* 20800 Concrete frame design using code "ACI 318-08" has been implemented.
Bridge Design
18790 The speed of performing bridge superstructure design has been considerably increased when the
program is installed on the network. Previously network installations could run significantly slower
than standalone installations. Now the speed is comparable.
19521 For bridge design of precast-concrete girder superstructures, the area of the concrete haunch below
the slab and above the girder is no longer considered in calculating the tributary area of the slab.
This may cause a small change in the design results, which will now be slightly more conservative.
Previously run design results, if any, will be deleted when a model is opened in the new version.
Results Output and Display

15383 Drawn section cuts now include link objects. Previously they only included lines, areas, and solids.
16836 For command Display > Plot Functions, the load case name is now displayed in the window title bar
of the "Display Plot Function Traces" form.
16985 Displayed plot functions have been enhanced by adding the ability to plot forces for section cuts
that have been defined using quadrilateral cutting planes. Previously only forces for sections cuts
defined from groups could be displayed as plot functions.
17734 When displaying mode shapes graphically, the modal frequency is now displayed as well as the
modal period.
19479 The reported transverse (plate) shear stresses (S13, S23) and shear forces (V13, V23) have been
improved for the homogeneous thick plate/shell element. The previous values were computed from
deformations and showed substantial gradients over the element when the twisting moment was
significant. The new implementation computes the values by equilibrium from moment gradients.
The new values are nearly constant over the element and are in better agreement with thin-plate
theory, where it applies, when twisting moments are significant. There is no substantial change in
the results where the twisting moment is small. This change only affects the reported transverse
shear values. There is no change to the stiffness of the element, to the computed deformations, nor
to the reported membrane forces, plate moments, and in-plane stresses (S11, S22, S12). No change
SAP2000 V14.2.0 2010-03-23 Page 4

was made to the homogeneous thin plate/shell element, nor to the layered shell element.
Data Files (.SDB, .S2K, .$2K)

19289 An enhancement was made to allow the export and import of the double-quote character (") in the
text file. On export, any double-quote marks in an exported text item are replaced with a pair of
double quotes and the text item itself is then put inside double-quotes. For example the property
name 24" will now appear in the .S2K or .$2K file as "24""". This approach must be used to
represent literal double-quote marks in any text file being used for import.

15816 The Open API function that hides the GUI now also turns off the drawing functions for increased
execution speed.
18869 The two Open API functions SapModel.Func.FuncTH.SetFromFile and
SapModel.Func.FuncTH.GetFromFile have been replaced by the new functions
SapModel.Func.FuncTH.SetFromFile_1 and SapModel.Func.FuncTH.GetFromFile_1. The new
functions include a time-step size parameter. Previously this was assumed to be 0.02 for the case
where the function was defined with fixed time step.
19290 Two new Open API functions have been added: (1)
SapObject.SapModel.BridgeObj.SetBridgeUpdateDataOne to update a linked bridge model subject
to specified parameters, and (2) SapObject.SapModel.BridgeObj.GetBridgeUpdateData to get the
parameters used for the last update.
20954 A new OpenAPI function, SapObject.SapModel.FrameObj.GetHingeAssigns, has been added to get
the locations, types, and names of the generated properties for hinges assigned to frame objects.
13669 Improved error and warning messages have been added for the import of CIS/2 STEP file.
16496 The import and export of IFC files has been updated to include Schema 2x2, 2x3, and 2x3_TC1,
including the import/export of sections properties.
21456 The ability to export physical objects to IGES files has been added. Previously all objects were
exported as FEM entities. Now you can choose either option. If you export as FEM, loads and
properties are also exported. If you export as physical objects, only geometrical line and surface
entities will be created, but properties and loads will not be exported.
* 22232 A new option to export a Perform3D Structure has been added. Most geometry, material and section
properties, and loads are exported for frame and shell elements. Corresponding Perform3D
members are created depending on the properties and assignments present on the individual
SAP2000 members. Detailed hinge properties and other Perform3D-specific features must be
defined in Perform3D. Restraints, diaphragm constraints, groups, and basic load cases are also
exported. The export option is available after the SAP2000 analysis model has been created.
SAP2000 V14.2.0 2010-03-23 Page 5

Note about Incidents Resolved: We have performed a thorough audit of the program, and have resolved all known
Incidents for which we have been able to determine that the program is not behaving as intended.
License and Installation

Incidents Resolved
22475 An Incident was resolved in which the bridge, staged-construction, and offshore licenses were
sometimes lost while using the program, requiring the user to close and re-open SAP2000.

Incidents Resolved
12183 An incident was resolved where a cylindrical coordinate system defined with only one theta grid
could cause a display error to occur in the program when displaying an elevation view.
13844 An incident was resolved in which the extruded deformed shape of an automeshed nonprismatic
frame section, plotted with the cubic curve flag on, did not correctly extrude the section. This has
been resolved by turning off the extrusion of nonprismatic shapes for the deformed shape in the
present version.
14003 An Incident was resolved in which the Edit > Change Labels command was not working properly
when a selection of the model is first made and then the subcommand Edit > Auto Relabel >
Highlighted in List is used with a highlighted selection in the Change Labels form.
15436 An incident was resolved where individual grid lines specified as hidden were still being displayed
16183 in plan and 3D views. Note that it is intentional that Z grid lines are always shown in 3D views, and
that edge grid lines are always shown in elevation views.
15439 An Incident was resolved in which an error message was generated after the program closed for
17854 some models with tendons modeled as elements and for which the analysis had been run. No data
19357 was lost, and no results were affected.
16188 An Incident was resolved in which an extraneous line could appear in the plot of the Tee section in
the frame section property form. This was cosmetic only.
16359 An incident was resolved where an exception (runtime error) was generated when the design
procedure was changed for a frame member in the right-click form after the analysis was run.
17280 An incident was resolved in which the units conversion for the material temperature values shown
in the right-click information form for frame, shell, and solid objects was converting for a
temperature change rather than absolute temperature, and hence did not include the difference of 32
degrees F between degrees C and degrees F.
17414 An Incident was resolved in which the extruded shape was not always displayed correctly for
18076 certain Section-Designer frame sections.
17497 An incident was resolved where the Show Selection Only setting was turned off (and all objects
were shown) after performing frame design.
17612 An Incident was resolved in which the coordinate system drop-down box allowed text input.
18089 An incident was resolved where time history functions defined with very large function values
would generate an error when plotting the function in the function definition form.
18567 An incident was resolved where a right-button click on a cable element would generate an exception
(runtime error) when the analysis model was being shown.
18654 An incident was resolved where, in rare cases, the extruded shape of a spine model for a bridge
object did not display.
18667 An incident was resolved where the on-screen display of area object and element joint offset and
thickness overwrite values were not updated when the current units were changed.
18716 An Incident was resolved in which graphics printing did not always use a suitable line thickness for
text and other symbols, such as end releases.
18800 An Incident was resolved in which the arrows did not show on the up/down buttons on the “Define
Load Cases” form.
18801 An Incident was resolved in which the name of the Quick Material “ASTM A500 Grade B, Fy 42
SAP2000 V14.2.0 2010-03-23 Page 6

(HSS Rect.)” should have correctly be called “ASTM A500 Grade B, Fy 46 (HSS Rect.)”. This is a
naming issue only, the correct value of yield stress was used in the generated material properties.
18861 An Incident was resolved in which an exception (runtime error) could be generated when switching
between bridge objects while viewing bridge design results in the bridge response display form.
18947 An Incident was resolved in which the “Vehicle Remains Fully in Lane (Longitudinal)” option for
bridge vehicles did not remain set when applied to a standard vehicle. This option was effective for
general vehicles.
18986 An Incident was resolved in which the bridge scheduler sometimes could not be started due to an
error exporting the “Bridge Object Definitions 07 – Bents” database table.
19004 An incident was resolved where, if a curved frame object was being shown in an extruded view and
then the curved object was divided into a series of straight line objects, the resulting extruded view
would appear incorrect.
19277 An Incident was resolved in which 2-D contour plots of pore-pressure loading on solid elements
were not being displayed correctly. The display of pore pressure values was correct, as were 3-D
contour plots and all analysis results. Only the 2-D display of the contour plots was affected.
19332 An Incident was resolved in which the previously set yield-stress overwrites (Fy) were not always
being displayed correctly when using the Modify/Show button to view the definition for frame
sections of type “Built-Up I Section with Cover Plate”. This could result in an incorrect value being
saved if the user clicked OK after viewing the incorrect values.
19370 An Incident was resolved in which right-clicking on the layout-line diagram in the Bridge Layout
Line form would prevent being able to exit this form if the layout line was curved.
20312 An Incident was resolved in which using the reshaper tool in Classical Plus graphics mode would
leave traces of the movement on the screen until the view was refreshed. This was cosmetic only.
20465 An Incident was resolved in which the loads are not displayed correctly for curved frame objects.
This was a graphical display issue only. No results were affected.
20519 An Incident was resolved in which some error messages show the program name as being
SAP2000V12 instead of SAP2000V14. This was a cosmetic issue only.
20593 An Incident was resolved in which the assignment of strain loading to frames, areas, and solids
using joint patterns was not working correctly. The specified joint patterns did not get assigned, as
could be seen by using the right-button click on the object, or from the database tables. The load
was applied during analysis as if the joint pattern was unity at all joints.
21392 An Incident was resolved where, in rare cases, performing a 3D rotation after changing to a
different coordinate system would generate an exception (runtime error).
21746 An Incident was resolved in which there was a text error on the form to assign fireproofing to frame
objects using the command Assign > Frame > Fireproofing. Two checkboxes were labeled "No
Fireprooofing on Top Flange". These labels have been corrected to say "Fireprooofing on Top
Flange". Checking these boxes adds weight to the structure, and this behavior has not changed.
Drafting
Incidents Resolved
17611 An Incident was resolved in which the length that was displayed when drawing line objects was
incorrect when certain drawing snaps were on. This was a display issue only.
18871 An Incident was resolved in which an exception (runtime error) was generated when drawing cables
using the "Fixed Length" or "Fixed Length and Angle" options.
19084 An Incident was resolved that addressed two problems with the general reference line: (1) An
exception (runtime error) was sometimes generated when modifying a B-Spline point on a general
reference line. (2) When adding points to a general reference line, they were always added to the
right, even when the left option was chosen.
16098 An Incident was resolved in which a runtime error could occur when using the command Edit >
16446 Extrude > Extrude Lines to Areas > Advanced > Define/Modify Path and moving the mouse to the
19088 data table.
SAP2000 V14.2.0 2010-03-23 Page 7

Modeling
Incidents Resolved
11960 An Incident was resolved in which the frame automesh did not work with curved frame objects.
This has been resolved so that curved frames now automesh wherever the straight elements used for
the analysis discretization intersect with other straight or curved frame elements or the edges of area
and solid elements, if such automeshing has been requested.
14924 An Incident was resolved in which the local axes for a frame object could be significantly changed
when the insertion point (cardinal point plus joint offsets) changed the orientation of the local-1 axis
so that it was no longer parallel to the line connecting joints i and j. In the most common cases, the
local-2 axis for a frame object having vertical joint alignment could change sign or the local 1-2
plane could be rotated about the vertical, depending on the direction of the offsets. This has been
changed so that the 1-2 plane and the sign of the 2-axis are first determined from the orientation of
the axis from joint i to joint j without offsets, and then the local-2 axis is rotated as needed to be
perpendicular to the final offset local-1 axis. Specifically, the cross product of the offset local-1 axis
and the original local-2 axis gives the offset local-3 axis, then the cross product of the offset local-3
and local-1 axes gives the offset local-2 axis. See also related Incident 18695.
17634 An Incident was resolved in which the command Edit > Edit Points > Merge Joints would merge all
selected joints located within the merge tolerance of each other, regardless of their merge numbers.
This has been changed so that only joints having the same merge number will be merged with each
other.
17680 An incident was resolved where cookie-cut meshing based on points could fail in some rare
situations due to tolerance problems.
18803 An Incident was resolved in which the bridge-deck section properties calculated for a spine model
of a composite steel U-girder bridge deck section was in error if the parameter B4 used in the
definition of the steel U-girder section was too large. This parameter now has no effect on the
section properties for a steel U-girder, but is only used to indicate single or double bearing support
for the girder in a bridge deck section.
* 18802 An Incident was resolved in which there could be a small error in the calculated section properties
19448 for the precast U-girder frame section. Approximately half of the left-side upper flange was omitted
from the shape if there was flange present.
Section Designer
Incidents Resolved
17534 An incident was resolved in which the thickness of a pipe section drawn in Section Designer
appeared to be changed when exported and re-imported using the database tables. This was a
display issue only. The correct thickness was being used for analysis and design, and no results
were affected.
18061 An Incident was resolved for Section Designer in which the nudge feature was not working for any
shape, and the reshaper tool was not working for structural shapes. These were drafting issues only
and did not affect any results.
18693 An incident was resolved where the units designation Ton in section designer was changed to Tonf
for consistency with the rest of the program.
* 20852 An Incident was resolved in which the PMM surface calculated in Section Designer for a concrete-
filled pipe section was not always symmetrical, and did not always close properly at the bottom
(pure-tension) side of the surface.
21185 An Incident was resolved in which Section Designer reported an incorrect centroid location for the
following cases: (1) A double-angle structural shape by itself having a non-zero rotation angle. (2)
For any structural shape having a non-zero rotation angle if that shape partially overlaps another
shape in the Section Designer section.
21454 An Incident was resolved for Section Designer in which merging two partially overlapping polygon
shapes sometimes created an spurious internal edge that prevented further editing of the section.
SAP2000 V14.2.0 2010-03-23 Page 8

22990 An Incident was resolved for Section Designer in which the program would sometimes become
unresponsive when trying to calculate the overlap of a pipe or tube structural shape with a solid
shape.
18754 An Incident was resolved in which Section Designer sometimes calculated a torsional constant of
19198 zero when using a more refined mesh, as controlled by the Section Designer command Options >
19392 Preferences. This occurred when memory limitations prevented calculation of the constant J from
completing. Now a more efficient method is utilized that achieves greater speed but uses less
memory.
Bridge Modeler
Incidents Resolved
13262 An Incident was resolved for the Bridge Modeler in which non-prismatic steel girders, modeled as
areas, would not always consistently connect together in the case where one bridge object ends at
the same point on a curved layout line as a second bridge object begins. This is an extremely subtle
point that affected very few models in those cases where the girder sections were identical and
continuous connection was to be expected.
15616 An Incident was resolved for the Bridge Scheduler in which a runtime error occurred when clicking
the Options button in a new schedule with no task defined.
16133 An incident was resolved where the insertion point was incorrectly labeled as the reference point in
the upper right-hand plot in the Bridge Section data form. This was a display issue only. There is no
effect on the model created or the results obtained.
* 17520 An Incident was resolved for the Bridge Modeler in which the weight of cross diaphragms was not
being included in bridge objects that were updated as spine (frame object) models. This affected
self-weight and gravity loads. The weight of the diaphragms was being included in bridge objects
updated as area and solid objects. The mass of the diaphragms was being included for inertial
purposes in all linked models, including spine models. The weight of the cross diaphragms in spine
models is now being modeled as zero length link elements at the cross-diaphragm locations.
17594 An Incident was resolved in which the Bridge Modeler, in certain circumstances, would create a
bearing that was not properly connected to the bottom of the corresponding girder at the bent. This
could occur when the girder dimensions changed at a continuous bent and the grade was non-zero.
18587 An incident was resolved where viewing the available cap beam sections on the "Bridge Bent Data"
form changes the girder support condition to from "Integral" to "Connect at Girder Bottom Only". If
the OK button is clicked, this change is applied to the bent.
18689 An Incident was resolved for the Bridge Modeler in which a sharp kink was sometimes created at
the abutment in the spine model of a bridge object for which an offset reference point was specified
for the deck section.
19083 An Incident was resolved for the Bridge Modeler in which the depth of generated diaphragms did
not match the girder depth when nonprismatic steel girders were used in the deck section. The
diaphragm depths were being calculated based on the depth of the girder at the start of the
nonprismatic variation. Now the depth of the diaphragm varies with the depth of the girder.
19518 An Incident was resolved for the Bridge Modeler in which steel U-girders used in a bridge deck
section may be upside down or positioned incorrectly in the generated model if the girders are of
different sizes.
20523 An Incident was resolved in which tendons in certain bridge models were not being properly
connected to the containing superstructure elements modeled as frames. This was due to internal
tolerances, and was not common.
21409 An Incident was resolved for the Bridge Modeler in which an error was generated when updating
the linked model for a bridge object with nonprismatic steel girders using multiple steel materials.
21796 The Bridge Modeler now provides a warning when updating the linked model for a bridge object in
which the number of girders changes from one span to the next at a continuous (single-bearing)
bent. In such a case, girders that are not continuous across the bent may not be supported on the
leading span. The user has the option of manually adding the needed bearings, or using two separate
SAP2000 V14.2.0 2010-03-23 Page 9

bridge objects.
16474 An Incident was resolved for the Bridge Modeler in which deck sections specified to have zero-
16477 length top slab overhangs along with differing thicknesses for the main top slab and the top-slab
overhang would generate area-object linked models with vertically oriented area objects at the
edges of the deck.
16796 An Incident was resolved in which the option for the superstructure mesh to NOT match the bent
18742 alignment was not working.
* 18659 An Incident was resolved in which the frame section properties generated for the bridge
19235 superstructure in spine models sometimes had a zero value for the torsional constant J. This occured
when the section was large or detailed, and memory limitations prevented calculation of the
constant J from completing. This problem was introduced in SAP2000 V14.1.0 when more accurate
meshing for torsion was implemented. Now a more efficient method is utilized that achieves greater
speed but uses less memory. The value of J is calculated when the analysis model is generated. This
means that J values for bridge deck sections may be reported in database tables as zero prior to
running the analysis. After the analysis, the correct values will be shown in the tables.
* 18804 An Incident was resolved for the Bridge Modeler in which an error was generated when updating
18828 the linked model for a steel I-girder deck section with girders modeled as areas and having beam-
19273 type cross diaphragms.
19338
19372
20031 An Incident was resolved for the Bridge Modeler in which using large offsets of the deck reference
20294 point with respect to the layout line, combined with skewed supports, sometimes resulted in poor
meshing or invalid linked models being created that would not run.
Loading
Incidents Resolved
12481 An Incident was resolved in which the frame loads were only applied for the first instance of a load
pattern specified in a nonlinear static or nonlinear direct-integration load case if that load pattern
was specified multiple times in that load case. This only affected frame elements and it did not
affect any other load-case type. This is not a common problem.
* 12794 An Incident was resolved in which projected loads on frame objects defined in alternate coordinate
systems were not correctly applied or displayed. Loads were transformed to the global system, then
projected on the element using global load components. This could result in the load being applied
with a somewhat different direction and magnitude than intended. Loads applied in the global or
element local coordinates systems were not affected. Non-projected loads applied in alternate
coordinate systems were not affected. This error was introduced in v12.0.0. Models having this type
of loading should be re-verified.
* 18310 An Incident was resolved in which uniform loads applied to shell elements in the Global or other
fixed coordinate systems were not always being properly rotated into the element local system,
possibly resulting in the load being applied in the wrong direction. This did not affect self-weight,
gravity, or pressure loads, and it did not affect uniform loads applied directly in the element local
coordinate system. This error was introduced in v12.0.0. Models having this type of loading should
be re-verified.
* 18572 An incident was resolved where the uniformly distributed shell loads were not being fully applied in
certain rare cases. This only occurred when the shell uniform load was used for the generation of
notional loads and the area object was further meshed. The first element of the meshed area object
was loaded, but not the remaining elements for that object. This affected Versions 12.0.0 to 14.1.0.
Models satisfying these conditions should be reevaluated.
* 18583 An Incident was resolved in which joint displacement loads assigned to a load pattern were not
applied in a given load case if that load pattern was listed after any acceleration load in the list of
applied load patterns for that load case. Displacement loads were correctly applied in load patterns
listed before any acceleration load, or if there were no acceleration loads applied in the load case.
SAP2000 V14.2.0 2010-03-23 Page 10

* 20091 An Incident was resolved in which deleting a load pattern could, in rare cases, delete load
assignments to objects that are part of another load pattern. This only affected deformation and
target-force loads that were assigned to frame/cable/tendon objects, and only for assignments to
load patterns that were defined after the deleted load pattern. This did not affect any other type of
object, or any other type of force, strain, or temperature load.
20943 An Incident was resolved where load patterns specified to be of type Wave, and for which no auto-
generated wave loading was defined, were sometimes applying concentrated and distributed span
frame load assignments from other load patterns.
* 16145 An Incident was resolved in which tendons that are modeled as loads did not always properly load
16269 the structure where one end of a discretized tendon segment was not inside any bounding box. This
16883 could create unbalanced loads, causing large displacements and/or reactions. Now, when any part of
18508 a discretized tendon segment falls inside any bounding box, self-equilibrating loads are applied to
the structure. No load is applied for any discretized segment that lies entirely outside all bounding
boxes.
Analysis
Incidents Resolved
11190 An Incident was resolved in which solver times were sometimes reported in the analysis log file as
being negative for nonlinear static and time-history load cases.
11231 The documentation of the link element in the CSI Analysis Reference Manual has been updated to
describe the correct use of fixed DOF (degrees of freedom (DOF): (1) Links with fixed DOF should
not be coupled with other fixed links or connected to constrained joints. (2) Fixing fewer than all 6
DOF can lead to loss of mass coupling between rotational and translational DOF, which can affect
the dynamics of the structure if large mass or rotational inertias are present at the connected joints.
(3) When all six DOF are fixed, the translational and rotational inertia is handled with no loss of
coupling.
* 14485 An Incident was resolved in which the incremental P-delta effect in frame elements was not always
18785 correct for nonlinear static and nonlinear direct-integration time-history load cases. The error could
be significant in an increment when the axial load was changing and large lateral displacements
were already acting on the element. This was of primary concern for nonlinear time-history load
cases, and for some nonlinear static cases where many increments were used. Most nonlinear static
load cases used for design apply the load in one step and were not affected. Linear load cases using
the stiffness from a nonlinear P-delta case were not affected. Large-displacement analysis was not
affected. See Incident 21284 for a related issue for shell elements. Solid, link, and other elements
were not affected.
15195 An Incident was resolved in which unexpected numerical results could sometimes be generated for
very fine discretization of tendons modeled as elements. This was caused by the merge tolerance
affecting the constraint equations used to connect the tendons to their containing structural objects.
15926 An Incident was resolved in which memory utilization continued to grow for very long analyses
21119 with a large number of nonlinear iterations. This would, in rare cases, cause the analysis to
terminate prematurely. No results up to that point were lost or affected.
* 16015 An Incident was resolved in which the structural period of a model could change when the local
axes of a joint that was connected to a link element with fixed degrees-of-freedom are rotated.
Rotating the joint local axes from the global system couples the constraint equations, and that
coupling was not always properly handled. This has been corrected. However, the period may still
be affected by rotating joint local axes if fewer than all six link degrees-of-freedom are fixed, due to
loss of some off-diagonal mass terms. This can be avoided by using stiff rather than fixed link
degrees-of-freedom in that case.
* 16264 An Incident was resolved for influence-based moving load analysis in which the reactions at a
restrained joint did not include the influence of loads applied directly at that joint. This only
affected models in which the loaded surface was modeled with shell or solid elements and the
restraints were connected directly to the loaded surface, hence most models created by the Bridge
SAP2000 V14.2.0 2010-03-23 Page 11

Modeler were not affected. Only the restraint reactions themselves were affected. All other response
quantities were correct, including displacements, forces, stresses, reactions at spring supports, and
reactions at restraints due to loads not at the restraint itself.
16270 An Incident was resolved in which using the Construction Scheduler with a locked model
sometimes caused the analysis to re-run automatically, deleting previous results.
16761 An Incident was resolved in which the influence surface was not always calculated correctly for
18369 bridge lanes whose width was greater than their length. In some cases this would result in incorrect
moving-load analysis results, in other cases the analysis would terminate with an error message.
16932 An incident was resolved where an error was sometimes generated when creating the analysis
model with the mesage "Error in Creating Analysis Model" when "Updating multi-step moving load
case values" because of memory limitations. More efficient use of memory will now reduce the
likelihood of this problem.
17158 An Incident was resolved in which frame end releases applied as a named set during a staged-
construction load case were applied separately to each element when a frame object was
automatically meshed rather than to the object as a whole. This could result in the meshed frame
object becoming unstable, preventing convergence of the analysis.
* 17292 An Incident was resolved in which the mass value, when computed from loads used as the mass
17887 source, had double the mass value at the third joint in triangular area elements (shell, plane, and
20515 asolid). This would lead to 33% extra total mass for each triangular element, and the acceleration
loads were correspondingly increased. Similarly, when solid elements were collapsed to create 5, 6,
or 7-noded elements, the mass values at the collapsed joints were duplicated when mass was
computed from loads. In the most common, default case where mass was computed from material
mass density, there was no duplication of mass or acceleration load.
* 17401 An Incident was resolved in which load applied in a user-defined coordinate system is zero if that
17918 coordinate system is identical to the global coordinate system. This does not affect the majority of
19158 cases where load is applied in element local coordinate systems, the global system, or user-defined
systems that are different from global.
* 17649 An Incident was resolved in which joint displacements for a moving load case are reported
incorrectly if the joint has a rotated local coordinate system. This has no effect on joints that have
their local coordinate system equal to the global system, which is the usual and default case.
* 18365 An Incident was resolved in which joint reactions for an influence-based moving load case did not
include any contribution from connected solid or plane elements. Force transmitted to the restraints
from frame, shell, and link elements were correct.
18409 An Incident was resolved in which Plane and Asolid elements were always displayed for staged
construction load case results even when they are not present in the stage being displayed.
18682 An Incident was resolved in which specifying load-case damping as a function of period would
generate an error message when the analysis was run, producing no results. Specifying damping as a
function of frequency worked as expected.
* 18808 An Incident was resolved in which the base reactions were sometimes incorrect when restrained
18937 joints were present with local coordinates different from the global directions.
18980
19191
19302
* 18949 An Incident was resolved in which thermal loading of solid elements in nonlinear static and
nonlinear direct-integration time-history load cases did not produce the correct stresses. The
response of the rest of the structure was correct, including displacements, reactions, and
forces/stresses in other elements. Only the stresses in the thermally loaded solids were incorrectly
reported.
19214 An Incident was resolved in which an error was generated during analysis when a fiber hinge was
using a material with the Hysteresis Type for the stress-strain curve set to be Elastic. This problem
did not occur for Hysteresis types of Kinematic or Takeda.
19287 An Incident was resolved in which an error message was generated during analysis when strain load
19409 was assigned to a solid object, and no analysis results were produced. Now strain loading works
correctly for solids.
SAP2000 V14.2.0 2010-03-23 Page 12

* 19433 An Incident was partially resolved in which frame PMM hinges sometimes exhibited excessive
hardening when the stress point was near to the tension region of the interaction surface. Further
improvements will be made in a future release. Note that it is not expected that the moment-rotation
behavior will exactly follow the backbone curve when the load point on the PMM surface moves
from the point of initial yield.
19486 An incident was resolved where an error was sometimes generated when trying to run an analysis of
a moving-load case when no lanes had been defined. This happened in certain models if the bridge
license was not obtained.
* 19522 An Incident was resolved for the Bridge Modeler in which the reported superstructure forces,
moments, and stresses were, in certain cases, much too large at the abutments. This could occur
when edge constraints were created at the abutments to handle mismatched meshes between the
deck and the diaphragms. This was a localized reporting error only and did not affect the behavior
or results in the rest of the structure.
20527 An Incident was resolved in which linear buckling, steady-state, and PSD load cases would not run
in the Plus level, only in the Advanced level. Now these types of load cases can be run in the Plus
and the Advanced levels. Also, hyperstatic load cases can now be run in all levels (previously they
required the Advanced level).
20936 An Incident was resolved in which target-force targets were not always correctly met in staged-
construction load cases when the same load pattern was assigned multiple times (e.g., to different
groups) in the same stage. The target-force iteration would converge to incorrect values. The
behavior was correct if the load pattern was assigned just once to a single group that contained all
the frame/cable objects having the desired target-force loads.
21226 An Incident was resolved in which memory utilization continued to grow slowly when a large
number of analyses were run in the GUI process during a single SAP2000 session. This would, in
rare cases, cases an analysis to terminate prematurely. No results up to that point were lost or
affected.
* 21284 An Incident was resolved in which the incremental P-delta effect in shell elements was not always
correct for nonlinear static and nonlinear direct-integration time-history load cases. The error could
be significant in an increment when the axial load was changing and large lateral displacements
were already acting on the element. This was of primary concern for nonlinear time-history load
cases, and for some nonlinear static cases where many increments were used. Most nonlinear static
load cases used for design apply the load in one step and were not affected. Linear load cases using
the stiffness from a nonlinear P-delta case were not affected. Large-displacement analysis was not
affected. See Incident 14485 for a related issue for frame elements. Solid, link, and other elements
were not affected.
* 22452 An Incident was resolved in which the effect of temperature and strain load was not being included
in linear buckling analysis for shell and solid elements, and the effect of temperature load was not
being included in the nonlinear P-delta effects for solid elements.
Frame Design
Incidents Resolved
12763 An Incident was resolved for steel frame design in which an error message was generated for certain
15590 design codes when the input value of Fy was smaller than the code-mandated value of Fr (10 ksi for
rolled shapes or 16.5 ksi for welded shapes). The program did not report any results in this case and
the error was obvious. The affected design codes are "AISC-LRFD93", "UBC97-LRFD", "API
RP2A-LRFD 97", and "AISC-LRFD99".
* 12843 An Incident was resolved for steel frame design using code “BS5950 2000” and "BS5950 90" in
which the incorrect strut curve was being used for the axial-capacity calculation for an H-section
(an I-Section with depth/width < 1.2 (BS5959:2000 1.3.23, BS5950:1990 1.2.22)). H-sections and I-
sections are assigned with different sets (major and minor) of strut curves (BS5959:2000 Table 23,
BS5950:1990 Table 25), and hence, different Robertson constants (BS5959 App. C) are used for the
axial capacity calculation. Capacity of H-sections were taken unconservatively higher. I-sections
SAP2000 V14.2.0 2010-03-23 Page 13

were correct.
14675 An Incident was resolved for concrete frame design in which the program sometimes would declare
a concrete column member as "O/S" in the right-button click design display while not declaring the
same member as "O/S" in the graphical display. This only occurred when the PMM ratio fell
between the user-specified Utilization Factor Limit and 1.0. If the Utilization Factor Limit is set to
1, this problem did not occur. The graphical display was checking the PMM ratio against a value of
1.0 rather than the Utilization Factor Limit. All concrete frame design codes were affected.
15992 An Incident was resolved in which the virtual work calculated for frames was incorrectly including
19319 the load acting directly on the element, rather than just using the stiffness forces. The effect of this
was generally small. In some cases this could affect the results of displacement and period
optimization used in frame design. The computation of virtual work for cables and shells has been
similarly corrected. However, element loads are currently still included in the virtual work for solid,
plane, and asolid elements.
16085 An Incident was resolved for steel frame design in which the panel-zone design shear force used to
determine the doubler plate thickness was sometimes calculated incorrectly. This design shear force
is the difference |Vb|-|Vc|, where Vb is the shear force from the beam flanges connecting to the
joint, and Vc is the shear force from the column above the joint. Vb is calculated as the larger of the
capacity moment or the factored moment from the beams, divided by their mean flange distance.
Normally the capacity moment governs, and this was being calculated correctly. However, when the
factored moment governed, the design could be too conservative, since the absolute values of plate
forces due to moments from the two beams were added together, but should instead have been
added using their algebraic values, that is, using vectorial addition. The affected codes are
"AISC360-05/IBC2006", "AISC-LRFD99", "AISC-ASD 01", "UBC97-ASD", "UBC97-LRFD",
"CAN/CSA-S16-01".
16410 An Incident was resolved in which steel frame design using the "AISC360-05/IBC2006" code
generated error messages when designing I-sections with different flange widths or thickness. No
results were produced for these sections.
16780 An Incident was resolved for steel frame design using code “AISC360-06/ICB2006” in which an
error message was generated during right-button click on a previously designed L-section. No
results were produced for the design after right-button click on such sections. The behavior was
correct for other section types using the “AISC360-06/ICB2006” code, and it was also correct for
all sections types when using any other code.
* 17250 An Incident was resolved for steel frame design in which the deflection reported for cantilevered
members was not the tip deflection, but rather was the in-span deflection relative to the chord, the
same as for members supported at both ends. Now the effect of the rotation at the cantilever support
is considered. Only the results of cantilever beams were affected. All steel frame design codes are
affected by this change.
18478 An Incident was resolved in which the description for field “FramingType” and some other fields
was incomplete for the Design Detail tables. This is a cosmetic issue only.
18646 An incident was resolved for SAP2000 steel design code for which the steel frame design
preference variables "Is Doubler Plate Plugwelded?", "Reduce HSS Thinness?" and/or "Consider
Deflection?" in the output table do not match the input values in the preferences form. The affected
codes are "AISC360-05/IBC2006", "AISC-ASD01", "AISC-LRFD99", "CAN/CSA-S16-01" for the
first two values, and all steel design codes for the last value.
* 18840 An Incident was resolved for steel frame design using code AISC 360-05/IBC2006 in which the
stress-based interaction equation H2-1 was not being used as required for sections which are not
doubly symmetric and for which Iyc/Iy is outside of the range 0.1 to 0.9. This only affects the singly
symmetric I-sections with Iyc/Iy outside of the range 0.1 to 0.9, all T-sections, all double-angle
sections with Iyc/Iy outside of the range, and all equal-legged angle sections. For singly symmetric
I-sections, the old implementation was slightly unconservative with a maximum factor of 8/9. For
T-sections, double-angle sections, and equal-legged angle sections, old implementation was
sometimes unconservative with a maximum factor of 8/9, sometimes conservative, and sometimes
matching.
18849 An Incident was resolved for steel frame design using the Canadian “CAN/CSA-S16-01” code in
SAP2000 V14.2.0 2010-03-23 Page 14

which the beta factor, which is used to calculate the stress ratio per CSA S16-05 section 13.8.2, was
being computed incorrectly. This affected only the stress ratio component of the minor axis
bending. Previously the value Lambda_x (33) was used in the expression of Beta. Now Lambda_y
(22) is correctly used. This error was marginally unconservative.
18858 An Incident was resolved for steel/concrete/aluminum/cold-formed frame design in which an
exception (runtime error) was sometimes generated when calculating the K factors during design if
the model contained line objects which are not structural members, i.e., were not assigned any
frame section properties.
18945 An Incident was resolved for steel-frame design using the “Indian IS:800-1998” code in which the
reported Kl/r ratios for major and minor directions were swapped. The calculated values were
correct.
* 18969 An Incident was resolved for concrete frame design using the “Eurocode 2-2004” design code in
which the alpha-cc parameter specified in the design preferences was not working. The alpha-cc
was not connected to the interaction surface generation.
18996 An Incident was resolved for database table "Steel Design 2 - PMM Details - AISC360-05-
IBC2006" in which the reported values of K1major and K1minor were not correct in the database
tables. This was a display issue only. The correct values were being used in the design, and no
results were affected. In addition, steel frame design using the "AISC360-05/IBC2006" code has
been enhanced by imposing a limit on K2 factors: K2major >= 1, K2minor >= 1 to help avoid user
errors.
* 19210 An Incident was resolved for steel frame design using the Eurocode 3-2005 design code in which
the Nc,Rd values were incorrectly computed. The calculation of the non-dimensional slenderness
(lambda_bar) was previously using (pi)^2*E*I/L^2 rather than Cl. 6.3.1.3(1) from the code.
* 19303 An Incident was resolved for concrete column design using any design code in which the PMM
interaction surface used for design was not being updated when design preferences were changed
after the first time design was performed following an analysis. Unlocking the model and re-running
the analysis would update the PMM surface correctly. Now the PMM surface is updated every time
a design preference is changed, even without re-running the analysis.
* 19304 An Incident was resolved for concrete frame design using the “Eurocode 2-2004” code in which the
calculated imperfection inclinations (theta) were not correct if the base length unit for the model is
anything other than meter. Since the alpha_h parameter is always taken in between 2/3 and 1, the
effect of this error was limited. If the base length unit was mm, cm, or inch, the resulting theta was
unconservative.
19517 An Incident was resolved for the Eurocode 3-2005 steel design check in which the PMM
demand/capacity ration results had the major and minor ratios swapped when the interaction
equations 6.61 or 6.62 were used. The total ratio was still correct.
* 19528 An Incident was resolved for steel frame design using the "Chinese 2002" code in which the design
was still using the gross area for design under clause 5.2.1 even when the "Gross Area / Net Area"
design overwrite was specified. This has been corrected so that now the net area is used when this
ratio is specified.
* 20248 An Incident was resolved for steel frame design using "Eurocode 3-2005" in which the calculation
of the interaction ratios could be incorrect in the case where lateral torsional buckling governs per
equations 6.61 or 6.62. The value of lamLT was being taken as zero for these equations. The
previously reported result could be unconservative. For other capacity checks, the correct value of
lamLT was being used.
20551 An Incident was resolved for concrete frame design using the "Chinese 2002" code in which the
design would fail when a column section had been assigned to a horizontal member. Now the beam
design is carried out, using information from the PMM surface as needed.
* 22646 An Incident was resolved that corrected two minor issues for steel frame design using "Eurocode 3-
2005": (1) The Kl/r for angle sections was calculated along the axes parallel to the legs of the angle
rather than the principal axes. This may unconservatively affect the axial capacity and slenderness
check in some cases. (2) Members with very small axial load were being treated as being of Class 4,
and therefore not checked or designed. Now such members may be treated as being of Class 1 if the
small axial force is compressive, and therefore they will be checked or designed.
SAP2000 V14.2.0 2010-03-23 Page 15

Bridge Design
Incidents Resolved
17157 An Incident was resolved in which the bridge superstructure-design shear check for concrete box
girders did not produce results for certain models, even though no error message was given.
18714 An Incident was resolved in which bridge design-request results were sometimes lost after exiting
from SAP2000 and re-opening the model file.
18797 An Incident was resolved in which it was possible to modify a load combination that was used for a
bridge superstructure design request that had already been run. Now if you try to change the
definition of such a load combination, you will be warned that the design results will be deleted and
given the option to cancel the change.
* 18799 An Incident was resolved for bridge superstructure design in which the vertical location of the three
stress points at the top of prestressed concrete I-girders and U-girders was in error by an amount
equal to the top flange thickness. This only affected the case where the spine model was used.
18862 An Incident was resolved in which the bridge design for concrete box girder structures may
generate an error message and fail to run when a tendon position at one or more of the design
stations is located so that its horizontal plane cuts a web at more than two points. This is not
common.
* 18889 An Incident was resolved in which the tabulated stress results for the "AASHTO STD 2002" bridge
design stress check for prestressed concrete box girder superstructures were not being scaled by the
corresponding demand-set limit factor. For each demand set, the reported stress should be divided
by the limit factor so that the controlling stress can be compared between the various demand sets to
determine the controlling value. This was properly done during the design check and for the plotted
results. Only the tabulated results were not being scaled.
* 19494 An Incident was resolved for bridge design using the AASHTO stress check of prestressed concrete
box-girder or precast composite-girder superstructures in which the reported stress values were not
scaled for the live load distribution factor (LLDF). This affected that portion of the stress coming
from the live load, not the portion of the stress from dead or other types of loads.
* 21013 An Incident was resolved in which the stresses reported for bridge design stress-checks may be
incorrect for unsymmetrical girders when the LLDF (live-load distribution factors) are computed by
analysis. The effect of the product of inertia I23 was not being included. This affected the slabs of
precast girder composite sections, as well as the exterior girders of multi-cell concrete box sections.
This did not affect stress checks when LLDF were code-calculated, user-specified, or uniform. This
also did not affect the concrete box stress-checks when LLDF are not used.
* 21014 An Incident was resolved in which the stresses reported for bridge design stress-checks may be
incorrect for precast-composite and multi-celled box girders when using LLDF (Live-Load
Distribution Factors). The moments used to compute the stresses were being computed at the girder
output point rather than at the centroid of the girder where the moments of inertia were computed.
This also did not affect the concrete box stress-checks when LLDF were not being used.
22031 An Incident was resolved in which bridge seismic design for seismic design category (SDC) "D"
would not create a pushover load case when there was no bent or abutment property assigned to the
start end of the bridge object.
17902 An Incident was resolved in which the bridge flexural design check would not produce any results
19367 for deck sections of type Advanced Concrete Box Girder having two or more interior girders.
* 21008 An Incident was resolved for bridge seismic design in which the automated determination of the
21033 SDC (seismic design category) was not always correct for AASHTO2007, IBC2006, and
21053 NCHRP2007 response-spectrum curves. The value S1 was being used to determine the SDC rather
than the correct value, SD1 = Fv * S1. For other codes and user-defined functions, the correct value
of SD1 was being obtained directly from the curve, so there was no error.
SAP2000 V14.2.0 2010-03-23 Page 16

Incidents Resolved
* 10962 An Incident was resolved in which loads applied to joints, solids, links, plane, and asolid elements
12039 were not included in the restraint reactions at joints connected directly to those elements for
17934 nonlinear static and nonlinear direct-integration time-history analysis. Note that this only applies to
the load applied directly to those elements connected to the restraints, not to load applied elsewhere
in the structure. This did not affect frame or shell elements. This did not affect the reactions
reported at spring supports or one-joint links. This was a reporting issue for restraint reactions and
base reactions only and did not affect displacements, element stresses or forces, or any other
response quantity. Because of these changes, the base shear reaction reported for the nonlinear
direct-integration time-history load case in verification Example 6-010, "SUNY Buffalo Eight-Story
Building with Rubber Isolators", differs by 0.39005% from the published results for Version 14.0.0.
This is a slight improvement since the mass of the isolators is now accounted in the reaction, and is
considered acceptable.
12065 An Incident was resolved in which the frame force and moment diagrams for envelopes were not
correctly using the colors set under Options > Colors to represent positive and negative range values
when envelopes were displayed. Now the colors used to display positive and negative range values
are correctly displayed but are intentionally set to be the same.
12533 An Incident was resolved in which principal stresses were reported for load combinations even
though they were only calculated for some of the load cases in the combination. For example,
principal stresses reported for a load combination that added a dead load case to a response-
spectrum load case were computed for the dead load only. Now, principal stresses will be reported
as zero for any load combination that includes a load case for which principal stresses cannot be
computed.
13551 An Incident was resolved in which an error sometimes occurred when plotting energy response for
19226 modal time-history load cases.
* 13732 An Incident was resolved in which load combinations of the additive type did not give correct
results when multi-step static load cases were included. This did not affect other types of load cases
and other types of load combinations, such as the enveloping type.
15072 An Incident was resolved in which the scaling of the deformed shape of a cable sometimes appeared
to be incorrect. This was because the undeformed shape is not well defined when there is no load,
and exagerating the deflections from that shape can be misleading. This has been resolved by
always scaling the deflection of the cable relative to the deformed chord by a factor of unity,
regardless of the scale factor used for joint displacements. This was a cosmetic issue only.
16122 An Incident was resolved in which the Report Setup would fail to respond after creating a report
using the default file option for table formats.
16187 An Incident was resolved in which shell influence lines and surfaces were sometimes incorrectly
plotted because the components were incorrectly being selected by the form.
16925 An incident was resolved where certain section cuts defined using quad cutting planes would not
produce any results.
17101 An incident was resolved where incorrect stress contours could be displayed on screen for staged-
construction load cases for an active element connected to an inactive element when the contours
were displayed with averaging turned on. The zero stress value in the inactive element was being
averaged with the stress in the active element. This affected stresses for shell, plane, asolid and solid
elements, as well as resultants for shell elements. This did not affect contour plots when averaging
was turned off, and it did not affect the values in the database tables, which are not averaged.
* 17479 An Incident was resolved in which the element joint forces reported in database tables were always
17605 given in the global coordinate system rather than in the joint local coordinate system .
17741 An Incident was resolved in which the backbone curve plotted for interacting (PMM, PM, MM)
hinges was not always shown as symmetrical when using the command Display > Show Hinge
Response. This was a display issue only. No analysis results were affected, since the backbone
curve plotted is for reference only and is not the backbone curve used in the analysis.
17890 An Incident was resolved in which, in rare cases, stress contours for plane/asolid elements would
SAP2000 V14.2.0 2010-03-23 Page 17

plot outside of the element boundaries due to an internal tolerance problem. This was a display issue
only. The analysis results were correct.
17891 An Incident was resolved in which the bridge design shear check could produce results that would
generate an exception (runtime error) when plotted using the Display > Show Bridge
Forces/Stresses command. This could occur when design output stations were closely spaced.
Design results were otherwise not affected by this problem.
18064 An Incident was resolved in which the deformed shape for envelope load combinations sometimes
showed cable elements disconnected from other elements. This was a display issue only, and was
due to the way the relative deflections of the cable with respect to the joints were being scaled. A
scale factor of unity on the relative deflections of the cable are now always used regardlesss of the
scaling of the joint deflections. Numerical results were not affected.
* 18568 An Incident was resolved in which the material take-off for frame section properties was not always
correct when there were cables present in the model.
18715 An Incident was resolved in which stress-contour plots were not shown for some solid objects when
a 2D view was displayed.
18792 An Incident was resolved in which the Bridge Seismic Design Report was not using the supplied
format file to control table layout in the report. This only affected the number and size of the
columns shown in the tables. The values reported were correct.
18793 An Incident was resolved in which the behavior of the Bridge Response Display form was not
always correct when changing between Envelope Max, Envelope Min, and individual steps for the
response of multi-stepped load cases. This did not affect the correctness of the plotted or tabulated
results, just the options shown on the form.
* 18892 An Incident was resolved in which plot functions for shell, plane and solid stresses were not
correctly accounting for non-zero offsets specified in the plot-function definition. Note that if
offsets are specified that fall outside of the object, results will be plotted for the nearest point
element that is part of the analysis model for that object.
19099 An incident was resolved where the program would stop responding when attempting to display
hinge response that required more memory than was available. Now a warning message is given
that more memory is needed to display the desired response.
19152 An Incident was resolved in which an error message was generated for certain models when using
the command Display > Show Hinge Results after opening the model.
* 19306 An Incident was resolved in which the stresses displayed for the bridge superstructure were
incorrect when the entire section was not present during staged construction. Now stresses are
reported separately for the beam and slab of composite deck sections (using steel or precast-
concrete beams), but not for the composite girder (combined beam plus slab). Furthermore, these
beam and slab stresses are computed on a girder-by-girder basis rather than for the entire deck
section. Stresses for the beam and slab of composite sections are only available when the linked
model is udpated as areas or solids, not as a spine model. For integral deck sections (concrete box
girder, flat slab, tee-beam), stresses are computed on the entire section or the entire girder, and do
not account for partial sections during staged construction.
20913 An Incident was resolved where error messages were being generated when displaying frame/cable
force results for a construction stage in which cable objects had been removed from the structure.
This did not affect the accuracy of any results.
21023 An Incident was resolved in which an error was generated when graphically displaying link results
for a modal time-history load case if the links were representing area springs.
21188 An Incident was resolved in which it was not possible to generate a report of a model with spring
supports if the report contained a picture showing the springs.
21817 An Incident was resolved in which an error message was sometimes generated when trying to
display hinge results for a model with multiple different types of fiber hinge definitions. No result
were affected.
* 22110 An incident was resolved where the vertical coordinate of the girder force output points was not
correctly calculated for steel I and U girder bridges based on the user input. This affected the
moment M3 and torsion T reported for individual composite girders using the command Display >
SAP2000 V14.2.0 2010-03-23 Page 18

Show Bridge Forces/Stresses. It did not affect the moments for the overall section, or any other
force or moment for the individual girders. This was a reporting issue only. Design results were not
affected.
Database Tables
Incidents Resolved
14944 An incident was resolved in which an error was being generated when displaying layered shell
results in the database table “Element Forces - Area Shells”. No results were being produced in the
table. This did not affect the non-layered homogenous shell.
15552 An incident was resolved where the Joint column in the generalized displacement data form was
incorrectly shown alphabetically sorted. This was a display issue only, and did not affect the
definition of the generalized displacements unless the OK button was clicked.
16271 An Incident was resolved where the File > Create Report command was not using the default format
file unless specifically requested by the user.
16399 The two fields “MirrorAbt2” and “MirrorAbt3” have been removed from the database table “Frame
Local Axes Assignments 1 – Typical”. Field “MirrorAbt2” was not being used since it actually
defined elsewhere in table “Frame Insertion Point Assignments”. Field “MirrorAbt3” had no effect
on the model except to set the location of the bounding box. When opening models from previous
versions, this value internally will now be set to “No”. This will have no effect on the analysis or
design results of a model from a previous version unless this value was previously set to “Yes” for a
frame object containing tendons, and the tendons change from being inside to outside of the box, or
vice versa.
17818 An Incident was resolved in which the database tables did not include the following information for
load combinations used in steel, concrete, aluminum, or cold-formed frame design: (1) The design
limit-state type (Strength, Deflection) for user-defined load combinations that had been selected for
design. (2) The parameters defining automatically generated design load combinations.
17883 An Incident was resolved in which canceling interactive database editing would sometimes cause
previously deleted properties, objects, and load assignments to reappear in the model. This would
not occur if the model was saved prior to entering interactive database editing.
18193 An incident was resolved where stresses were not reported for triangular asolid elements in the table
named Element Stresses - Area Asolids.
18586 Notional load data has been added to the database tables.
18787 An Incident was resolved in which the database tables for bridge temperature-gradient loading
could not be imported when included in the same file as the tables for the bridge object itself.
18923 An Incident was resolved in which the joint response spectrum tabulated using command Display >
Show Tables > Analysis Results > Structure Output > Named Set Data > Table: Joint Time History
Response Spectrum presented period values instead of frequency values when frequency values
were requested. This only affected the tabulated results, not the plotted results.
19075 An incident was resolved where load cases that were referenced in hinge definitions could not be
properly imported from database tables.
19202 An Incident was resolved in which the error message "Error cleaning frame section arrays" was
sometimes generated after using the interactive database editor and then saving the model. No data
was affected.
19230 An Incident was resolved in which an exception (runtime error) was sometimes generated when
importing load combination definitions from database tables as an addition to an existing model.
19255 An Incident was resolved in which solid property assignments were not properly imported from
database tables when no frame section property definitions existed in the model.
19502 An Incident was resolved in which analysis results tables did not include results for hyperstatic load
cases. The on-screen display of results was available.
19519 An Incident was resolved in which the design-results database tables “Bridge Super Design 01 -
Design Result Status” and “Bridge Super Design 02 - AASHTOSTD02 – CboxStress” were not
available for bridge design using code “AASHTO STD 2002”, and the former table was not
SAP2000 V14.2.0 2010-03-23 Page 19

available using code “JTG-D62-2004”.
20479 An Incident was resolved that corrected minor problems with interactive database editing: (1) After
any change is made through the interactive database, the load case selected for mass and stiffness
text file output resets to NONE. (2) Changes done to the "Project Information" table through the
interactive database do not get applied.
20668 An Incident was resolved in which the database tables "SD Stress-Strain 06 - Concrete Mander
Confined Circle" and "SD Stress-Strain 07 - Concrete Mander Confined Rectangle" were not being
written to RTF files.
21053 An Incident was resolved in which an error message was being generated when displaying tables for
bridge seismic design results for the case where the seismic design category (SDC) was less than
"D" and there were no frame hinges present in the model. This message did not affect any results.
Data Files (.SDB, .S2K, .$2K)

Incidents Resolved
16291 An incident was resolved where models from Version 11 and older may not have had a material
property specified for the rebar in some concrete frame section properties, and this was causing
errors when opening the model files in Version 12 and later. This has been resolved by assigning a
default rebar material property to such concrete frame sections when opening the older model.
17896 An incident was resolved where Version 10 models with multilinear area spring properties could not
be opened in later versions of the program.
18047 An Incident was resolved in which the .SDB file could not be opened if it was saved after a serious
error occurred when using the database. Now a warning message is displayed and the corrupted
database formatting data is reset to default values.
18299 An incident was resolved where text file import errors related to area object auto meshing and
general vehicle length effects caused a model to have an error during analysis.

Incidents Resolved
16408 An Incident was resolved in which staged construction analysis would fail to complete a stage in
which objects are being removing at the same time target force loading was being applied. No
results were produced for that or subsequent stages in the load case.
* 22202 An Incident was resolved in which the following OpenAPI functions in CPointObj were not
converting length from current units to model database units: AddCartesian, AddCylindrical, and
AddSpherical. The given lengths were being assumed to be in database units. Now they are treated
as being current units and are converted to database units.
Incidents Resolved
11401 An Incident was resolved in which CSI/2 files could not be imported if there was an additional
period (.) in the filename anywhere before the extension.
12542 An Incident was resolved in which reserved keywords were not properly used for the import and
export of CSI/2 Step file.
12570 An Incident was resolved in which STAAD files containing general sections defined in a separate
user-table file were being imported with default properties rather than with the section properties
defined in the user-table file.
12593 When importing CIS/2 STEP files, an error message will be generated if an unsupported schema is
present in the file. Previously the import would fail without explanation.
12897 An Incident was resolved in which encountering an error during the import of CIS/2 STEP files
SAP2000 V14.2.0 2010-03-23 Page 20

would previously terminate the operation with no data being imported. Now all data that is
successfully read will be retained.
12978 An Incident was resolved for the import of STAAD, STRUDL, IGES, and NASTRAN models in
which unit conversions were not always correct for the coefficient of thermal expansion and for the
gravitational constant g used to convert mass to weight.
14351 The Help has been updated to clarify that the DXF Export always exports all objects present in the
active window.
16320 An Incident was resolved in which frame section properties were not being imported when they
were explicitly defined for an individual frame member on separate data lines rather than being
assigned for a group.
16774 An Incident was resolved in which the import of an IFC file would sometimes generate a runtime
error when specified entities were missing some required properties in the file. No results were
produced. Now any entity with such missing properties will be ignored during import without error.
18558 An Incident was resolved in which the local axis of vertical members was not imported correctly for
StruCAD*3D files. They were rotated 90 degrees from the orientation in the StruCAD*3D model.
This only affected vertical members.
18926 Several changes have been made to the export to SAFE V12 to address the following issues: (1)
Response-spectrum cases will no longer be available for export unless the prerequisite modal case
has already been run, since the modal results are needed by SAFE to compute the response-
spectrum results. (2) Braces were being exported, which should not be the case. This was also
creating duplicate column section property names. Both issues have been resolved. (3) Wall
supports were sometimes exported with the wrong height.
19497 An Incident was resolved in which sections defined in a StruCAD*3D input file were not being
found in SAP2000 section property (.PRO) files even though the names were the same.
20555 An incident was resolved in which values in Nastran files did not import correctly if the values were
in scientific notation and missing the "E" prior to the plus (+) or minus (-) sign of the scientific
number. In addition, moments of inertia and torsional constants were performing units conversions,
when needed, using length to the power three rather than to the power four.
13395 An Incident was resolved in which an error occurred when import certain IFC data files. The import
15698 did not complete and no results were produced.
17882 An Incident was resolved in which an exception (runtime error) was generated when importing a
18561 StruCAD*3D model while analysis results were available. This has been changed so that it is no
longer possible to import StruCAD*3D files when the SAP2000 model is locked.
Documentation
14566 An Incident was resolved in which Figure 6 of the CSI Analysis Reference Manual, showing
examples of restraints, listed the incorrect degrees of freedom for the 2-D frame.
16033 The Help for "Load Case Data - Response Spectrum" has been updated to remove the description of
"Diaphragm Eccentricities" since this item is not currently available in the program. The program
has not been changed.
17155 The Help has been updated to correct a minor error in step 48 of Example Problem Z. The
directional combination should use the Absolute option with a scale factor of 1.
18978 The table of contents was updated for the steel-frame design manual “SFD-OlderCodes.pdf”.
19156 The steel frame design manual for AISC-ASD89 has been corrected as follows: Fb for T-sections
was previously defined as "Fb = 0.6 * Fy". It has been changed to "Fb = Qs * 0.6 * Fy". This is a
documentation error only. The program was correctly using the latter definition for the calculations.
19334 The documentation for code "AASHTO LRFD 04" has been removed from the steel frame design
manual since this code is no longer supported in the program.
20096 The documentation and Help were updated to describe the advanced parameters that are available
when assigning a nonprismatic frame section to frame objects.
SAP2000 V14.2.0 2010-03-23 Page 21

Miscellaneous
18796 The version number has been changed to V14.2.0 for a new update.
15695 The Read-only flag has been removed from the data files in the Verification subfolder of the
SAP2000 installation (except the function files). This subfolder should be copied to a separate
location before running verification examples so as not to overwrite the original data files in the
installation. The Read-only flag was set in previous versions to prevent accidental overwriting of
the data files, but caused confusion when the verification examples could not be run even after
copying them to a separate location until the flag was turned off.
SAP2000 V14.2.0 2010-03-23 Page 22

Release Notes
ReadMe file.

* 17537 The Rotate 3D View command has been enhanced to rotate about the center coordinate of the
current view, accounting for zoom and pan. Previously the rotation was always about the center of
the structure for perspective views, and about the origin for orthographic views.
Modeling
14341 The IBC2006 Auto Seismic Load case has been updated as per Supplement # 2 to ASCE 7-05
where the minimum Cs value is revised.
16297 The API 4F implementation has been enhanced to include a Shielding Factor. The factor applies to
17406 the overall wind load on the structure, but does not apply to the load on the member itself. Only
members that are transversely supported in both directions at both ends will be shielded, otherwise
they will transfer the full (unshielded) wind load to the rest of the structure.
18441 The Norwegian national parameters have been implemented for the EC8-2004 auto seismic load
and response spectrum functions. In addition, air density has been added as a new parameter to the
EC1-2005 auto wind load for use with different countries.
* 18152 Automated wind lateral loading for Australia and New Zealand has been implemented according to
the AS/NZS 1170.2 2002 code.
18385 The Chinese auto lateral wind load has been updated to account for reduction in wind loads for the
special case of a uniformly tapered building.
18531 A new section-property database file, ChineseGB08.pro, has been added. This file contains hot-
rolled sections for code “GB/T 706-2008”, hot-rolled and cut-T sections for code “GB/T 11263-
2005”, welded steel H sections for code “YB 3301-2005”, and high-frequency welded light-gauge
H steel sections for code “JG/T 137-2007”. The previous file, Chinese.pro, is still available.
Section Designer
18262 The calculation of Caltrans frame hinges has been made more efficient in order to reduce the time it
takes to assign these types of hinges and to create the analysis model. The improvements made to
the underlying iteration procedure may slightly change the PMM surface and moment-rotation
curves, usually in the fourth significant figure.
SAP2000 V14.1.0 2009-07-29 Page 1

18338 The calculation of Caltrans frame hinges has been made more efficient by not repeating the
calculations for hinges assigned to identical cross sections. This affects the time it takes to assign
hinges and to create the analysis model.
Bridge Modeler
18166 The creation of frame objects to model bridge bent columns has been changed as follows: (1) The
frame objects are now equally divided over the clear height from the bottom of the column to the
bottom of the cap beam, and the top frame object is extended with an end offset to the bent cap
centerline. Previously they were divided equally over the total height, except for short columns.
This change should have no effect on the static behavior of the model, and very little or no effect on
the dynamical response. (2) Columns shorter than the half depth of the bent cap are now set equal in
height to the half depth of the bent cap. Previously they were discarded.
* 18523 The U-girder frame section can now be used to model steel tubs in the Bridge Modeler. When a
steel material is chosen for the frame section, the generated linked bridge model will treat the
alignment of the top and bottom flanges similarly to how they are treated for steel I-girders: The
haunch distance is measured to the bottom of the top steel flange, rather than to the top of the top
flange as is the case for concrete U-girders. One or two bearings will be created for each steel U-
girder depending on the definition of the frame section. A single bearing is used for concrete
sections. Significant further specializations for steel U-girders are under current development.
18524 Constraints have been added to the linked model that is generated for steel-girder diaphragms used
in conjunction with area (shell) models of steel I-girder bridge deck sections. The purpose of the
additional constraint is to assure that the diaphragm provides the expected stability to the lower
flange of the longitudinal I-girders.
Analysis
14718 Additional hysteresis models are now available for the single degree-of-freedom frame hinges with
uncoupled P, V2, V3, T, M2 and M3 behavior. The choices include: Isotropic, Kinematic, Takeda,
and Pivot types of behavior. The Isotropic model gives the hysteresis behavior that was provided in
the previous versions of SAP2000, and this is still the default. The three new types of hysteresis are
identical to those offered for the multilinear plastic link element. Hysteresis primarily affects time-
history results with load reversal, although small changes in monotonic pushover behavior may also
be seen between the original Isotropic model and the new hysteresis models. The Isotropic model is
optimized for pushover analysis, and is recommended if time-history analysis is not important. The
new models add a very small amount of elastic flexibility the frame element, which the Isotropic
hinge does not.
Frame Design
* 17972 “AASHTO LRFD 1997” concrete frame design, which had been removed with Version 12, has now
been reinstated after updating it to “AASHTO LRFD 2007”.
* 18008 Steel frame design has been added for “NORSOK N-004”, including punching checks. The design
of non-tubular sections is in accordance with Eurocode 3-2005 with the Norwegian National Annex.
The SAP2000 Offshore add-on license is required to use this feature.
18386 The Norwegian national parameters have been implemented for concrete frame design using the
“Eurocode 2-2004” code and steel frame design using the “Eurocode 3-2005” code.
SAP2000 V14.1.0 2009-07-29 Page 2

18504 For steel frame design using codes “API RP2A-LRDF 97” and “API RP2A-WSD2000”, the design
overwrite previously called “Internal Pressure” has been changed to “Additional External Pressure”,
and the sign of the value changed accordingly. A positive value for Additional External Pressure
will cause compressive hoop stress. Negative values are permitted, which indicate internal pressure.
Whether it is positive or negative, this overwrite value acts in addition to the external pressure
produced by any wave loading included in the design load combinations. When old data files are
opened or imported, this overwrite value will be set to zero and a warning given that the value must
be re-assigned. Any external programs using the OpenAPI functions to set or get this value must be
modified to account for the change in sign of this value.
Bridge Design
* 17922 Detailed design checking has been implemented for multi-cell prestressed concrete box-girder
bridge superstructures according to the “AASHTO LRFD 2007” code. Separate design checks are
available for stress, flexural capacity, and shear capacity using MCFT (modified compression field
theory). Live-load distribution factors can be automatically calculated using code formulae,
specified by the user, or determined from detailed 3-D live-load analysis. Results are reported for
each girder, and include plots of stress, moment demand and capacity, shear demand and capacity,
and shear-rebar requirements. Detailed tables showing all results and intermediate values are
available for display, printing, and export to Excel or Access. These new checks are in addition to
the whole-section checks that were previously released.
17952 Bridge seismic design has been enhanced to provide more information when the design fails due to
inadequate axial capacity of the columns. Previously the reason for the failure was not always
obvious.
Database Tables
* 18280 The “Floating Point Number Format” and “Units” settings have both been removed from the
database table format file. Now all displayed tables, printed tables, and tables in formatted reports
will use the corresponding settings that are controlled using the menu command Options > Set
Program Default Display Units. This makes it easier to format the tables and provides more
consistent formatting.

17944 The following API functions were added which supersede older functions in order to implement
new features in this version. See file “SAP2000_API_Documentation.chm” in the SAP2000
installation folder for more information:
• SapObject.SapModel.LoadPatterns.AutoWind.GetAPI4F2008_1
• SapObject.SapModel.LoadPatterns.AutoWind.GetChinese2002_1
• SapObject.SapModel.LoadPatterns.AutoWind.GetEurocode12005_1
• SapObject.SapModel.LoadPatterns.AutoSeismic.GetEurocode82004_1
• SapObject.SapModel.Func.FuncRS.GetEurocode82004_1
• SapObject.SapModel.LoadPatterns.AutoWind.SetAPI4F2008_1
• SapObject.SapModel.LoadPatterns.AutoWind.SetChinese2002_1
• SapObject.SapModel.LoadPatterns.AutoWind.SetEurocode12005_1
• SapObject.SapModel.LoadPatterns.AutoSeismic.SetEurocode82004_1
• SapObject.SapModel.Func.FuncRS.SetEurocode82004_1
SAP2000 V14.1.0 2009-07-29 Page 3

* 18155 The capability to export a model to SAFE V12 has been implemented. A single global-Z elevation
is chosen, and all objects connected to joints within a tolerance of that elevation are exported.
Linear static and response-spectrum load cases and associated data are also exported.

Incidents Resolved
17172 An incident was resolved in which the option “Glue to Grid Lines” worked when accessed using the
Define > Coordinate Systems/Grid menu command, but did not work accessed by right-clicking
with the mouse on a grid line.
* 18157 An Incident was resolved in which the license was sometimes lost during creation of the analysis
model for certain types of models. This only affected network licenses.
Modeling
Incidents Resolved
17272 An Incident was resolved in which analysis would fail if bridge lane loads were applied to a frame,
shell, or other object when its property was set to "None." This has been changed so that bridge lane
loads applied to an object with its property set to "None" will be ignored.
17657 An Incident was resolved in which an exception (runtime error) could be generated in rare cases
when calculating the apparent period for certain models having wave loading.
17927 An Incident was resolved for the New Zealand response-spectrum function and auto-generated
static lateral loads in which the near-fault factor, N(T,D), was being applied uniformly across all
periods rather than non-uniformly as a function of period. The specification has been changed from
the near-fault factor to the near-fault distance.
* 18376 An Incident was resolved in which some of the “Uniform to Frame” loading was lost when assigned
to an area object that could not be meshed by cookie-cutting into 3- and 4-noded areas the using
existing frame objects. Now a warning message is given to the user if this problem is detected
while assigning the load or while creating the analysis model. If the warning is issued when creating
the analysis model, the user is given the option of either converting the load to a uniform area load,
in which case no load is lost, or canceling the creation of the analysis-model.
Section Designer
Incidents Resolved
17325 An Incident was resolved for Section Designer in which the Caltrans idealized moment-curvature
18057 curve could not be plotted for sections that contained only tendons and no rebar. This has been
resolved so that rebar and tendons, when present, are checked for failure against their respective
ultimate strains.
18090 An Incident was resolved for Section Designer in which the calculation for the plastic neutral axis
could give incorrect results for section shapes having sudden changes in the section dimensions near
the plastic axis.
18337 An Incident was resolved for Section Designer in which the confined Mander model computed
using the casing in a Caltrans section was not correctly considering the ultimate strain, Esu, of the
casing material.
SAP2000 V14.1.0 2009-07-29 Page 4

Bridge Modeler
Incidents Resolved
16543 An Incident was resolved in which bridge girders were not always being included when assigned to
18127 a staged-construction group for a bridge object. The problem only occurred in Steel girder, precast-
I and precast-U bridges modeled as area objects with the girders modeled as line objects. The
girders were not included in the group if the specified station range to include in the group did not
include station zero.
17912 An Incident was resolved in which the torsional constant J calculated for bridge deck sections,
precast-U sections, and precast-I sections could differ from the correct value by 5% or more,
especially for the precast-U girder. This has been resolved by internally using a more refined mesh
to calculate the torsional constant.
17954 An Incident was resolved in the Bridge Deck Section form in which entering a formula in certain
cells, and then clicking in a another cell, would enter the calculated value in the second or both cells
rather than in just the first cell.
right-clicking on a solid element joint with springs created from the Bridge Modeler.
18021 An Incident was resolved in which it was possible to delete frame sections that were being used to
define bridge deck sections, resulting in an error when accessing the definition of the bridge section.
18102 An Incident was resolved in which, under rare circumstances, an out of memory error message was
18115 generated when creating the analysis model for a bridge model with tendons. Memory use has been
optimized.
18233 An Incident was resolved in which the connection of abutment bearings to solid models of a bridge
superstructure sometimes formed an unstable mechanism for certain geometric configurations. Now
additional connections are made to assure stability.
adding bents to a bridge object to which deck width parametric variations had been assigned.
18415 An Incident was resolved for the Bridge Modeler in which the area (shell) objects representing the
bottom flange of built-up I girders were not being generated. This did not affect spine models of the
superstructure, or area models in which the girders were represented as frames.
18468 An Incident was resolved in which the linked SAP2000 model could not be created from a bridge
object in certain rare cases where curve or skew in the bridge created two or more discretization
points that were too close together, failing a tolerance check. Now the more significant
discretization point is used.
18470 An Incident was resolved for the bridge modeler in which nonprismatic steel girders did not
properly change cross sectional shape at double-bearing (discontinuous) bents.
Analysis
Incidents Resolved
* 15873 An Incident was resolved for bridge moving-load cases in which the vehicle axle loads were not
15953 being restricted to remain within the lane-edge distances specified for the vehicle, but instead were
17970 allowed to move to the edge of the lane. The effect of this was conservative.
18058
15878 An Incident was resolved for bridge moving-load cases in which vehicles were not always restricted
to remain fully within the length of the lane when this option was specified for the vehicle. The
effect of this was conservative.
17967 An Incident was resolved in which the advanced solver would, in rare cases, generate an error when
solving a model with internal instabilities and could not complete the analysis.
17978 An Incident was resolved in which the moving-load load cases did not properly account for file size
18217 when saving response. For certain large models this could result in the analysis failing to complete
with a disk-error message. Otherwise, the results were correctly saved.
SAP2000 V14.1.0 2009-07-29 Page 5

* 18277 An Incident was resolved in which the P-delta force in frame elements was assumed to be constant
over the element using the value at the I-end of the element rather than at the center of the element.
The P-delta force is used for nonlinear static analysis, nonlinear direct-integration analysis, and
buckling analysis. This means that different P-delta effects or buckling loads could be calculated
when the local 1 axis is reversed (i.e., by switching the ends I and J) for the case where there is
significant axial load applied to the element itself compared with the total axial force being carried
by the element.
18536 An incident was resolved in which, in rare cases, generated an exception (runtime error) when
rerunning the analysis in the same session after performing analysis and design.
18540 An Incident was resolved in which direct-integration time-history analysis would fail for models
with multiple types of elements having mass-based material damping.

Incidents Resolved
17066 An Incident was resolved in which the force and moment results for bridge superstructures
17614 sometimes exhibited unexpected jumps at diaphragm locations. This was because the diaphragm
objects were being included in some of the internal sections cuts used to calculate the results.
Diaphragms are now excluded from the section cuts.
17907 An Incident was resolved in which an exception (runtime error) could occur when using the Display
> Show Hinge Results command and selecting a load case that has fewer steps available than the
current step value chosen for the previously displayed case.
18363 An Incident was resolved in which the plotted frame results were incorrectly displayed when the
object was meshed into elements and the output stations were not set to calculate results at
intersections with other elements.
Frame Design
Incidents Resolved
* 16491 An Incident was resolved for steel frame design in which the panel-zone design shear force used to
joint, and Vc is the shear force from the column above the joint. Vb is calculated as the larger of the
capacity moment or the factored moment from the beams, divided by their mean flange distance.
Normally the capacity moment governs, and this was being calculated correctly. However, when the
factored moment governed, the design could be unconservative, since the moments from the two
beams were added algebraically, but should have been added using their absolute values. The
affected codes are “AISC-ASD 01”, “AISC-LRFD99”, “UBC97-ASD”, “UBC97-LRFD”,
“CAN/CSA-S16-01”.
16747 An Incident was resolved for steel frame design using the direct analysis method of code AISC 360-
18405 05/IBC2006” in which the reported value for modified EA was given as 0.8*tau_b*EA instead of
0.8*EA, and the reported value of modified EI was given as 0.8*EI instead of 0.8*tau_b*EI. The is
a reporting error only. The correct values were being used for all calculations.
* 18147 An Incident was resolved for steel frame design using codes “Eurocode 3-1993” and “Eurocode 3-
2005” in which the section classification was sometimes incorrect for sections in pure compression.
18248 An Incident was resolved in which the legend for P-M steel design ratios showed zero values after
the design information was displayed more than once.
* 18347 An Incident was resolved in which superimposed dead load patterns were not being included in
auto-generated strength design load combinations for all types of design and all design codes.
SAP2000 V14.1.0 2009-07-29 Page 6

* 18402 An Incident was resolved for concrete frame design using code “ACI 318-05/IBC 2003” in which
column shear forces were not being properly amplified when Sway Ordinary frame design
procedure was chosen and the Seismic Design Category was greater than or equal to B. Now the
shear design of columns will be performed in this case according to the Sway Intermediate Frame
procedure. In addition, for such cases (Ductility=OMF, SDC >= B), the shear design of beams was
previously being performed as beams in Sway Intermediate Frame. Now such beams are designed
as Sway Ordinary beams irrespective of SDC.
* 18403 Steel frame joint design has been improved to now consider whether the joint being designed is at
the top of the column or not. Previously the joint was always assumed to have a column above it,
which could lead to an unconservative design for the topmost joint where there is less restraint. The
affected codes are “AISC360-05/IBC2006”, “AISC-ASD 01”, “AISC-LRFD99”, “UBC97-ASD”,
“UBC97-LRFD”, “CAN/CSA-S16-01”.
* 18404 An Incident was resolved for steel frame design in which the panel-zone design shear force used to
joint, and Vc is the shear force from the column above the joint. Previously Vc was taken as the
shear force from the column below rather than above the joint. This error could be slightly
unconservative, since Vc is usually much smaller than Vb. The affected codes are “AISC360-
05/IBC2006”, “AISC-ASD 01”, “AISC-LRFD99”, “UBC97-ASD”, “UBC97-LRFD”,
“CAN/CSAS16-01”.
18407 An Incident was resolved for steel frame design using the Chinese code where the reported shear
stress could be the fictitious shear stress even when the calculated shear force was governing. The
reported governing shear-stress ratios and the associated pass/fail status were being correctly
reported. Only the shear stress value itself could be incorrect if the option to check the fictitious
shear stress was chosen in the preferences.
* 18408 An Incident was resolved in which the D/C ratio calculated for design could be incorrect for
unsymmetrical Section Designer sections due to an error in interpolating the capacity from P-M-M
surface. Sections which are symmetrical for major (M3) bending were not affected.
* 18457 An Incident was resolved in which the punching shear overwrites were being ignored for steel
frame design using the API design codes.
18491 An Incident was resolved for concrete frame design using code “Eurocode 2-2004” which prevented
the design of a beam to complete if it had a tensile axial force.
* 18498 An Incident was resolved for steel frame design using code “Eurocode 3-2005” in which the
buckling moment capacity was not being considered in the PMM interaction equation.
18541 For steel and concrete frame design using the "Chinese 2002" code, the design overwrite "Dual
System Seismic Magnification Factor" has been modified so that it multiplies only the seismic loads
in each design load combination. Previously this factor was magnifying all loads in the
combinations.
Bridge Design
Incidents Resolved
* 17910 An Incident was resolved for bridge design of precast-girder superstructures in which the live-load
distribution factors calculated from code equations sometimes gave a zero value for the interior
girder of a three-girder section.
17911 An Incident was resolved in which the shear rebar area calculated for the bridge superstructure
shear check of precast girder superstructures was sensitive to the sign of the moment when the
moment was near zero. The magnitude of the minimum moment used could change significantly
with the sign. This has been changed so that now the shear rebar is computed by taking into account
the minimum moment for both positive and negative signs. The practical effect of this change
applies only near inflection points, and is not common.
SAP2000 V14.1.0 2009-07-29 Page 7

17926 An Incident was resolved in which a bridge seismic design request for seismic category D would
sometimes fail to run when columns were discretized into short frame objects, such that the hinges
were not located in the top-most or bottom-most frame objects.
* 17945 An Incident was resolved for the bridge superstructure shear check of precast girder superstructures
in which the correct controlling results for shear rebar were not always presented in the output
tables. Results were presented for the correct demand set and load combination, but not always for
the correct correspondence set, e.g., maximum or minimum moment with maximum or minimum
shear. The plotted results were shown for the correct controlling case.
17948 An Incident was resolved which included several minor problems in the handling of bridge design
results: (1) If bridge design results were deleted, the Bridge Object Response Display form would
still allow the design option to be selected, although no results would be available to plot. (2) Bridge
design results were still available for plotting after the model was unlocked, even though they may
no longer have been valid. (3) If seismic and superstructure design requests both existed, and only
seismic design had been run, the Bridge Object Response Display form would still allow the design
option to be selected, although no superstructure results would be available to plot. (4) If seismic
and superstructure design requests both exist, and the superstructure design had been run first, the
seismic design might not have been able to be run. (5) After a superstructure design had been run, it
was possible to delete a load case or its analysis results, even though it was included in load
combination used for the design. This did not invalidate the design, but it could lead to confusion
between analysis and design results.
17951 An Incident was resolved in which a bridge seismic design request for seismic category D would
sometimes fail to run when non-prismatic section properties were assigned to one or more bent
columns in the bridge object of that design request.
17962 An Incident was resolved in which the demand and capacity reported in the bridge seismic design
results table did not properly convert for units.
18387 An Incident was resolved for bridge design of precast-girder superstructures in which the values
CGFibTop and CGFibBot reported in the output table for the flexural check were switched. These
are the distances to the top and bottom fibers of the composite girder, measured from the centroid of
that girder. This was a reporting problem only. Design calculations were not affected.
Database Tables
Incidents Resolved
17921 An Incident was resolved in which the option that controls whether or not to calculate section-cut
forces for moving-load analysis was not being included in the database tables. This option is now
included in the tables, and the default value has been changed from “Yes” to “No” (not to calculate
section cut forces). The section-cut calculation for moving loads is not needed for section cuts that
contain only frame and/or shell objects, the most common case.
18231 The import of database tables has been changed so that when a new model is imported the present
units are set equal to the database units, that is, they are set equal to the units listed in the Program
Control table. This enables models run in batch mode to export their results to database tables in the
same units as the model. Previously they were being exported in the units chosen when the batch
run was started.
18530 An Incident was resolved in which the database tables for some types of element response were
giving the element index rather than the element label.

Incidents Resolved
18514 The GetOverwrite and GetPreference API functions for the Chinese steel frame design have been
updated. Enhancements to the framing type and element type parameters that were previously
released in Version 14.0.0 had not been implemented in these API functions or the documentation.
SAP2000 V14.1.0 2009-07-29 Page 8

Incidents Resolved
17909 An Incident was resolved in which an exception (runtime error) was generated when exporting
some bridge models to DXF.
Miscellaneous
17944 Version number changed to 14.1.0.
SAP2000 V14.1.0 2009-07-29 Page 9

Release Notes
ReadMe file.

* 17059 Multiple enhancements have been made to the graphical display: (1) Line thickness, as controlled
by the Screen Line Thickness preference, has been enhanced for different object types. (2)
Transparency and anti-aliasing have been added to lines drawn in the Classical Plus graphics mode.
(3) Display of frame forces and moment diagram has been clarified by outlining the filled areas. (4)
Cyclic animation of deflected shapes has been made smoother. (5) The speed of displaying extruded
shapes has been increased by an order of magnitude.
17554 The metric unit designation “ton” has been changed to “tonf” to clarify that this refers to a metric
ton-force rather than ton-mass. The meaning has not changed, and results are not affected. The
import of old files using the “ton” designation will still work.
Modeling
* 16500 Directional nonlinear material behavior has been added to the layered shell element for modeling
shear-walls and similar applications. Each layer may have its own material and material angle.
Uniaxial (uncoupled) nonlinear behavior can be specified in each layer for any or all of the in-plane
stress components S11, S22, and S12. The nonlinear shear stress-strain curve for a material is
automatically computed from the axial stress-strain curve. Each layer may be specified to have
plate, membrane, or full shell (membrane plus plate) behavior. Simple or complex shell models may
be created using these features. A Quick-Start option is provided for modeling reinforced concrete
sections.
* 17107 Automated lateral loading for Eurocode has been implemented: Wind according to Eurocode 1 (EN
1991-1-4:2005), Seismic according to Eurocode 8 (EN 1998-1:2004), and Response Spectrum
according to Eurocode 8 (EN 1998-1:2004).
* 17108 Automated lateral loading for the Australian code has been implemented: Seismic according to AS
1170.4:2007, and Response Spectrum according to AS 1170.4:2007.
* 17109 Automated lateral loading for the New Zealand code has been implemented: Seismic according to
NZS 1170.5:2004, and Response Spectrum according to NZS 1170.5:2004.
17127 An enhancement has been implemented that affects hinges assigned to frame objects having a
Section Designer section with design type set to “Concrete Column – To Be Designed”. Previously,
hinge properties (yield moments or interaction surfaces) were calculated for the actual amount of
rebar specified for the section. This has been changed so that the hinge properties will now be
calculated for the designed area of rebar if concrete frame design has been performed for that
section. If no design has been performed, or if design results have been explicitly deleted by the
user, the hinge properties will be calculated for the actual amount of rebar specified for the section.
SAP2000 V14.0.0 2009-05-05 Page 1

* 17210 The AASHTO/USGS LRFD 2007 built-in response-spectrum function has been added, using data
corresponding to 5% probability of exceedance in 50 years (7% probability of exceedance in 75
years), or approximately 1000-year return period.
* 17505 Material-based damping has been implemented for direct-integration time-history and frequency-
domain (steady-state and PSD) analysis. For each material, you may specify mass- and stiffness-
proportional viscous damping coefficients to be used for direct-integration time history analysis,
and separate mass- and stiffness-proportional hysteretic damping coefficients to be used for
frequency-domain analysis. This damping acts in addition to that specified for the load case.
17629 The loads applied to tendons that are modeled as elements have been changed to now allow elastic,
creep, shrinkage, and steel-relaxation losses to be specified. Previously these losses were only
available for tendons modeled as loads. If present, they act in addition to the losses computed by
analysis. For this reason, the elastic loss should usually be set to zero for tendons modeled as
elements.
17792 The default parameterized stress-strain curves for unconfined Mander-model concrete have been
modified to better capture the shape of the curve, and to reduce the negative slope after ultimate,
usually to be no steeper than about 10% of the initial elastic slope. This improves convergence
behavior during nonlinear analysis. The net area under the compression curve has not been
significantly changed from Version 12.0.2, so that the generated confined Mander-model curves
will be little changed.
17795 The Chinese section-property database file Chinese.PRO has been updated.
Section Designer
17413 An option has been added in Section Designer to convert double-angle sections to polygons.
14725 An enhancement has been made to the PMM surface displayed inside Section Designer when the
fiber-model option is chosen. Previously the fiber-model PMM surface included the steel over-
strength factor and the compression cap. Now the PMM surface for the fiber model is displayed
without any modifications for the design codes. This option allows you to see the “true” interaction
surface. However, the PMM surface displayed when the design-code option is chosen still includes
the effect of the steel over-strength factor, the compression cap, and the phi factor (optionally) are
still included. This option allows you to see the PMM surface that will be used for checking design.
Bridge Modeler
* 13391 The Bridge Modeler now allows parametric variations to be specified for the girder spacing in those
14017 deck sections that allow for non-uniform girder spacing: Advanced Box Girder, Precast I Girder,
Precast U girder, and Steel Girder. The girder spacing will be proportionately adjusted to fit within
the specified total width minus the specified overhang distances, whether or not any parametric
variations are specified for width, overhang, and/or girder spacing.
16974 The automatic discretization along the longitudinal direction of the generated linked model for
bridge superstructures has been improved to reduce the creation of very short line/area/solid objects
near in-span hinges, diaphragms, user-discretization points, and section variations.
17071 The default wobble coefficient for tendons created in the Bridge Modeler has been changed to 2.0E-
4/foot to be in accordance with the value given in the ASHTO LRFD 2007 Table 5.9.5.2.2b-1.
17072 Tendons in bridge objects now load only objects that are part of the superstructure cross section.
Previously they could connect to objects that were part of an integral bent-cap.
17429 An enhancement was made to the Bridge Modeler for bridge deck sections modeled as areas
(shells). The element local-1 axis is now directed along the two element joints that are most nearly
parallel to the layout line, running in the up-station direction. This results in the longitudinal stress
being S11 for all elements. This was previously done for steel girders under Incident 17011. It is
SAP2000 V14.0.0 2009-05-05 Page 2

now extended to the concrete decks, webs, soffits, and the webs and flanges of U-girders modeled
as areas, as may be applicable to different cross sections.
17456 An enhancement was implemented for the Bridge Modeler that allows parametric variations to be
specified for the deck section reference point in the X and Y local directions. This gives more
control over the eccentricity of the superstructure with respect to the layout line at widenings and
for other situations.
Analysis
* 17151 Two enhancements have been made to the stiffness used during nonlinear iteration for multilinear
link elements, frame-element fiber hinges, and the nonlinear layered shell: (1) The initial stiffness
used at zero force or stress will be the larger of the values in the positive and negative direction of
loading. Previously the average of these two values was being used. (2) Negative tangent stiffness is
now allowed during iteration. Previously the tangent stiffness was not allowed to be less than a
small positive value. Both of these changes tend to improve the rate of convergence during
nonlinear analysis. However, they may also significantly affect linear load cases that use the
stiffness at the end of a nonlinear load case. This may change results for multilinear link elements
and for fiber hinges in frame elements compared to Version 12.0.2 and earlier.
* 17152 Stiffness-proportional damping used for direct integration (DITH) has been changed from previous
versions, which used the tangent stiffness matrix (KT damping). Now the initial stiffness matrix (K0
damping) is used for all elements, as described in the CSI Analysis Reference Manual. These
changes will normally make nonlinear iteration faster and more stable, but will tend to increase the
overall energy dissipation. Because of this, analysis results may now be different from previous
versions of the program. The effect of stiffness-proportional damping on modal time-history
analysis is not changed, nor has the effect of stiffness-proportional hysteretic damping on steady-
state and PSD analyses.
17484 Section-cut forces, element joint forces, and base reactions for direct-integration time-history
previously included stiffness-proportional damping effects for the Solid, Plane, and Asolid
elements. This has been removed to be consistent with the Frame, Shell, and Link elements. Now
section-cut forces, element joint forces, and base reactions contain only stiffness forces due to
displacement. Damping effects are not included.
17503 A new membrane formulation has been introduced for the layered shell element that does not use
the drilling DOF (rotation about the element normal). Membrane behavior is coupled only to the in-
plane translational displacements. See the CSI Analysis Reference Manual for important modeling
considerations. The homogeneous membrane and the thin/thick shell still use the previous (coupled)
formulation with drilling DOF.
* 17592 The response-spectrum load case has been enhanced to allow the option to consider fully-correlated
rigid response for all modal combination methods except the absolute sum. This is an extension of
the capability that was already present for the GMC method. The frequencies controlling the rigid
response can be specified, as well as the method for combining the rigid and the periodic response.
17635 The “Modified SRSS (Chinese)” option for directional combination in the response-spectrum load
case has been removed, since this produced the net extreme response rather than separating the two
directional responses. The same result can be achieved instead by defining two response-spectrum
load cases with different directional scale factors, and enveloping them in a load combination.
Models created in previous versions using the “Modified SRSS (Chinese)” direction combination
will be converted to use the regular “SRSS” directional combination, which is conservative.
* 17681 Multi-step static load cases created from Bridge Live Load patterns can now be run in the Plus and
Advanced levels without the Bridge license. This allows analysis of crane, footfall, and other path-
like loading on structures other than bridges. Consideration of full width effects still requires the
Bridge license.
* 17682 Staged-construction load cases starting from zero initial conditions and containing a single stage can
now be run in the Plus and Advanced levels without the Staged-Construction license. This allows
SAP2000 V14.0.0 2009-05-05 Page 3

consideration of multiple configurations of the same structure, such as gravity and lateral framing,
alternative support conditions, separate portions of a structure, and other applications.
* 17732 Base-reaction calculation for response-spectrum and modal time history analysis has been changed
to more accurately account for inertial forces due to mass at joints supported by springs or grounded
links. They were previously calculated using the accelerated mass, but more accurate results are
now obtained directly from the springs and grounded (one-joint) links. For this to work well when
very stiff springs or supports are used, eigen vectors should include static correction vectors, or else
Ritz vectors should be used. The effect of this change will be small for the usual case of small
masses at the springs or supports, and for adequate mass participation ratios. Note that inertial
effects at restrained DOF are not included in the base reaction for the previous or current version.
Base reaction refers to the total resultant support force for the structure, not to the individual joint
reactions, which have not changed.
* 17821 The handling of constrained joints in staged construction has been changed. Previously all
constrained joints deflected with the master joint as soon as any joint in a given constraint was
present in the structure. Now the deflections of a constrained joint will not be updated until that
joint has been added to the structure. The user can control when the joints begin to deflect by adding
constrained joints at any stage, even before any connected elements are added.
* 17852 Base reaction calculation has been changed to exclude the force coming from constraints. This is
consistent with how sections cuts are calculated. If reactions are needed at joints connected to
constraints, the support condition should be modeled using springs or grounded (one-joint) links
rather than restraints.

17686 Plot functions can now be defined for stresses in layered shell elements. The layer and thickness
location can be specified as part of the function definition. Previously only resultants could be
plotted for layered shells.
Frame Design
* 13389 Concrete frame design has been added for Eurocode 2-2004, incorporating the National Annexes for
Slovenia and the United Kingdom. Seismic provisions of Eurocode 8 are not included at this time.
* 14473 Concrete frame design has been added for Australian code AS 3600-2001, including seismic
provisions.
* 16739 Steel frame design has been added for Eurocode 3-2005, incorporating the National Annexes for
Bulgaria, Slovenia, and the United Kingdom. Seismic provisions of Eurocode 8 are not included at
this time.
* 17055 Multiple enhancements have been made to concrete frame design using Indian code IS 456-2000.
These includes the following items:
(1) The torsional design of concrete beams has been added, with output in a form similar to the
ACI code for the detail sheet, text file, and database tables.
(2) The column shear demand is now calculated based on the beam moment capacity only, not the
column moment capacity. Previously the demand was based on the minimum of the moment
capacity of the beams and columns at the joint.
(3) A detailed page has been added for beam-column joint-capacity check information. This is
accessed by clicking the "Joint Shear" button on the "Concrete Column Design Information"
window obtained by doing a right-button click on a column member after design.
(4) Error messages that were previously given for failed beam-column capacity ratios or joint-
capacity checks have been removed, since these two items are for informational purposes only
according to the current code.
SAP2000 V14.0.0 2009-05-05 Page 4

(5) K factors for the columns are now calculated based on the Wood's chart as recommended by
the code. Previously the K factors were being taken as one.
(6) For the design of T-beams, the depth of neutral axis, xu, is now being compared with the depth
of the flange. Previously the depth of an equivalent rectangular compression block depth,
0.84*xu, was being compared with Df. The new implementation matches the Appendix G
closely.
(7) The effect of axial force upon the allowable average shear stress, Tau_cd, is now being taken
into consideration. Previously, the effect of axial force was being ignored. The effect of this
enhancement is usually small as beams do not carry significant axial force. The column shear
design was already considering the effect of axial force.
(8) Beam and column shear design has been enhanced by providing at least the minimum shear
rebar even when Tau_v < 0.5*Tau_cd. Previously the minimum shear rebar was being provided
only when Tau_v was in the range 0.5*Tau_cd < Tau_v < Tau_cd + 0.4*MPa.
(9) The moment amplification factors have been removed from the design overwrites. These
factors were not being used, since the program assumes that P-Delta analysis is performed
explicitly.
17666 Load combinations containing both “Quake” (seismic) load and “Wind” load cases are now
17771 internally tagged as of type “Quake”. This allows steel and concrete frame design to consider
special seismic requirements. Earlier these combinations were being tagged as of type “Other” thus
ignoring special seismic requirements. The user has the option to change the design type of the load
combination.
* 17720 Multiple enhancements have been made to steel frame design using the Chinese code. These
17725 includes the following items:
17726 (1) The program now calculates the Mue factor (K factor) for Sway and Nonsway cases based on
17757 the equations provided in Appendix D of GB 50017 code. The factors are used as appropriate
17758 for Sway and Nonsway Moment Resisting Frame
17759 (2) In addition to previous types “Column”, “Beam”, and “Brace”, a member can now be
17762 designated as “Truss” for design purposes. When a member is designated as a Truss all
moments are ignored for design, which may be unconservative. Special lo/r limits are applied
for Truss members.
(3) Single and Double Angle sections are now treated as Class B. Previously they were treated as
Class C.
(4) Two new limits have been added to the overwrites: lo/r for compression and l/r for tension.
Using these limits, the user can supersede all other such limits as recommended by the code. By
default, program-recommended values will be used for both regular design and seismic design.
If these new overwrites are assigned to a given member, then the overwrites control the design
of that member. Setting the overwrites back to zero resumes default behavior using program-
recommended values for that member.
(5) A new factor, the “Dual System Seismic Magnification Factor,” has been introduced in the
design overwrites. This allows the user to increase the forces to ensure that the steel frame takes
at least 25% of base shear. This value is not calculated by the program, and its default value is
1. If the user overwrites this value, the program amplifies the forces by this factor when
designing the member for load combinations that contain seismic loads. The program does not
check framing type or element type for applicability, but simply uses the factor as specified by
the user.
(6) A new framing type, “Braced Moment Resisting Frame,” has been introduced in the
preferences and overwrites. This is in addition to the previous types “Moment Resisting
Frame,” “Concentrically Braced Frame,” and “Eccentrically Braced Frame.” Also, the previous
type “Moment Resisting Frame” has been renamed as “Sway Moment Resisting Frame” for
clarity. The framing type allows the program to choose the appropriate Mue factor to be
calculated by default.
(7) A new option namely “Is Tall Building?” has been added to the preferences. This setting is
used by the program to set the default values for gamma, phi_b, b/t slenderness limit, etc., and
to impose the limits like lo/r and b/t slenderness in a more accurate way. Previously the default
SAP2000 V14.0.0 2009-05-05 Page 5

values were always calculated assuming a tall building.
* 17768 Multiple enhancements have been made to concrete frame design using the Chinese code. These
17769 includes the following items:
17770 (1) The column effective-length calculations have been enhanced to reflect the GB50010 section
7.3.11-1 and GB50010 section 7.3.11-2 more closely. The K factors used for lateral load
governing cases are calculated based on the equations given in section 7.3.11-2. The K factors
used for gravity load governing cases are taken from the default value. During design time the
appropriate K factors are used for each load combo being considered. Both types of K factors
(for lateral and gravity load governing cases) for both major and minor direction buckling are
now over-writable.
(2) The governing N/(fc*A) is now reported for all columns, whether or not the combinations
involve seismic load. Previously the program reported this information only for seismic design.
Now it is always reported, but only for seismic design is it compared with its limiting value.
(3) Three new options have been added to the preferences: “Structural System,” “Is Tall
Building?,” and “Seismic Field.” These settings are used by the program to set the default
values for minimum steel rebar percentage and the limit on N/(fc*A) in a more accurate way.
Previously the default values for these values were fixed and the user had no control over them.
17799 Plotted output for concrete beam design has been enhanced to produce the envelope of the results
over the left quarter, middle half, and right quarter of the beam length. Previously results were
reported only at the left station, the right station, and the station closest to the middle of the beam.
Tabulated results are for all stations.
Bridge Design
* 15628 Detailed design checking has been implemented for precast-concrete girder composite bridge
superstructures according to the “AASHTO LRFD 2007” code. Separate design checks are
available for stress, flexural capacity, and shear capacity using MCFT (modified compression field
theory). Live-load distribution factors can be automatically calculated using code formulae,
specified by the user, or determined from detailed 3-D live-load analysis. Results are reported for
each precast girder, tributary slab, and/or composite girder/slab assembly, as appropriate. Results
include plots of stress, moment demand and capacity, shear demand and capacity, and shear-rebar
requirements. Detailed tables showing all results and intermediate values are available for display,
printing, and export to Excel or Access.
* 15915 A new bridge design check has been added following the AASHTO Guide Specifications for LRFD
Seismic Bridge Design 2009. This has been implemented as a bridge design request for a bridge
object that performs the following operations: (1) Determines the seismic design category from a
specified response spectrum function. (2) Automatically creates and runs a gravity load case. (3)
Automatically determines cracked section properties for the columns from the gravity load case and
applies them as property modifiers. (4) Automatically creates and runs modal and response-
spectrum load cases for categories B/C/D. (5) Automatically creates and runs multiple pushover
load cases for the bents, including a prerequisite staged-construction case, for category D. (6)
According to code and category, determine demands and capacities. (7) Produces a seismic design
report including D/C ratios and other data.
* 17746 The flexural design check for prestressed concrete box girder bridge superstructures has been
enhanced to fully account for secondary effects from prestress tendon forces. Previously all
prestress load was being removed from the demand design combos, including primary and
secondary forces, unless hyperstatic load cases representing the secondary forces were added to the
combos. Now only the primary prestress forces are being removed, so that the demand will
automatically include the secondary forces. There is no longer a need to include hyperstatic load
cases in the design combos. The flexural design check now requires tendons to be modeled as
elements.
SAP2000 V14.0.0 2009-05-05 Page 6

17307 New OpenAPI functions have been added to set and get the advanced local axis assignments to
object types: Point, Frame, Area, Solid, and Link.
17765 The Open API functions to access the design preference and overwrite data have been updated for
all Chinese and Indian design codes.
* 15968 Import capability has been added for StruCAD*3D models, including geometry, material and
section properties, and loads. The imported file can be used to create a new model or to add to an
existing model.

Incidents Resolved
17271 An Incident was resolved in which, during model creation, deleted vehicles were still available for
use when defining load patterns of type Bridge Live.
17289 An Incident was resolved in which the “Cable Property/Stiffness Modification Factors” form for the
cable property (not the object assignment) incorrectly displayed the “Frame Property/Stiffness
Modification Factors” form. In addition, modifiers assigned to the cable object were not effective.
Both issues have been resolved.
17422 An Incident was resolved in which strain load assigned to a cable could not be deleted.
17443 An Incident was resolved in which an exception (runtime error) was generated when defining a grid
system and omitting grid lines in one or more coordinate directions.
17473 An incident was resolved where unused material properties could not be deleted if a frame section
existed with a concrete material property assignment.
17543 An Incident was resolved in which coordinates in the Section Cut Data form were not properly
converted for units.
17580 An Incident was resolved in which an error was sometimes generated when using the command Edit
> Edit Lines > Trim/Extend Frames with multiple objects.
17595 An Incident was resolved in which an exception (runtime error) would be generated when
attempting to draw line objects after having used the Interactive Database Editor.
17655 An Incident was resolved in which strain loads on area objects (shells) were not available for the
Edit Replicate command and for the Assign Copy and Assign Paste commands.
17673 An Incident was resolved in which the first group listed on the Group Definition form could not be
deleted using the Delete button on the form.
17761 An Incident was resolved in which an exception (runtime error) could be generated if printing to a
PDF or XPS file was canceled.
17853 An Incident was resolved in which it was possible to delete a material property that was being used
by a Section Designer section, which changed the section properties and behavior. Only the base
material was being protected. Now all materials are being protected.
SAP2000 V14.0.0 2009-05-05 Page 7

Modeling
Incidents Resolved
17063 An Incident was resolved in which tendons modeled as loads did not always produce self-
equilibrating loading if the tendons did not fall fully within the bounding boxes of the loaded group
of objects. Now tendon loads that fall outside of the bounding boxes are applied to the nearest point
element that is connected to one of the objects in the loaded group.
17139 An Incident was resolved in which incorrect top or bottom Z elevations could be calculated, or an
exception (runtime error) generated, when defining auto seismic loads for “UBC 94” or Indian “IS
1893 2002” codes.
17300 An Incident was resolved in which, in rare cases, part of a tendon load may be missed from a
bounding element due to a tolerance problem.
17405 An Incident was resolved in which, for rare cases, the mass-source gravitational constant used to
17418 convert loads to mass could saved in the wrong units, resulting in incorrectly calculated mass. This
constant will now be corrected, if necessary, when opening older models.
17421 An Incident was resolved in which the section modulus S22 was incorrect for the Double Channel
sections in the property database file EURO.PRO. This file has been updated with the correct
values. Models from older versions of SAP2000 that reference EURO.PRO will be corrected when
opened in Version 14.0.0 and later.
17466 An Incident was resolved in which the curvature loss calculation for nearly straight tendons, in rare
cases, could cause a numerical problem that resulted in failure to produce design results.
* 17590 An Incident was resolved in which area loads to frame were not always fully distributed due to a
tolerance check that failed on certain geometries. Although this error was uncommon, it could result
in loss of load.
17840 An Incident was resolved in which user-defined material stress-strain curves were not properly
17849 scaled when used in fiber hinges generated from Section Designer sections. The stresses being used
were normalized by fy or f'c, and the strains by fy/E or f'c/E. This means the hinges were too
flexible. This did not affect parametrically defined stress-strain curves.
Section Designer
Incidents Resolved
17021 An Incident was resolved for Section Designer in which the torsional constant was sometimes
computed incorrectly when shapes were included inside rectangular tubes.
17038 An Incident was resolved in Section Designer in which the display of the fiber locations for one
section would appear when another section was created. This would correct itself when changes
were made to the new section. This is cosmetic only and does not affect results.
17044 An Incident was resolved in which the section properties calculated by Section Designer were in
error if one or more shapes are duplicated, i.e., identically coincident. Specifically, if a shape is
duplicated, then that shape is not being considered in calculating the J value. If all shapes in the SD
section are duplicated, then all properties are computed as zero.
17124 An Incident was resolved in which changing the design type of a Section Designer section from
“Concrete Column” to “No Check/Design” had no effect.
17126 An Incident was resolved in which the P-M2-M3 interaction surface displayed inside Section
Designer for a section with design type “Concrete Column – To Be Designed” was calculated for an
area of rebar arbitrarily scaled upward or downward from the actual amount of steel defined for the
section. This has been changed so that the displayed P-M2-M3 surface inside Section Designer is
always for the actual amount of rebar specified for the section. After performing concrete frame
design, the P-M2-M3 surface for the designed area of rebar can be displayed as part of the design
results.
17404 An Incident was resolved in which Section Designer was sometimes unable to calculate the P-M-M
surface for a concrete shape inside of a steel polygon or a steel polygon inside of a concrete shape.
17411 An Incident was resolved for Section Designer in which, when two or more identical steel
SAP2000 V14.0.0 2009-05-05 Page 8

plates/polygons are overlapped, the section properties were not being calculated correctly.
Similarly, the fiber model for the overlapped steel plates was not excluding the duplicated fibers.
Both issues have been resolved.
17412 An Incident was resolved for Section Designer in which the initial rotation was not being set to zero
when a general shape was converted to a polygon, causing some of the section properties of the
converted polygon not to be calculated correctly.
17415 An Incident was resolved for Section Designer in which the torsional constant (J) and shear areas
(As2 and As3) were incorrectly calculated for the steel box (tube) and pipe sections. The maximum
and minimum axial capacities (Pmax and Pmin) used for moment-curvature were also incorrectly
calculated. Both issues are now resolved.
17417 An Incident was resolved for Section Designer in which the section properties and axial strength
were not properly calculated for a steel box (tube), pipe, or double-angle filled with another
material.
17424 An Incident was resolved in which the Edit > Copy command used when displaying the PMM
interaction surface always copied the Design-Code results even when the Fiber-Model results were
being displayed. Now the selected results will be copied.
17527 An Incident was resolved in which Section Designer was not updating the section properties (area,
moments of inertia, etc.) to reflect changes made to the section until analysis time unless the section
properties, PMM surface, or moment-curvature relationships were displayed inside Section
Designer itself. This was a display issue only and did not affect analysis results.
17599 An Incident was resolved in which Section Designer shapes that were fully contained inside larger
shapes did not automatically govern as expected. However, correct results were obtained if the
larger shape was moved backward behind the smaller shape. This problem was introduced in
Version 12.0.2, and did not exist previously.
17692 An Incident was resolved for Section Designer in which rebar line objects were not being accounted
for in the moment-curvature plot after first being added to the section or imported from tables until
analysis is performed. This means that the displayed moment-curvature plot may not display
correctly, although analysis results were correct, and subsequent displays were correct.
17812 An Incident was resolved in which an exception (runtime error) was sometimes generated after
updating a Section Designer concrete section that has no rebar. This error was rare.
17875 An Incident was resolved for Section Designer in which the replicate and snap-to-intersection
options were not working correctly for reference lines.
Bridge Modeler
Incidents Resolved
16220 An Incident was resolved in which the Bridge Modeler incorrectly generated bearing links for
certain models. When this occurred, the error was obvious.
16308 An Incident was resolved in which changing the length units affected the stations used in a bridge
design request.
16341 An Incident was resolved in which the frame section property assigned to a bridge abutment
17626 property did not appear to remain correctly assigned when returning to the definition in the form.
However, the assignment actually worked correctly.
17089 An Incident was resolved in which the in-span bearing elevation could only be specified as an
integer value in the input form.
17308 An Incident was resolved for the Bridge Modeler in which changing the bearing orientation for an
in-span hinge had no effect along a curved layout line.
17427 An Incident was resolved in which defining a bridge parametric variation sometimes generated an
error if the model was originally created from the new-model Quick Bridge (BrIM) template.
17464 An Incident was resolved in which the shear areas calculated for bridge deck sections were
reversed, i.e., values As2 and As3 were switched. This only affected spine models, which use a
frame element to represent the superstructure. Area and solid models were not affected.
SAP2000 V14.0.0 2009-05-05 Page 9

17711 An Incident was resolved for the Bridge Modeler in which bearing elements did not always connect
properly to girders in models with horizontal curve and negative superelevation.
17778 An Incident was resolved for the Bridge Modeler in which the Bridge Object command “Copy
Tendon to All Girders” produced incorrect results when the deck cross section is using precast U
girders. Previously the tendons got copied to the left most point on the girder cross section. Now
they are being centered on the U girders. Similarly, the command to move an individual tendon will
now center the tendon horizontally on a U girder.
Analysis
Incidents Resolved
* 16398 An Incident was resolved in which the loads applied to layered shells were not active in a nonlinear
analysis. The behavior was correct for linear and nonlinear analysis of homogeneous shells, and for
the linear analysis of layered shells.
17270 An Incident was resolved in which the displacements calculated by the thick-shell and layered-shell
elements were slightly unsymmetrical for symmetrical problems, generally in the fourth significant
figure. Asymmetry was in the j2-j3 direction for a rectangular element. Analysis and design results
were slightly affected. Verification results have changed slightly for some examples.
* 17339 An Incident was resolved in which the geometric stiffness effects (P-delta, large displacements)
were not being included in the stiffness used for the following types of linear analyses when they
were based on the state at the end of a nonlinear analysis: (1) Linear direct-integration time-history
analysis, (2) Hyperstatic analysis, (3) Steady-state analysis, (4) PSD analysis, and (5) Eigen modal
analysis for those modes calculated after an automatic shift; modes calculated for the initial shift did
correctly include the geometric-stiffness effects, and these usually are the modes for which these
effects are most important. The geometric-stiffness effects were correctly included for analyses of
type: linear static, linear multi-step static, Ritz modal, moving load, and buckling. Response-
spectrum and modal time-history cases depend on the modal (Eigen or Ritz) case used as their basis.
17407 An Incident was resolved in which multiple hyperstatic load cases could not be analyzed in the
same run.
17603 An Incident was resolved in which the cable material overwrite was not intended to affect cable
objects, but was being considered when calculating modal composite damping for modal history
cases.
17663 An Incident was resolved in which the error message "File open error -32" sometimes occurred
during the analysis of small nonlinear problems on very fast machines, causing the analysis to
terminate.
17704 An Incident was resolved in which the axial (U1) stiffness for the Rubber Isolator Link property
was being treated as zero during analysis, regardless of the value specified by the user.
17779 An Incident was resolved in which the conjugate-displacement method of load control for nonlinear
static analysis did not work correctly for softening behavior in models without any frame elements,
generally leading to failure to converge when load was dropping.

Incidents Resolved
16157 An Incident was resolved in which the plotted shell design results were incorrect for multi-valued
combinations and response-spectrum cases. Other minor inconsistencies were also present. This has
now been rewritten based on the Eurocode. Except for the multi-valued combinations and
response-spectrum cases, the differences should be small.
17380 An Incident was resolved in which pictures specified in a report contents files were not always
properly included in a generated report.
17563 An Incident was resolved in which, for certain rare cases, the model did not display the undeformed
shape.
SAP2000 V14.0.0 2009-05-05 Page 10

17588 An Incident was resolved in which the units imported from an Excel spreadsheet into the Advanced
Report Writer were properly converted into current units, but the units listed in the printed tables
were not correspondingly converted.
17671 An Incident was resolved in which an exception (runtime error) was generated trying to use the
command Display > Show Virtual Work Diagram when no linear static cases had been defined.
17672 An Incident was resolved in which plot functions for shell stresses and resultants sometimes would
not produce any display, or would produce only zeroes for layered shell stresses.
17708 An incident was resolved where the user specified range for a displayed pushover curve was
internally using database units while the curve itself was internally using present units
17798 An Incident was resolved in which it was not possible to change the bridge object being displayed
in the Bridge Response Display form when viewing design results.
Frame Design
Incidents Resolved
17036 An Incident was resolved in which the deflection load combinations generated for code AISC 360-
05/IBC2006 incorrectly included the text “Notional Loads” in the Notes for the combination. This is
a cosmetic issue only and did not affect any results.
17111 An Incident was resolved in which the program could generate an exception (runtime error) when
plotting the design interaction surface if the moment values were too large.
17115 An Incident was resolved for concrete frame design in which the beam/column capacity ratios and
joint-shear ratios were not being reported for some columns when either: (1) the column was
skewed with respect to the planar frame, or (2) in models having other design materials in addition
to concrete. Codes that consider seismic design were affected: “ACI 318-99,” “ACI 318-02,” “ACI
318-05/IBC 2003,” “CSA A23.3-94,” “CSA A23.3-04,” “Chinese 2002,” Indian “IS 456:2000,” and
“NZS 3101-95.”
17330 An Incident was resolved for steel design using the “AISC360-05/IBC2005” code in which the
program failed to calculate the interaction ratio for a non-compact pipe section.
* 17393 An Incident was resolved in which current design results for a given member could be changed
inadvertently by the following sequence of operations: (1) Select the member. (2) Use the command
Design > Steel/Concrete/etc. Frame Design > View/Revise Overwrites, then click OK or Cancel. (3)
Right-button click on the member to view design details, then click OK. This problem affected all
design codes. Re-running the design would correct the design results. Viewing the design
overwrites using the Overwrites button while viewing design details did not cause this problem.
* 17398 An Incident was resolved in which a steel section reported by design as not being seismically
compact could be reported as being compact after viewing the overwrites and clicking OK.
17402 For steel frame design, the right-click design information form has been slightly changed to always
display the option buttons for Strength and Deflection. Previously the Deflection button was not
shown if results were not available, causing some confusion. Now this button will always be
present, but deactivated if there are no results available.
* 17550 An Incident was resolved in which the calculation of axial compression capacity for singly
symmetric sections (Channel, Tee, Zee) per 1996 AISI cold form steel design code ignored torsional
and torsional-flexural buckling. Now the program considers the torsional and torsional-flexural
buckling in addition to the regular flexural buckling limit state. The program was slightly
unconservative.
17695 An incident was resolved in which a load combination could be selected for more than one design
load combination type through the form, although this was not the intended behavior of the
program. Now a load combination can only be selected for a single design combination type for
each design material.
17748 An Incident was resolved in which, for rare cases, a runtime error was caused when generating
design combinations or incorrect design combinations were being generated. This error was
possible when Load Cases were added, deleted or their order was changed after an initial set of
design combinations had been generated.
SAP2000 V14.0.0 2009-05-05 Page 11

17763 An incident was resolved for steel frame design using the “Chinese 2002” code in which the Design
Type was always being reported as “Beam” in the detailed display even though the column was
being appropriately designed as a column.
17764 An incident was resolved for steel frame design using the “Chinese 2002” code that sometimes
prevented the Seismic Magnification Factor from being available in the Overwrites form even
though seismic load was present in the model. When this was the case, the program was calculating
the seismic magnification factor automatically for specific member types (column, beam, and brace)
in specific framing types (Sway Moment Resisting Frame, Braced Moment Resisting Frame,
Concentrically Braced Frame, and Eccentrically Braced Frame) as recommended by the code. Only
the ability to overwrite the program-determined value was affected.
Bridge Design
Incidents Resolved
16308 An Incident was resolved in which changing the length units affected the stations used in a bridge
design request.
17257 An Incident was resolved in which the tension limit displayed and tabulated for the Bridge Design
principal-stress check could be incorrect due to improper unit conversion.
* 17513 An Incident was resolved for bridge superstructure design of prestressed concrete box-girder
sections in which the shear check was not correctly considering the correspondence between
moment and shear when calculating the amount of shear rebar required.
17515 An Incident was resolved in which the Bridge Design Request demand-set parameters were
sometimes made available for Modify/Show in the AASHTO LRFD and JTG stress checks.
Attempting to edit them gave an error message, although no data was lost. These parameters are
only intended for use with the AASHTO STD stress check.
Database Tables
Incidents Resolved
16401 An Incident was resolved in which the program became unresponsive after changes made during
interactive database editing were applied to a given model.
17034 An Incident was resolved in which importing the database tables for a bridge model may create a
foundation spring with a blank name, generating an error message when this model was
subsequently exported. The analysis and design results for the model were not affected by this issue.
17409 An Incident was resolved in which, during Interactive Database Editing, clicking the “Done” button
too quickly after clicking the “Apply to Model” button could cause the program to become inactive.
Now the “Done” button is deactivated until the “Apply to Model” operation is completed.
17442 An Incident was resolved where importing a text, Excel or Access file from Version 11 may
generate an exception (runtime error) if the imported file has frame hinge assignments.
17444 An Incident was resolved in which an exception (runtime error) was generated when displaying
results in the table for layered-shell resultants.
17472 An Incident was resolved in which an exception (runtime error) was generated when importing
certain Section Designer solid circle shapes.
17478 An Incident was resolved in which an unimportant error message could be generated when
importing a previously exported bridge model having zero-length frame joint offsets at the top web-
flange juncture of bridge girders. No information was lost or corrupted.
17822 An Incident was resolved in which the mode number did not always appear in the Modal
Information database tables.
17507 An Incident was resolved in which the total mass reported for a group was incorrect if any joint in
17575 the group had a mass assignment in terms of weight or volume of material. This is a reporting error
only and did not affect analysis results.
17510 An Incident was resolved in which the import of Section Designer fiber layout did not work
SAP2000 V14.0.0 2009-05-05 Page 12

correctly for a grid other than 3x3 rectangular.
17552 An Incident was resolved in which using Interactive Database Editing to modify the Lane Definition
Data table would sometimes generate an error if any Lanes were defined or deleted using the Bridge
> Lanes menu command before using the Interactive Database Editor.
* 17585 An Incident was resolved in which Section Designer sections imported from database tables or the
Interactive Database Editor did not always correctly maintain the forward/backward ordering of the
contained shapes when many shapes were present in the section.
17587 An Incident was resolved for the Interactive Database Editor in which changing the number of time
steps in the table “Case – Modal History 1 – General” also changed the damping to 5% constant
regardless of the type of damping previously specified.
* 17619 An Incident was resolved in which the casing material for a Caltrans-type Section Designer section
was not properly being imported from database tables.
17646 An incident was resolved in which an exception (runtime error) was generated when importing
certain rectangular shapes in Section Designer sections.
17654 An Incident was resolved in which an exception (runtime error) was being generated when
performing sorting operations on displayed tables that were maximized.
* 17667 An Incident was resolved for database import where only the first one of multiple joint mass
assignments to a given joint was imported. The other joint mass assignments to that joint in the
database table were ignored. This had affected the following three tables: “Joint Added Mass
Assignments”, “Joint Added Mass By Weight Assignments”, and “Joint Added Mass By Volume
Assignments”.
17745 An Incident was resolved in which, when importing a Bridge superstructure design request, a
Bridge-Start to Bridge-End station range would be added to any user-defined station ranges.
17760 An Incident was resolved in which importing database table “Bridge DesReqSuper - Demand -
AASHTO STD 2002 – CboxStress” generated an exception (runtime error).
* 17766 An Incident was resolved in which Section Designer sections imported from database tables
sometimes set the area and diameter to zero for the confinement rebar in a Mander model, resulting
in a change to the generated moment-curvature relationships.
* 17767 An Incident was resolved in which Section Designer sections imported from database tables did not
properly import the setting that determined if rebar limiting strains were to be computed
automatically using Caltrans bar-size-dependent criteria. As a result, the rebar stress-strain curve
could be different after import, affecting the moment-curvature relationship.
17793 An Incident was resolved in which openings in Section Designer shapes were sometimes exported
to database tables as having rebar material properties, causing an error upon import.
17857 An Incident was resolved in which the coordinate system used (Cartesian/cylindrical) to define the
fiber layout in a Section Designer section was not being saved in the data base tables. On import,
the system was being assumed as Cartesian.

Incidents Resolved
17122 An Incident was resolved in which the OpenAPI functions
SapObject.SapModel.PropMaterial.SetOSteel_1,
SapObject.SapModel.PropMaterial.SetOConcrete_1, etc., failed (returned non-zero values) when
the function argument FinalSlope was not positive. This has been resolved by allowing any positive,
negative, or zero value for FinalSlope.
17173 An Incident was resolved in which joints added by calling various API functions were not always
saved in the list used for subsequent searching and merging, leading to the possibility of duplicate
joints.
17305 An Incident was resolved in which the API functions to set design combos don't work correctly but
instead return an error code.
17306 An Incident was resolved in which the MergeOff flag does not work when adding points using in
the OpenAPI, the points were always being merged even if the flag was True.
SAP2000 V14.0.0 2009-05-05 Page 13

17559 An Incident was resolved in which the OpenAPI function SapModel.PropLink.SetLinear returned
an error code when trying to set coupled stiffness and/or damping properties. The function worked
correctly for uncoupled stiffness and/or damping.
17639 An Incident was resolved in which the OpenAPI function
SapModel.DesignConcrete.GetSummaryResultsBeam did not return values for arguments TopArea
and TopCombo.
17694 An incident was resolved in which the API function to add default design combos was only adding
strength combos. It now adds both strength and deflection combos when appropriate..
17784 An incident was resolved in which the OpenAPI functions that set and get design preference and
design overwrite data had minor errors: (1) Conversion to/from present units was not performed for
“Chinese 2002” code overwrite item 16 (concrete cover for closed stirrup) and for “CSA A23.3-04”
code overwrite item 15 (Maximum aggregate size). (2) Items 12, 13, and 14 for GetPreference for
the “NZS 3101-95” code returned incorrect values. (3) Items 7 through 12 for GetOverwrite for the
“Italian DM 14-2-92” code returned incorrect values.
17844 An Incident was resolved in which the Open API function SapModel.PropMaterial.AddQuick
created tendon and rebar materials as isotropic rather than as uniaxial.
Data Files (.SDB, .S2k, .$2K)

Incidents Resolved
17313 An Incident was resolved in which scheduler data was lost when the model was saved as a new
name. Now the data, which is stored in the .BCS file, is copied to a new .BCS file with the new
model name.
Incidents Resolved
17449 An Incident was resolved in which spring stiffness coefficients imported from STAAD files were
sometimes given negative values. This occurred when swapping the spring value directions for the
z-axis up direction.
17811 An Incident was resolved in which the column rotation angle was not properly exported to or
imported from CIS/2 data files.
Documentation
17430 Three new manuals are available as .PDF files and bound into a single printed volume: Introduction
to SAP2000/Bridge, SAP2000/Bridge Seismic Design, and SAP2000/Bridge Superstructure Design.
17719 The CSI Analysis Reference Manual has been corrected for the description of how the frame-
element local 1 axis may change orientation along the length of an element having both a non-
prismatic cross section and a non-centroidal cardinal point. This type of element is common in spine
models generated by the Bridge Modeler.
17791 All documentation and Help systems have been updated for the new release, including new manual
for new features.
Miscellaneous
17043 Version number changed to 14.0.0.
SAP2000 V14.0.0 2009-05-05 Page 14

Release Notes

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

Release Notes

Uploaded by

Copyright:

Available Formats

SAP2000 Version 14.2.

Release Date: 2010-07-30

Changes from V14.2.1 (Released 2010-03-31)

License and Installation

SAP2000 V14.2.2 2010-07-30 Page 1

Application Programming Interface (API)

User Interface and Display

SAP2000 V14.2.2 2010-07-30 Page 2

SAP2000 V14.2.2 2010-07-30 Page 3

SAP2000 V14.2.2 2010-07-30 Page 4

SAP2000 V14.2.2 2010-07-30 Page 5

SAP2000 V14.2.2 2010-07-30 Page 6

SAP2000 V14.2.2 2010-07-30 Page 7

Results Display and Output

SAP2000 V14.2.2 2010-07-30 Page 8

Application Programming Interface (API)

SAP2000 V14.2.2 2010-07-30 Page 9

SAP2000 V14.2.2 2010-07-30 Page 10

Release Date: 2010-03-31

Changes from V14.2.0 (Released 2009-03-23)

User Interface and Display

SAP2000 V14.2.1 2010-03-31 Page 1

Release Date: 2010-03-23

Changes from V14.1.0 (Released 2009-07-29)

User Interface and Display

SAP2000 V14.2.0 2010-03-23 Page 1

SAP2000 V14.2.0 2010-03-23 Page 2

SAP2000 V14.2.0 2010-03-23 Page 3

Results Output and Display

SAP2000 V14.2.0 2010-03-23 Page 4

Data Files (.SDB, .S2K, .$2K)

Application Programming Interface (API)

SAP2000 V14.2.0 2010-03-23 Page 5

License and Installation

User Interface and Display

SAP2000 V14.2.0 2010-03-23 Page 6

SAP2000 V14.2.0 2010-03-23 Page 7

SAP2000 V14.2.0 2010-03-23 Page 8

SAP2000 V14.2.0 2010-03-23 Page 9

SAP2000 V14.2.0 2010-03-23 Page 10

SAP2000 V14.2.0 2010-03-23 Page 11

SAP2000 V14.2.0 2010-03-23 Page 12

SAP2000 V14.2.0 2010-03-23 Page 13

SAP2000 V14.2.0 2010-03-23 Page 14

SAP2000 V14.2.0 2010-03-23 Page 15

SAP2000 V14.2.0 2010-03-23 Page 16

SAP2000 V14.2.0 2010-03-23 Page 17

SAP2000 V14.2.0 2010-03-23 Page 18

SAP2000 V14.2.0 2010-03-23 Page 19

Data Files (.SDB, .S2K, .$2K)

Application Programming Interface (API)

SAP2000 V14.2.0 2010-03-23 Page 20

SAP2000 V14.2.0 2010-03-23 Page 21

SAP2000 V14.2.0 2010-03-23 Page 22

Release Date: 2009-07-29

Changes from V14.0.0 (Released 2009-05-05)

User Interface and Display

SAP2000 V14.1.0 2009-07-29 Page 1

SAP2000 V14.1.0 2009-07-29 Page 2

Application Programming Interface (API)

SAP2000 V14.1.0 2009-07-29 Page 3

User Interface and Display

SAP2000 V14.1.0 2009-07-29 Page 4