ReleaseNotesSAP2000v2610
ReleaseNotesSAP2000v2610
0 Release Notes
© 2024 Computers and Structures, Inc.
This document lists changes made to SAP2000 since v26.0.1, released 13-September-2024. Items marked
with an asterisk (*) in the first column are more significant.
Database Tables
Incidents Resolved
* Ticket Description
10799 An incident was resolved where in an uncommon situation assigned frame point loads did
not show up in the database tables.
10874 An incident was resolved where the table name displayed in the first row of an Excel
worksheet was incorrect when the Excel worksheet was created from the interactive
database.
User Interface
Incidents Resolved
* Ticket Description
* 10856 An incident was resolved where running many load cases that iterated very quickly in
parallel for a long time caused (1) frequent flickering on the analysis monitor form, (2)
incorrect total progress on the main form, and (3) sometimes unexpected termination of the
program.
10912 An incident was resolved where in some cases the temperature value on the Assign Frame
Material Temperature form was being unexpectedly converted.
This document lists changes made to SAP2000 since v26.0.0, released 05-September-2024. Items marked
with an asterisk (*) in the first column are more significant.
This document lists changes made to SAP2000 since v25.3.1, released 11-July-2024. Items marked with
an asterisk (*) in the first column are more significant.
API
Enhancements Implemented
* Ticket Description
* 10555 Following enhancements have been made to the API: SAP2000 (SAP2000v1.dll) and cross-
product API (CSiAPIv1.dll) libraries have been updated to target .NET Standard 2.0,
increasing range of compatibility to API clients targeting .NET Standard 2.0, .NET Framework
4.6.1 to 4.8.1 and .NET (Core) 2 to .NET 8. Increased support for complex plugins where
dependencies of the plugin might conflict with dependencies of SAP2000. Better error
handling for API clients calling API functions that were not implemented by the connected
version of SAP2000. The Remote API feature, used to start and/or connect to a running
instance of SAP2000 on a Remote Computer, has been disabled with the release of SAP2000
v26.0.0. This functionality may be added back to the program in a future release. Please see
API help file for details regarding backward and forward compatibility.
10745 An enhancement has been made to allow an unallocated array argument to be passed into
cPointObject.GetSpring(), cPointObject.GetSpringCoupled(), cPointElm.GetSpring(), and
cPointElm.GetSpringCoupled() API methods to store the returned spring stiffness values.
Loading
Enhancements Implemented
* Ticket Description
10765 A minor enhancement was made to the iterative scheme used to calculate the wave length
using Stokes 5th Order Wave Theory. This allows iteration convergence for a much larger set
of wave parameters. Results should not change where the old iterative scheme converged
and no iteration failure message was given.
Structural Model
Enhancements Implemented
* Ticket Description
* 10741 A new link property 'Sumitomo Viscoelastic Damper' has been implemented to represent
the behavior of high-damping rubber vibration control damper devices produced by
Sumitomo Rubber Industries. The nonlinear damper behavior is a combination of elastic,
plastic, and viscous damping behavior and can be enabled for any of the translational
degrees of freedom independently. Information about the damper and its parameters is
available in the 'Sumitomo Viscoelastic Damper Link Property' technical note provided with
the program.
User Interface
Enhancements Implemented
* Ticket Description
8466 A change has been made to keep user defined stress-strain curves for materials unchanged
if later revisions are made to the Young's Modulus and/or material strength. This allows
users to experiment with different effective Young's Modulus and material strength for
linear analysis and design without disturbing the user defined stress-strain curves used for
nonlinear analysis. Earlier versions would scale the user stress-strain curves when the
Young's Modulus or material strength were modified. Parametric stress-strain curves are
unaffected by this change.
Database Tables
Incidents Resolved
* Ticket Description
8342 An incident was resolved where the Plot Function Trace table may not have been available if
only steady state and/or power spectral density plot functions existed. Additionally, an issue
was also fixed where the database table did not have the StepType and StepNum fields
populated if the named set plot function trace was for a steady state or power spectral
density load case.
10672 An incident was resolved in the Auto Seismic - NBCC 2015 database table, where the
StructType value was always populated with Steel MF even when the value selected in the
load pattern definition was something else. This was an issue in filling the database table
and did not affect the calculated loads applied to the structure.
Graphics
Incidents Resolved
* Ticket Description
10453 An incident was resolved to correct the location of point labels in 2D views when the
selected coordinate system was not Global.
Structural Model
Incidents Resolved
* Ticket Description
10355 An incident has been resolved for the super-T frame section property calculations in which
the section properties would be calculated incorrectly when the super-T frame section was
defined with a closed flange. In this case, the section properties were larger than expected
and the analysis results were calculated based on the section properties calculated and
displayed within the program
User Interface
Incidents Resolved
* Ticket Description
10647 An incident was resolved in the NBCC 2020 auto seismic load pattern definition form where
some of the parameters were not correctly recovered when opening the form for an existing
definition. This was a user interface issue only and the loading and analysis results were
consistent with the last values on the form when the OK button was pressed. The values
displayed in the database tables were correct and consistent with the loading and analysis
results.
10696 An incident was resolved in the Section Cut Data form, where the advanced axes option
would be selected upon clicking OK on the form when the selected coordinate system was
Global. This issue was introduced in v25.2.0. Results would correspond with the defined
section cut definition shown in the database tables.