v4.0.8

04 Nov 2024 | Maintenance Release
Build 32485

MAINTENANCE RELEASE

KEY BUG FIXES

• The built-in template files have been updated to use the correct C_min factor of 1.8 for poor road surfaces, as specified in the October 2022 version of CS 454. Previous versions used a value of 1.5 from earlier versions of CS 454, which may have led to a bridge resistance overestimate. New template files for HB and CS 458 abnormal loading vehicles have also been added [ref 6302]
• Fixed an issue where the correction factor m_pc, used for ULS analyses, was incorrectly applied to passive lateral earth pressure calculations in a PLS analysis. This could have led to non-conservative Adequacy Factors in cases where the backfill had non-zero cohesion. Where typical non-zero values of drained cohesion intercept are specified, this effect is typically small (less than 3% to 4%) for the default value of m_pc [ref 6335]

NEW FEATURES

• Implemented a diagnostic check to notify users when piers or abutments overlap with skewback blocks. This issue may occur in certain cases involving negative skewback angles, such as when specifying adjacent oviform spans and a low pier height [ref 6061]
• Added a diagnostic check to alert users when the reinforcement shear capacity is modified on contacts that lack other reinforcement properties. This helps prevent potential errors, as such settings may lead to unexpected results if changed unintentionally [ref 6282]
• Updated the output stream and report to display information on the critical load, including the adequacy factor and position, for each scenario in a multi-scenario ULS or PLS problem. This enables users to quickly assess the criticality of each scenario [ref 6307]
• Added the ability to change the display colour of important messages in the output stream, including pre-sets for the three main variations of colour vision deficiency [ref 6316]
• Added a progress bar to indicate when file data is being loaded, especially for larger and more complex files [ref 6318]
• Updated the check for overlapping vehicles within the same scenario. An "Auto" load will now always trigger a warning if another vehicle is added to the scenario. "Single" and "Sequence" loads will also highlight cases where overlapping occurs [ref 6323]

ENHANCEMENTS

• Slight adjustment to the method used for calculating skewback block height to better cope with offset piers, negative skews and overlapping offsets. This may cause a minor change (small fraction of a percent) in the numerical results for a limited number of models [ref 6061]
• Reviewed and updated the User Manual to address issues such as unified spelling conventions, inconsistent figures, and discrepancies between the manual descriptions and the software [ref 6314]
• Updated the first column heading in the Vehicle Explorer to display "Vehicle Name" instead of "No." [ref 6325]
• Added a section covering the Preferences dialog and related settings to the User Manual [ref 6326]
• Improved the logic of the diagnostic check for identical / overlapping load cases between scenarios [ref 6327]
• A new notification has been added to alert users when different scenarios have critical adequacy factors that are nearly identical (within 0.1%). The output stream will display a message to inform the user, and the report will direct readers to the 'Critical Load Cases' table for further details [ref 6330]
• Updated the 'magnify displacements' slider by replacing the percentage symbol (%) with a multiplication symbol (x) to more accurately represent that the displayed displacements (in ULS or PLS mode) are scaled instantaneous movements rather than directly measurable values [ref 6332]
• Improved the messaging displayed when switching licenses to provide clearer guidance on the workflow and available options for the user [ref 6344]
• Added tooltips for the show/hide fill and backing icons [ref 6345]
• Upgraded the MOSEK solver engine, the default solver for many problem types, to v10.2. This provides a number of solve efficiency and stability enhancements [ref 6350]
• Resolved an issue with comment formatting in reports, where lengthy comment strings were displayed without line breaks, potentially causing them to span across pages in an unstructured manner [ref 6360]

BUG FIXES

• Improved the process for identifying backfill blocks during DXF imports, resolving an issue in certain geometries where loads could bypass masonry blocks instead of being correctly applied to them [ref 6284]
• Fixed a bug that would cause a crash when a top level "Span" cell in the Block Explorer was selected [ref 6285]
• Fixed an issue where the auto-installer "Install now?" prompt would appear a second time after selecting "No" on the first instance [ref 6289]
• Fixed an issue where specifying two duplicate "Single" position scenarios caused the adequacy factor chart to appear scrambled in the report output. The software now detects duplicated scenarios and automatically adjusts the zoom level to ensure all points are properly displayed within the chart [Ref 6312]
• Fixed a bug whereby all load vehicles in the same scenario would be shown in the report as having an "Auto" position type when any other vehicle had been set to "Auto" [ref 6313]
• Fixed an issue where the number of copies in a "Sequence" scenario would be set to zero when switching from "Auto". The field now correctly defaults to 1 copy [Ref 6321]
• Fixed an issue where, when specifying multiple vehicles of the same type in a scenario, a "sequence" would only apply if set to a vehicle not in the first row. Sequence data for the first vehicle would be nulled. Sequence data is now saved regardless of position in the table and default sequence values are set properly [ref 6324]
• Fixed an issue where the adequacy factor chart would not display correctly if a "single" load was placed above a "sequence" within a scenario [ref 6324]
• Fixed a bug where the diagnostic dialog window incorrectly stated that PLS partial safety factors were applied for Support Movement analyses. The dialog now correctly confirms that ULS factors are used. A note reflecting this correction has been added to the Support Movement chapter of the User Manual [ref 6335]
• Resolved an issue in 'command line mode' where the output stream occasionally failed to display data (e.g., when using the '-help' command) or caused the caret to return to an incorrect position. [ref 6340]
• Adjusted the text colour of intermediate header rows in the ODT report output. Previously, the white text was difficult to read, and this has been updated for better visibility [ref 6342]
• Corrected a number of minor grammatical inconsistencies in the user interface and report output [ref 6351]
• Fixed a bug in the calculation of limiting adhesion at soil-block interfaces, where the effect of soil cohesion was previously overrepresented. In rare instances, this could result in a slight miscalculation of the maximum horizontal stress applicable to backfill elements. The impact on the adequacy factor after the fix, for affected models, is typically minimal (less than 2% to 3%) [ref 6355]

v4.0.7

28 May 2024 | Maintenance Release
Build 30846

MAINTENANCE RELEASE

• A bug causing a recurring warning message regarding the incorrect distribution of loads in auto-load cases for DXF imported problems has been addressed. Users previously encountered messages indicating that "loads were not distributed correctly". A new method has been implemented for determining extrados block coordinates specifically for imported geometries. This enhancement ensures that loads are distributed more accurately. As a result, instances of the warning message mentioned above will be significantly reduced [ref 6142]
• Fixed a scenario indexing bug that could cause a crash if a pre-v4 file was opened and contained different vehicles within the same loading sequence [ref 6203]
• Fixed a bug that could lead to the erroneous creation of an infinitely long backfill element. This issue stemmed from a failure to correctly identify a block/element intersection point, causing the problem to zoom out indefinitely [ref 6204]
• Improved file load and editing speed. Previously, where a model contained a large number blocks and contacts (~1000s), loading and editing the file could be unacceptably slow. A number of improvements have been made to make file load, materials dialog and geometry dialog changes much faster. Note that very complex files may still experience some slowdown, but this will not be of the same magnitude as previously experienced [ref 6205]
• Fixed a bug that could cause a mismatch between the contact material properties reported in the Materials dialog and the Property Editor for problems involving multi-ring, multi-span geometries [ref 6206]
• Fixed a bug that could cause a crash if 'zero length' contacts were inadvertently enabled through the Property Editor and then saved in the file [re 6207]
• Fixed a bug that meant single load positions above x=50m could not be entered manually in the Scenario Manager (users could still drag vehicles past this point). The software now limits loading to +- 9000m. A warning message is shown if the bridge and a load are far enough apart that they may vanish at full zoom and a diagnostic warning message will be shown if any scenarios contain a vehicle where the nearest axle is > 2x the project size away [ref 6212]
• Fixed a bug whereby user-defined restraint settings for pier support blocks were being reset to full restraint upon solve. This bug impacted both v3 of the software and earlier releases of v4 [ref 6213]
• Diagnostic warnings have been added to indicate when a problem may be overly complex and reduce efficiency. These warnings now appear if a bridge has a significant number of spans or rings containing a large number of blocks [ref 6214]
• Implemented measures to enhance user understanding when applying shear bond strengths. Diagnostic warning messages now alert users to situations where the shear bond is non-zero, particularly when it is non-zero and the coefficient of friction is zero (i.e., shear bond strength dictates failure). Additionally, cells corresponding to non-zero shear bond strengths are now highlighted [ref 6226]
• Fixed a bug that caused positive shear bond contact strength to be reset to zero if the coefficient of sliding friction for the associated contacts was set to zero [ref 6226]
• Based on user feedback, a 'reduced report output' option is now available. This option omits lengthy tables (such as load positions, block geometry, contact properties, and forces) to create a more concise and easier-to-read document [ref 6234]
• Fixed a bug that caused inter-ring sliding properties to be incorrectly reported as "Varies" in the Materials dialog when they were actually consistent. The Property Editor values were not affected by this issue [ref 6241]
• Enhanced the UI and revised the user manual descriptions for several new application features to improve user comprehension [ref 6242]
• Fixed a bug that caused stale material property data to be retrieved and applied in the Materials dialog after toggling crushing, inter-block, or inter-ring sliding off and on. Default values are now reset between projects [ref 6245]
• Fixed an issue where the datum point for measuring backing at the ends of the bridge depended on the "Fill behind abutment" setting. Previously, the top of the skewback block was used when there was no fill behind the abutment, and the span springing level was used when fill behind the abutment was present. Now, both situations use the top of the skewback to maintain compatibility with files from previous software versions. Additionally, the label "Backing below springing height" has been changed to "Backing behind abutment" for clarity [ref 6247]
• Fixed a rare bug that could cause an incorrect image to be displayed in the Geometry dialog when setting a springing offset over a pier. This issue occurred only when the trailing vertical edges of the skewbacks from the joining spans were overlapping [ref 6248]
• Fixed a bug where the 'Masonry Unit Weight' partial factor was incorrectly reported in the 'Masonry Compressive Strength' field of the report output. The correct Masonry Compressive Strength factor was used in the analysis, so the numerical results were unaffected [ref 6258]

v4.0.6

21 Feb 2024 | Maintenance Release
Build 30301

MAINTENANCE RELEASE

• Fixed a rounding error within the DXF import feature that previously caused points to be inaccurately removed from the surface profile. This issue resulted in the absence of a surface and subsequent crashes [ref 6137] [ref 6159]
• Fixed a bug that previously hindered the automatic assignment of backing elements for blocks with a maximum y coordinate on the extrados lower than the overall maximum y coordinate of the block. This notably affected oviform structures imported from DXF files [ref 6141]
• A bug causing a recurring warning message regarding the incorrect distribution of loads in auto-load cases for DXF imported problems has been addressed. Users previously encountered messages indicating that "loads were not distributed correctly". A new method has been implemented for determining extrados block coordinates specifically for imported geometries. This enhancement ensures that loads are distributed more accurately. As a result, instances of the warning message mentioned above will be significantly reduced [ref 6142]
• Fixed formatting of DXF formatting explanation text. Previously, some captions overran into the scroll arrows [ref 6143]
• Fixed the link URLs in the User Manual for Qt and CLP [ref 6158]
• Enhanced compatibility with files created in older versions of the software. Blank load cases are now properly ignored during loading. Previously, in RING v4, attempting to set up and solve these cases could result in a crash. With this improvement, users will benefit from a more stable experience when working with legacy files [ref 6161]
• Addressed a bug which previously led to crashes at the conclusion of the wizard process when importing DXF files. Users can now complete the import process smoothly without encountering any unexpected behaviour [ref 6161]
• Fixed a bug affecting the new spline interpolation algorithm, which could cause the software to insert erroneous points into a span geometry when loading old files, resulting in shape distortion. Users can now rely on the spline interpolation algorithm to accurately maintain the intended shape of the geometry [ref 6163] [ref 6165]
• Resolved an issue where selecting a "Varies" entry in numeric editor boxes within the Property Editor, then navigating away, would result in it being replaced with an auto-fill value [ref 6165]
• Reduced the width of the selection button used during zone assignment in DXF import. This adjustment aims to minimise the obscuring of geometry, providing users with a clearer view and a more efficient process [ref 6171]

v4.0.5

13 Dec 2023 | Maintenance Release
Build 30070

MAINTENANCE RELEASE

• Fixed a bug that caused the default scale for post-solve deformation to be blank until set manually [ref 6102]
• Display missing project details metadata when selecting a file in Windows 10 file explorer. Note that Windows 11 does not display file metadata [ref 6103]
• Updates and improvements to the license activation dialog. Removed superfluous text and improved behaviour when using an erroneous activation key. Prevent a local license file path being displayed in network server field when restarting with a new license [ref 6104]
• Numerous fixes and enhancements to the LimitState:RING User Manual [ref 6106]
• Prevented logfile from being output when running the software in GUI mode [ref 6107]
• Updated the output in command line mode to display diagnostic information after any user-defined changes are made. Also improved the text formatting and ensured that files solved in command line mode do not appear in the "recent files" list when using the software in GUI mode [ref 6108]
• Removed "this is the critical scenario" wording from the report for problems containing only one load case [ref 6109]
• Fixed a number of issues when opening ring1.5 (.RNG) files. The default for explicit modelling of abutments is now false and the default (1kN) load vehicle will now retain its name. Note that, in some circumstances a sequential load defined in ring1.5 will display all loads simultaneously when the file is first opened. This is not a concern and the view can be corrected by opening the loading dialog and clicking OK [ref 6110]
• Removed superfluous options from the startup tab in the preferences dialog [ref 6111]
• Added two missing ring1.5 files to the ringInputFiles.zip file referred to in the User Manual [ref 6112]
• Fixed a bug that could cause a crash when attempting to save or export an 'empty' project [ref 6113]
• Corrected the logic that is used when determining point order in the moment, normal and shear diagrams. This prevents some portions being displayed 'inside out' [ref 6114]
• Move warning about inability to solve particular problem features with a Free license (e.g. reinforcement) into the pre-solve diagnostics [ref 6120]
• Allow copying from the output window using the CTRL+C keyboard shortcut. Previously only right-click > Copy would copy [ref 6122]
• Added "Load Effects" partial safety factor to information provided in the output stream [ref 6123]
• Fixed a bug that could cause a crash when cancelling the deletion of a scenario in the Loading Dialog [ref 6124]
• Improved the way in which "unstable" solutions are handled and reported. Unstable solutions will first be double-checked to confirm that this outcome is valid. If so, the output will report "unstable" as the critical case and, in multiple load-case scenarios, the chart will display unstable data points at AF=1e-4 on the log scale [ref 6125]
• Added license information to report output [ref 6131]
• Updated the 2_Span_Rail_Bridge_Central_Pier_Settlement.ring example file to remove properties that are unused, but that caused warning messages to be displayed regarding "unrecognised properties" [ref 6132]
• Permit the "Default 100kN Single Axle" vehicle to be overridden by itself when accessed through the command line interface [ref 6134]
• Replace references to "CU Triple Axle" vehicle in the Command Line Interface examples in the User Manual, as this vehicle no longer exists (under this name) in the database [ref 6134]
• Change scenario naming convention when overriding the vehicle via the command line. The new scenario will now be named "Scenario 1", rather than assuming the name of the replacing vehicle [ref 6134]

v4.0.4

20 Nov 2023 | Major Release
Build 29934

MAJOR RELEASE

HIGHLIGHTS

New Workflow for Defining Vehicle Loading

• Added the ability to automatically seek out the critical position for a selected loading vehicle. This removes the need to define a series of regularly spaced loads and ensures that the critical load position is found quickly and easily. A graph showing adequacy factor vs vehicle position is now also displayed [ref:5532]

• Provision of a new, more powerful, interface for defining load cases, with the user now able to choose between "Single", "Sequence" and "Auto" types for vehicle positioning, and the ability to specify a range of different loading "Scenarios" to analyse [ref:5651]

New CAD Import Functionality

• Users can now import geometries from CAD (via DXF files), providing a more flexible approach to problem definition. Features such as internal voids, and blockwork backing can be readily included in the model * potentially leading to a more accurate representation of the problem at hand. [ref:5514]

More Flexible Wizard Definition of Bridge Geometry

• New functionality to make it much easier to specify spans that spring from different levels at pier heads [ref:3273]

• Added the ability to model end abutments that retain fill. Previously, explicitly modelled end abutments would be treated as freestanding, without fill material behind them. Users can now specify backfill and also backing behind end abutments in their model [ref:5038]

New Permissible Limit State Analysis Mode

• A Permissible Limit State (PLS) analysis mode has been added, enabling a PLS analysis to be performed quickly and easily. The PLS is defined as the state beyond which load induced damage is likely to occur - see the freely available CIRIA C800 guidance document for more details

New Bridge Template Functionality

• A new model can now be created using key settings from an existing file. With the "Bridge Template" functionality, partial factors, effective width settings and material properties will all be copied across into the New Bridge Wizard, while the problem geometry is free for the user to define as required [ref:5034]

New Console Mode Functionality

• New console mode functionality that provides the user with the ability to modify and / or solve problems from the command line or a batch file, without the speed overheads associated with the GUI [ref:5795,5872]

More Informative

• When a model is solved a new "Diagnostics" dialog provides a wide range of information on the model to the user, at "Information", "Warning" and "Error" levels. This is designed to greatly reduce the likelihood of a model containing features that the user is unaware of, thereby reducing the likelihood of modelling errors [ref:5547]

• Added functionality that allows the user to graphically query the material properties of blocks and contacts. With this useful tool, strengths, weights etc. are coloured on a scale, according to their magnitude. This allows quick visual checking of whether material properties across the model are as

• Added the ability to display backfill and backing forces as arrows, scaled to the magnitude of the force on each block and with the ability to scale the arrows representing fill and backfill forces [ref:4036,5375,5404]

• Improved output pane text. Solving now displays the adequacy factor in green for values greater than or equal to 1.0, or red for values below 1.0. Additionally, the type of analysis (ULS, PLS or support movement) is also reported [ref:5867]

Auto-Save and Undo/Redo Functionality

• Auto-save backups are triggered every 5 minutes (unless the user is selecting objects, to avoid clearing the selection) [ref:5708]

• Greatly expanded coverage of Undo/Redo functionality, and increased reliability [ref:5927]

Apple Mac Version

• For the first time, LimitState:RING can be run on an Apple Mac computer with either an Intel or Apple silicon CPU [ref:5846,5668]

Other Highlights

• A shear bond strength can now be defined for masonry joints / contacts. This provides a simple means of taking account of "adhesion" between blocks, e.g. in multi-ring bridges. A partial factor can be applied to the value specified [ref:4678,5947]

• Arbitrary forces and/or moments acting on blocks can now be specified. This allows actions from a wide range of sources to be modelled [ref:4647]

• The strength of backing material can now be defined by the user (was fixed at 5MPa) [ref:5389]

OTHER CHANGES

Report Improvements

• Major improvements to the report layout, including addition of an adequacy factor graph, improvements to the quality for the failure mechanism image and better layout / spacing of the data tables, making the document easier to read [ref:5263]

• Added the option to save the report in Open Document (.ODT) file format, providing better compatibility with popular word processing applications, such as Microsoft Word and LibreOffice Writer. Also improved quality of the .RTF output [ref:5899]

• Improved styling of the PDF version of the report [ref:5715]

Partial Safety Factor Changes

• Load effects factor "gamma_f3" added to allow the effects of model uncertainty to be incorporated in an assessment [ref:5940]

• Partial factors that are set to a value other than unity are now highlighted in the "Partial Factors" dialog. This makes it easier for the user to identify the factors that will have an effect on the analysis results [ref:5939]

• The default axle load partial factor (ULS) has been changed to 1.5 to reflect the value typically recommended in modern assessment codes. The default PLS partial factors on masonry strength have been set to 2.0, to reflect the recommendations of the CIRIA C800 assessment guidance [ref:5976]

• Explanatory text added to clarify the nature of each set of partial factors [ref:4232]

Messages, Diagnostics & Warnings

• Warn the user when the number of blocks in a span is changed and that span has modified properties that will need to be re-applied [ref:5631]

• Warn when files contain blocks with multiple edges exposed to the fill, as the calculation of applied pressures may be affected [ref:5330]

• Improved the information provided when a multi-segment profile is specified with invalid reference points [ref:5214]

• Comprehensive review of the data included in the various explorers. Information is now complete and ordered in a logical manner [ref:5952]

• Warning message displayed when user chooses to plot thrust or hinges in projects with hinging disabled [ref:5443]

• Warn the user to check the block / contact properties if edits are made to the geometry of a span with varying material properties. This ensures that all objects have the expected properties before a solve is undertaken [ref:2924]

• Added text to help explain the status of the limiting forces in fill elements (especially those connecting two blocks e.g. over a pier) [ref:5937]

Handling Bridge Geometry

• Upgraded the spline algorithm used to create interpolated span profiles. In previous versions, inter-ring contacts could be missed for certain multi-ring arch geometries. The upgrade helps provide a more robust geometry

  and contact creation process. (Note that old files using a spline generated profile may have additional control points added to the span data in order to maintain the same shape.) [ref:5981]

• Improved the way in which the extrados point data is stored, to remove the need to re-calculate quite as often [ref:5823]

• Improved generation of skewback block geometry in edge cases where overlapping may occur [ref:5462]

• Improved the algorithm for identifying inter-ring contacts [ref:2936]

• Improved the method by which skewback blocks are created, allowing negative angles to be treated correctly and preventing them from turning inside-out [ref:2936]

• Improved the auto-generation of the surface layer. The wizard now calculates the maximum y dimension of the blocks and adds 500mm to this as the base of the surface layer. This helps prevent overlapping of the structure and surface [ref:5382]

Sequential Gross Displacement Analysis

• Undertaking a sequential, gross-displacement, analysis in a semi-automated way is now possible. Contact intrados coordinates can be copied from the contact explorer (for "minimum" post-solve deformation) and pasted into a user-defined profile, for subsequent re-analysis. This can then be repeated a number of times to facilitate a gross displacement analysis [ref:5935]

Solver

• Added a "maximum problem size" setting to prevent unduly long solves from being instigated. If the problem size exceeds the specified value, a diagnostic error message is shown. The user can then increase the limit or amend the model as appropriate [ref:5933]

• Upgraded the MOSEK solver engine, the default solver for many problem types, to v10. This provides a number of efficiency improvements as well as emulation compatibility for computers with Apple silicon CPUs [ref:5668]

• When solving DXF generated problems the Mosek solver is used by default [ref:5912]

• Various improvements to memory management [ref:5716]

Vehicle Loading

• Added functionality to read in old files with a fixed vehicle spacing between load cases as a "sequence" [ref:5979]

• Make the direction of travel of vehicles clear by adding an arrow in the viewer and allowing the user to set the direction in the Scenario Manager. Previously, local axle spacings were measured in the positive x direction from the first axle. This meant that a left-to-right traversal across the bridge was likely corresponding to a vehicle reversing over the structure. RING 4.0 also interprets files made in older versions and updates the direction and spacing settings to fit with this new method of working [ref:5723]

• Added a range of UK and international code vehicles to the database, including those included in CS454 [ref:5297, 5547]

• Set the default vehicle to 100kN single axle (rather than 1kN single Axle) [ref:5799]

• Set the default load type to "Auto" [ref:5799]

• Overhauled the process of adding load cases, to make it much more intuitive for the user [ref:5487]

• Allow the user to add a new loading scenario based on a problem created when using the "drag and solve" functionality [ref:5575]

• Improved the layout of the "Vehicle Database" dialog, making it easier to interpret [ref:5718]

• Added buttons to more easily delete scenarios (load cases) [ref:5733]

• Updated the filename for the vehicle database (VehcleDatabase4.xml) to ensure side-by-side compatibility with older versions of the software. Note that any user-defined vehicles will need to be imported into RING 4.0 before they can be used, unless they are active within a scenario in a file that is being opened [ref:6045]

• Prevent user-defined vehicles from assuming duplicate names unless explicitly set by the user. Also warn the user if a vehicle is defined with incomplete data [ref:6044]

• Identify axles that are subject to a dynamic factor by outlining them in red [ref:2877]

UI/UX Overhaul

• New look interface, with updated icons, cursors and general styling [ref:5416,5474]

• Updated the cursor images to match the new application styling [ref:5435]

• Changes in the way in which application scaling is handled for different resolution monitors and display scale settings. Dialogs, text and images should adapt better to these different conditions [ref:5452,5517]

• Disabled a number of icons that remain active when no project is present [ref:5441, 5476]

• Fill profile and ring data tables will now auto-expand to fit the size of any pasted data (previously only the first row of data would be added) [ref:5333]

• Updated the .ring file icon to match new application styling [ref:5918]

• Scale the display of hinges according to the problem geometry (to avoid them being overly large or small in the viewer) [ref:5677]

• Prevent pixelated icons and cursors by scaling according to monitor resolution [ref:5473]

• Reviewed tab order for all application dialogs [ref:5222]

• Made selecting objects in problems containing many blocks much easier. The scaling of contact handles now accounts for the number of blocks, meaning that they are narrower for more complex models [ref:5470]

• Ensure interface elements are appropriately scaled when viewed on high-definition (4k) monitors [ref:5294]

• Updated the license selection dialog to improve usability and add "Free mode" option [ref:5190]

• Improved the readability of symbols throughout the user interface [ref:5838]

• Updated the "New Bridge Wizard" with a range of visual and behavioural enhancements. The design is cleaner and the workflow is smoother and easier to understand. An improved layout and images ensure that bridge creation and subsequent editing is straightforward and quick [ref:5201, 5426]

• Tweaked the resolution and antialiasing settings to improve the rendering quality at all levels [ref:5531]

• Added a lasso select function. This mode allows quick and accurate selection of objects in complex shaped model geometries (e.g. if using a DXF imported model) [ref:5683]

• Updated the CTRL shortcut keys for improved efficiency and consistency with standard conventions [ref:5900]

• Improved layout for the Support Movement Wizard [ref:5571]

• Added extra information to the status bar text when solving and ensure this is displayed, even if detailed information is given in the output window [ref:5904]

• Structure the Property Editor as a tree view, allowing more fine-grained categorisation of data [ref:5255]

• Add input field validation to prevent negative values being entered into the Property Editor [ref:5965]

• Renamed 'Trial' mode to 'Free' mode and simplified the licensing dialog to help ensure users understand the options available [ref:5954]

• Cause Explorer trees to be expanded by default. This prevents the tree collapsing after data is modified, which disrupts the user experience [ref:6013]

• Various improvements to the copy / paste behaviour when using the explorers. Previously e.g. the cell selection area needed to be the same size when pasting as it was when copying [ref:5995]

• Fixed cell tabbing behaviour in the explorers so that focus moves from left to right and skips hidden columns [ref:6022]

• Removed the "All bridge parts" option from the dropdown in the masonry material properties dialog. This became over complex once e.g. the new ability to model offset piers was made available. The availability of new functionality to colour the model according to material property, alongside enhanced (rectangle and lasso) selection methods, ensures that the material properties of individual areas of the model can be quickly and easily altered and queried [ref:6035]

• Reduced the default 'Normal' level of post-solve displacement scaling to make it more moderate [ref:6055]

• Exposed the abutment angle settings in the Geometry dialog, though hide the values if "auto calculate" is selected [ref:6049]

• Active backfill/backing elements (those that have reached limiting values) are coloured differently according to element type and analysis type [ref:6007, 6057]

• Added descriptive disambiguation text in the Property Editor to clarify which directions are regarded as positive [ref:5507]

• A wide range of other minor updates to the GUI have been implemented in order to improve the user experience and assist the problem setup and solve workflow [ref:5736]

Bugfixes

• Fixed a bug in which displaying an Explorer could cause the software to crash. This could occur in different ways, such opening and closing an Explorer after resizing, leaving the software on too long with an open Explorer, amongst others [ref:5717]

• Perform check for numerical inaccuracies irrespective of the deformation state of the solution [ref:5978]

• Fixed a bug that caused the "Insert Span" dialog to be remain on screen if the user clicked OK on the parent "Geometry" dialog [ref:5632]

• Fixed a bug that meant that new blocks and contacts were displayed on screen, irrespective of the "show/hide" toggle status [ref:5534]

• Fixed a bug that could arise when invalid midspan / quarterspan rise values were entered (e.g. if the midspan value is significantly lower than the quarterspan value) [ref:5973]

• Fixed a bug in which deleting a pointed span could cause a neighbouring span to be deleted instead [ref:5963]

• Fixed a bug where span-skewback connection geometry could become nonsensical for complex bridges. Saved files with such geometries are fixed upon opening [ref:5289]

• Fixed a typographical error in equation A.4 of the manual [ref:5060]

• Rationalized the behaviour of pasting data into the span profile table. A (0,0) entry is now ensured if the top left entry in the pasted data is non-zero. Previously, the software would re-calculate the coordinate data by translating such that the first (springing) point became (0,0) [ref:5827]

• Fixed a bug that could cause files with user-defined profiles, saved in an old version to be read in incorrectly by LimitState:RING 4.x [ref:5643]

• Fixed a bug that could cause 'phantom' reinforcement elements to be displayed in problems where reinforcement is not present [ref:2987]

• Fixed a bug that could cause the load case spin box to not reset to 1 when opening a new file [ref:3991]

Other Changes

• The default angle of shear resistance for the soil model has been increased from 30 degrees to 37.5 degrees. This more accurately reflects a well compacted medium-dense frictional soil of the type likely to be encountered in masonry arch bridges in practice [ref:5945]

• Improved the copy/paste behaviour for data entered from other tables within the software and from external spreadsheet software [ref:5788, 5781]

• Retain the displaced state when saving a solved problem (in v3, the displacement would be zeroed) [ref:5783]

• For multi-monitor systems, try to ensure pop-up dialogs and other objects appear on the same screen as the main application [ref:5749]

• Added auto-update functionality. When new versions of the software become available, the auto-update will download these and prompt to install [ref:5697]

• Changed the behaviour of the software when modelling abutments explicitly. Previously, it was possible to specify zero blocks and the "explicitly model abutment" option was then automatically unchecked. Now, if the option is checked, a minimum of one block must be specified [ref:5183]

• Set minimum allowable ring thickness to 1mm [ref:3130]

• Updated the behaviour when copying and pasting profile coordinates such that i) 0,0 is automatically removed from the start of any pasted data and ii) blank rows are not automatically appended at the end of the table [ref:3030]

• Use the material properties set in the wizard when creating new objects (contacts, blocks etc.). Previously, the inbuilt application defaults (e.g. 20kN/m3 unit weight, 5N/mm2 crushing strength) would be used when a user created a new pier or span. This could lead to unexpected results [ref:5354]

• Changed the display units of moments to kNm/m [ref:5525]

v3.2.c

26 Feb 2020 | Maintenance Release
Build 24386

MAINTENANCE RELEASE

Update

• Academic licenses are now accessed from new server address in advance of shutdown of legacy server in Q3 2020 [ref:5407]

v3.2.b

17 Nov 2016 | Maintenance Release
Build 20773

MAINTENANCE RELEASE

Bugfixes

• Fixed a bug that could prevent a solution from being obtained when working with certain specific bridge geometries [ref:4975]

v3.2.a

18 Feb 2016| Maintenance Release
Build 20141

MAINTENANCE RELEASE

• Introduced an 'Auto-select solver' feature. This allows the software to select the most appropriate solver engine for different classes of problem. For models involving only single ring spans, the CLP * solver will be chosen by default. For models involving one or more multiple ring spans, MOSEK will be used. The user has the option to override this [ref:4796]
• Updated the backing model. Users can now set the limiting horizontal force that a backing element can resist. This allows areas of differing limiting backing strengths to be specified [ref:4835]
• Added more detailed description of backing properties and behaviour to the User Manual [ref:4800]
• Added clarification regarding force and moment reporting to the User Manual [ref:4805]
• Enhance usability by highlighting and selecting the text when renaming a vehicle [ref:4836]
• Fixed a bug that could cause the wrong selection type to be displayed as being selected [ref:4426]
• Upgraded the installer [ref:4576]

v3.1.b

24 Sep 2014 | French Language Release
Build 17345

FRENCH LANGUAGE RELEASE

• French language version introduced [ref:3756]
• Increased quality of hinges as displayed after solve [ref:4238]

v3.1.a

29 Jul 2014 | Maintenance Release
Build 16989

MAINTENANCE RELEASE

• Increased solve speeds for problems involving multiple load cases by up to 70% [ref:4216] [ref:4217]
• Significantly reduced memory footprint of software so that problems with a much larger number of load cases can be solved without running out of memory. e.g. in the case of a bridge containing 10 spans (created using the new bridge wizard with default parameters) and carrying a 10 axle highway vehicle, a total of approx. 800 load cases can now be analysed using the 32bit version of the software (which can access up to 2GB of memory). This is approximately 4x as many load cases as using previous versions. [ref:4207]
• 64bit version introduced (includes update of COIN 3D graphics library to v3.1.3) [ref:4209]

v3.0.f

23 Oct 2013 | Maintenance Release
Build 15296

MAINTENANCE RELEASE

• Fixed a bug that could cause the report generation to crash if no load cases were specified in the project. Also separated vehicles into two tables in the report ("Vehicles in Project" and "Vehicles in Load Cases") [ref:3946]
• Fixed a minor bug in the PDF of the User Manual that caused citations to be displayed as '?' [ref:3952]

v3.0.e

01 Oct 2013 | Maintenance Release
Build 15130

MAINTENANCE RELEASE

• Added full support for Windows 8 (previously it was necessary to run the executable in compatibility mode) [ref:3603]
• Updated the Installation and Licensing Guide. Now more informative and generally applicable to all LimitState products [ref:2817]
• Added the option to export the problem geometry (blocks, fill and surface profile) in DXF file format (e.g. for potential import into other programs such as LimitState:GEO) [ref:3633]
• The report now provides the coordinates of the blocks and contacts in all cases. Previously, if the solution was deformed when the report was generated, the deformed geometry was used [ref:3272]
• Increased the numerical stability of solves by modifying the scale factor on lambda applied in the pre-solve. Also warn the user if numerical inaccuracies are detected in the part of the solution required to display the collapse mechanism [ref:3023]
• Optimized the selection speed for the "Contact Select Tool" [ref:3003]
• Fixed a bug that, on a small number of Windows XP machines, could cause warning messages on install (Program ended with an exit code) and on execution (Assertion failed!). Note that the software would often still work in these instances if the messages were ignored [ref:3323]
• Fixed a bug related to the treatment of floating-point object coordinates within the program that could, on rare occasions, cause small numerical inaccuracies to be introduced into the solution [ref:3038]
• Fix a bug in the generation of interpolated arch profiles that caused a memory leak on solve. For problems containing many arch profile points and blocks, this could cause the software to reach the memory limit for a single process and crash if solve was attempted many times in the same session [ref:3337]
• Fixed a bug that caused segmental arches with a rise equal to exactly half of the span (i.e. semi-circular) to sometimes report an Adequacy Factor of 1e30 on solve (along with a 'no hinge' mechanism) [ref:3642]
• Fixed a bug that caused all load cases to be called "Load Case 1" in non-English language versions of the software [ref:3126]
• Fixed the tabbing order in the Partial Factors dialog (previously did not tab directly from "Axle load" to "Dynamic" fields [ref:3120]
• Fixed a problem that could cause saved files to fail to open, in very rare cases, with error message that "the file has been damaged". A workaround for previous versions is to right-click the file in Windows Explorer and select "Convert to XML". The created file will open correctly [ref:3116]
• Message reporting the number of days remaining on current license was potentially misleading; now report 'license expires in 0 days' during last licensed day [ref:3321]
• Fixed a bug that caused the names of individual rings in the "Contact Select Tool" to be replaced with the word "Project" [ref:3006]
• Fixed a bug in the support movement functionality that prevented the user from selecting support blocks of piers of inserted spans (the software would report that the block had already been selected) [ref:3099]
• Fixed a bug that caused the check for an academic license to hang on occasion [ref:3905]

v3.0.d

10 Jan 2012 | Maintenance Release
Build 12154

MAINTENANCE RELEASE

• Minor updates to Czech language translations [ref:3073]
• Fixed a problem that could cause saved files to fail to open, in very rare cases, with error message that "the file has been damaged". A workaround for previous versions is to right-click the file in Windows Explorer and select "Convert to XML". The created file will open correctly [ref:3136]

v3.0.c

25 Nov 2011 | Maintenance Release
Build 12091

MAINTENANCE RELEASE

• Italian, Czech and Spanish made available in version 3, and installer
• Corrected handling of ',' as a decimal separator in several dialogs [ref:3103]
• Corrected vehicle database. Replaced BD21 Annex F '3 tonne, Single Axle' with '2 tonne, Single Axle'. Note: BD21 Annex F requires a bridge to successfully carry a 2 tonne single axle load in order to give a 3 tonne vehicle load rating. Models using the original 3 tonne vehicle will, therefore, give a conservative solution when checked [ref:3098]
• After switching Bridge type from Railway (underline) to Highway, the 'Vehicle Database' dialog omitted required columns for user-defined vehicles. This problem is now fixed. A workaround for previous versions is to restart the software [ref:3069]
• Fixed bug which could lead to an error being reported when the key pressed after editing a numeric value in the Property Editor [ref:3047]
• Thrustline & moment/shear/ normal force diagrams now display properly when some contacts (i.e. masonry joints) in the project are not enabled or are constrained in some way [ref:2873]
• Added explanatory text to the Property Editor description of how reinforcement locations are determined. The user is now alerted to the fact that the reinforcement depth defaults to 0mm if a value greater than 1/2 the contact length is specified [ref:3058]
• Make the order of OK and Cancel buttons consistent across dialogs [ref:3104]
• Fixed issue with some tables that caused them to crop the displayed data, particularly when using non-English language interface [ref:3064]
• Loads icon now always displays properly in 'New Bridge Wizard' [ref:3105]
• Previously, the distributed example 'beam reinforcement' gave the correct solution numerically but displacements, if scaled, would occur in the horizontal direction. This has been fixed so that displacement is vertical [ref:3052]
• User Guide updated, including additional guidance on how to include reinforcement in a model [re 3019, 3101]
• Modified axle 'distance' description to improve clarity [ref:3015]

v3.0.b

19 Apr 2011 | Maintenance Release
Build 11817

MAINTENANCE RELEASE

• Pointed arch profile is now available [ref:2989]
• User-defined extrados is now available for interpolated profiles [ref:3007]
• Enable keyboard shortcuts to improve copy/paste function in tables [ref:3018]
• Fixed a very small (less than 0.01mm) change in problem geometry when saving and reloading models with segmental arches, which resulted in small change in the predicted collapse load (less than 1 part in a million, and never of any engineering significance) [ref:3039]
• For academic license users, remove a potential second display of the academic license dialog [ref:2969]
• Installing LimitState:RING 3.0 on a computer alongside version 2 now defaults to opening the latest version when double-clicking a project file [ref:3020]
• Users are now given the option of applying changes to the 'dynamic factor' vehicle attribute over all load cases rather than just the current one [ref:3024]
• Fixed a bug in load case definition dialog that could cause a crash if "Delete all cases" was selected while adding new vehicles to the first load case [ref:3027]
• Display warning when opening LimitState:RING 2.0 files that contain user-defined profiles (LimitState:Ring 2.0 could sometimes corrupt files containing multi-segment arch profiles, causing inconsistent behaviour of the points in the intrados table) [ref:3017]
• Bending moment, shear force and thrust diagrams now reliably displayed for piers as well as arch rings [ref:3013]

v3.0.a

24 Feb 2011 | Major Release
Build 11704

MAJOR RELEASE

NEW ARCH PROFILE TYPES

• The addition of several new profile types allows users to more closely model the true shape of an arch [ref:2724]
• Segmental - The arch profile is formed from a single segment of a circle using the crown rise and span measurements.
• Multi-segment (user-defined) - The arch profile is formed from multiple segments of circles, based on user-entered intrados and/or extrados points.
• Interpolated (user-defined) - The arch profile is formed from an interpolated `best-fit' shape based on a series of user-entered intrados and/or extrados points.
• Three-centered (pseudo-elliptic) - The arch profile is elliptical and is formed from segments of three circles using the crown rise and span measurements.

ENHANCED ANALYSIS ENGINE

• State-of-the-art MOSEK optimizer now used to obtain solutions, in many cases dramatically reducing run times [ref:2937]
• More robust and efficient - the MOSEK solver is designed to solve large-scale optimization problems in a highly efficient manner, bringing significant performance benefits to LimitState:RING
• Users can now specify the precision of the answer obtained using the Preferences dialog

MORE INFORMATIVE

• More analysis data is provided in the output window - load case data, vehicle position, effective bridge width and solution information are now all shown by default [ref:2878]
• Software now reports an 'adequacy factor' rather than a 'failure load factor', which is a more appropriate descriptor when partial factors on loads are specified.
• Allow users to view diagrams depicting normal force, shear force and bending moment at contact surfaces for analysed problems [ref:2297]
• The report output has been updated and contains new sections (e.g. backing details), additional data and an easier to read layout [ref:2419, 2965]
• Added a number of example files relating to the validation of the software, its features and application to 'real-life' bridges [ref:2994]

MODEL REINFORCEMENT

• Allow modelling of arch bridge problems containing reinforcement [ref:2160, 2161, 2162, 2164, 2165, 2166, 2207, 2297, 2418]

STREAMLINED DOCUMENTATION

• All supporting documentation has been merged into a single comprehensive User Manual, which is available to view through the built-in help system in the software or separately in pdf form. Existing sections have been expanded and / or updated to make the document more informative [ref:2742]

ENHANCED LOAD MANAGEMENT

• Many improvements made to the process of applying loads e.g. 'Delete all load cases (Except Current)' button added and option to move all vehicles in a load case simultaneously [ref:2888]
• Dynamic load factor can now be applied on a per load case basis (obviating the need to create special vehicles with dynamic factors applied to different axles) [ref:2930]
• Specifying which axles have dynamic factors applied is now possible in the load case dialog, rather than having to create custom vehicles. Existing files where custom vehicles have been created with dynamic axles will continue to function as before [ref:2930]
• Removed the previous maximum limit of 100,000mm for an initial load case position [ref:2961]
• Vehicle database updated with additional industry-standard highway and railway loading models [ref:2904]
• Allow up to 999 copies of a load case to be made (up from 99 copies) [ref:2910]

VISUAL IMPROVEMENTS

• Visual style of user interface, icons and graphics updated [ref:2879, 2945, 2960]
• Enhanced 3D rotation functionality [ref:2923]
• Updated 'New bridge wizard' tab images [ref:2928]
• Increased font size of greek partial factor symbols to improve readability [ref:2948]

INTEROPERABILITY

• Added the capability to transfer data between tables within LimitState:RING and external software (e.g. Microsoft Excel) [ref:2949]

EFFECTIVE WIDTH IMPROVEMENTS

• Introduced a user-defined 'maximum effective width' cutoff value when using the 'auto-calculated' effective width option [ref:1247]
• Renamed 'bridge width' to 'effective bridge width' for clarity [ref:2341]

CHANGES IN BEHAVIOUR

• Maximum limiting finite masonry material compressive strength set to 500 N/mm2 for new problems to avoid convergence problems e.g. when complex multi-ring problems are involved (N.B. an infinite material strength can still be specified) [ref:2958]
• The default value of Mpc, a modification factor used to determine the passive restraint offered by the backfill, has been increased from 0.01 to 0.05 [ref:3000]

OTHER CHANGES AND BUGFIXES

• Optimized code to more efficiently handle multi-axle / multi-load-case problems [ref:603]
• Minor modifications to text in materials dialog (railway model only) [ref:1247]
• Software checks whether drive exists on 'Save' and 'Save As' and warns if the file did not save correctly [ref:1993, 2814]
• Fixed a bug that caused an error when a project was saved after changing the profile shape from user-defined multi-segmental to 'segmental' [ref:2788]
• Fixed bug that, in some circumstances, caused a new report pdf file to save over an old report pdf file that had been generated in the same session [ref:2829]
• Fixed a bug which led to an error being reported when selecting the 'Auto computed' bridge width option in the first page of the 'New Bridge Wizard' [ref:2850]
• Various changes to make it easier for users to differentiate between load case names and numbers (when the former are of the form "Load Case X") [ref:2906]
• Fixed bug that prevented 'mirror=true' being saved with file for vehicles [ref:2944]
• Prevented the possibility of creating abutment blocks with zero area, which could result in an unstable model [ref:2972]
• Fixed bug that could, when following a certain series of geometry modification / save steps, result in a runtime exception being triggered [ref:2979]
• To avoid potentially erroneous geometries from being created, can no longerpecify negative user-defined abutment angles [ref:1248]
• Negative adequacy factor solutions are now also shown in the report, on the rare occasions that these are encountered [ref:2419]
• Switching a bridge from being a 'railway' bridge to a 'highway' bridge sometimes led to an error being reported. This is now fixed [ref:2713]
• Attempting to save the project during a solve would cause a crash. This has now been disabled [ref:2759]
• Fixed bug that caused "Save As" to create filenames with multiple ".ring" suffixes [ref:2915]
• Fix a very rarely encountered problem that prevented results from load cases analysed after a problematic load case (for which a solution could not be found) from being reported [ref:2920]
• Require a load to be defined before performing an analysis. Previous versions crashed on solve without loads [ref:2992]
• No longer iterate unnecessarily once a problem is found to be unstable under its own self weight [ref:2419]
• Warn of unsaved changes on exit following changes in the 'Property Editor' [ref:2796]
• User is no longer prompted to save if they have merely solved the project, or if have clicked 'Cancel' on a program dialog [ref:2796]
• User-defined profile points no longer lost when switching between profile types in 'Edit Bridge' geometry dialog [ref:2892]
• Load case 'spinbox' widened so that higher load case numbers are not cropped [ref:2907]

v2.0.k

23 Dec 2009 | Major Release
Build 10866 (RLM) / 10867 (FlexLM)

MAJOR RELEASE

• Software deals with problems involving multiple vehicles and spans more effectively - solution times significantly reduced in many cases [ref: 2801]
• Fixed bug (introduced in 2.0j) which meant that when the bridge geometry was changed, the load distribution was only updated for the currently displayed load case [ref: 2473]
• Upgraded vehicle database - added UK Highways Agency BD21 (road) and BD37 (road and railway) loading vehicles [ref: 1499]
• Added support for RLM licensing system (not 2.0k[FlexLM]) [ref:2770]
• License information available via the Help menu (2.0k[RLM] only) [ref:2770]
• New flexible academic licensing system introduced [ref:2770]

Tagged 2.0k, 2.0k[RLM] and 2.0k[FlexLM]

v2.0.j

17 Oct 2008 | Major Release

MAJOR RELEASE

MAJOR CHANGES

• Interface translated into French and Spanish, with 'beta' German and Arabic translations also available (change language via: Tools>Preferences)
• Added UK Highways Agency BD37 & BD21 highway vehicles to the Vehicle Database (HB loading and Fire Engines) [ref:1499]
• Fixed save bug caused by explicitly modelling abutments (unticking this option after previously modelling abutments caused 'Fatal error ap60' message) [ref:1476]
• Auto-calculated bridge width now always updated when geometry altered [ref:1509]
• Loads now always redistributed when the current load case is changed [ref:1509]
• Fixed bug that sometimes prevented help from being accessed when multiple versions of ring were installed on a single PC [ref:900]
• Visualization of instances where axle width is greater than bridge width improved [ref:1509]
• Fixed bug that could cause crash when swapping between pier and abutment tabs in the new bridge wizard [ref:1568]
• User can no longer define a spurious 'empty' new vehicle [ref:2137]

MINOR CHANGES

• Potential error prevented if intrados and extrados ring profiles overlap (warning message shown and modelling disallowed until geometry is corrected) [ref:753]
• Failure load factor now always correctly displayed in output (previously, an incorrect value may be displayed when repeatedly solving the same problem many times) [ref:1284]
• Fixed bug that caused 'Procedure entry point not found' error (sometimes occurred when installing to WIN2000 machines) [ref:2188]
• Theory and Modelling Guide worked example (Appendix A) - image modified for clarity (previously could confuse) [ref:2199]
• Changes to editable vehicle properties made in the Property Editor now reflected in the model [ref:1271]
• Fixed wizard pier tab - height now reads 'ha' in both image and text [ref:1567]
• Vehicle Database - resizing window now affects whole dialog (previously only Vehicle library resized, causing problems when reading with non-standard font size) [ref:1411]
• Console message now reports when load case 1 is critical in a multi-load case analysis [ref:2000]
• Whitespace now stripped from user-defined vehicle files when importing into Vehicle Database (could previously cause problems) [ref:1495]
• Fixed bug with 'recent files list' that sometimes caused it to work incorrectly when two files with the same name were present [ref:2159]
• Improvements to various message boxes to make them easier to understand [ref:1238]

v2.0.h

03 Dec 2007 | Major Release

MAJOR RELEASE

MAJOR CHANGES

• Different default values for highway and railway bridges [ref:1216, 1220]:
  • Highway: transverse distribution through fill and surface fill & longitudinal distribution through surface fill changed to 26.6° (2:1).
  • Railway: longitudinal and transverse distribution through ballast changed to 15° (in accordance with UIC774-2R); transverse distribution through fill changed to 30°. Now no additional transverse distribution through barrel.
• Railway sleeper breadth default changed from 300mm to 250mm (standard value) [ref:1227]
• Fixed vehicle database transcription errors [ref:1206]:
  • ‘CU double axle (1.85m)’ loading corrected to read 99.77kN per axle
  • ‘CU air suspended axle (1.85m)’ name changed to ‘CU triple air suspended axle (2.60m)’
• Fixed open/save problem affecting user-defined fill forces [ref:1203]
• Fixed railway track properties bug (changes to certain properties were not applied until after a vehicle had been moved) [ref:1164]
• ‘Theory and Modelling Guide’ now included in distribution.

MINOR CHANGES

• Some sample files updated for consistency with ‘Theory and Modelling Guide’ [ref:1240]
• Further enhancements to report output [ref:1039]: improved layout, no cropping of bridge image, significantly reduced report generation time, option of saving as html, option for user to ‘Select all’ in report. Also:
  • Report image renamed ‘Mode of response’ [ref:1234].
  • Analysis results now removed from report when problem unsolved [ref:1234].
• Program more responsive when report for large project requested [ref:1235]
• Improved detection of contacts for multi-ring problems containing only a small number of blocks [ref:839]
• All angles are now shown in degrees (except those related to rotations) [ref:1223]
• Fixed bug preventing all hinges from being highlighted in certain problems [ref:751]
• Fixed bug that caused 'Fatal error ap60' message to sometimes appear when entering user-defined span profiles [ref:753]
• ‘1kN Single Axle Load’ vehicle now shown in vehicles database [ref:1163]
• For consistency: ‘Load Factor’ now referred to as ‘Failure Load Factor’ everywhere except during solve (for conciseness) [ref:1199]. Other minor corrections to text [ref:1219]
• Fixed context sensitive help bug (when modelling multi-span bridges, incorrect / blank pages were shown for certain tabs) [ref:1221]
• Ensured that dialog giving option to reload vehicle database after this has been changed is only displayed at startup [ref:1237]
• Fixed bug that caused 'Cancel' button in 'Load Cases' dialog to disable after opening the vehicle database [ref:1173]

v2.0.g

18 Oct 2007 | Maintenance Release

MAINTENANCE RELEASE

• Initial enhancements to report output [ref:1039]
• Fixed report generation problem (report not generated if ‘Application Data’ folder was not present, e.g. in non-English versions of Windows) [ref:1075]

v2.0.f

24 Sep 2007 | Maintenance Release

MAINTENANCE RELEASE

• Fixed number tolerance / rounding problems (caused a warning to appear when opening some ring1.5 files) [ref:942, 985]
• Set precision of span and rise measurements to 2 decimal places [ref:1000]

v2.0.e

14 Sep 2007 | Maintenance Release

MAINTENANCE RELEASE

• Minor changes to facilitate translation of the software [ref:958, 959]

v2.0.d

20 Aug 2007 | Major Release

MAJOR RELEASE

• Improved error trapping, allowing save in case of a serious error [ref:533]
• Fixed Support Movement Wizard bug (a currently selected block could not be subsequently selected in the Support Movement Wizard) [ref:804]
• Ctrl key is now used for multiple object selection (instead of Shift key) [ref:807]
• Fixed ‘aborted analysis’ bug (program failed when re-solving a previously aborted analysis) [ref:853]
• Fixed problem setting up multi-ring arches (program occasionally crashed when navigating through the new bridge wizard in a particular way) [ref:854]
• Fixed ‘clear all’ bug (in some cases selected objects could not be cleared) [ref:857]
• Updated installation guide with information regarding floating single user licenses (dongles) [ref:863]
• Updated 'License enquiry' button and explanatory text [ref:865]
• Improved formatting of report details for problems with infinite crushing strength [ref:893]

v2.0.c

26 Jul 2007 | Maintenance Release

MAINTENANCE RELEASE

• Improved quality of collapse mechanism image in report [ref:702]
• Fixed report printing bug (user was not initially asked to select a printer) [ref:703]
• Enhancement to allow company logo images to be added to the report header and footer [ref:759]
• Enhancement to allow the name of the default load case to be saved automatically [ref:766]
• Default railway track load corrected to 2kN/m2 (was 20kN/m2) [ref:776]
• Improved procedure used to obtain the MAC (Ethernet adaptor) address for use in the license request email [ref:799]
• Fixed problem which meant that ring2.0 files defining problems with certain user defined contacts could not be opened [ref:831]
• Updated description of the 'ID' field in the property editor [ref:843]

v2.0.b

10 Jul 2007 | Limited Release

LIMITED RELEASE

• Enhanced solution convergence properties [ref:831]
• Fixed ring1.5 file compatibility bug (ring1.5 files with inter-ring constraints would not open) [ref:831]

v2.0.a

15 May 2007 | Initial Release

INITIAL RELEASE