Terms & Conditions

Contents

Go to -> Company Details

Go to -> Licensing of Oasys software – Licensing Documentation PDF

Go to -> Help with ordering

Privacy and Cookies

Data Security

Website Terms and Conditions

Software Licensing Terms


Privacy and Cookies

We may change this privacy notice from time to time by updating this page.

What information do we collect?

When you use this website, we may collect the following information:

  • the areas of the website that you visit
  • information about your computer, such as which browser you are using, your network location, the type of connection you are using (e.g. broadband, ADSL etc) and your IP address

We do this by using cookies, which are small files that help us track how our visitors use the website and enable us to understand where we can improve your experience. If you would like to find out which cookies we use and the information they track see our Cookies Policy.

Once you submit or register information through our website we will know who you are and your activities on this website and information about you and/or your company may be recorded on our systems. For example, we may ask for personal information when you download our software including:

  • your name
  • company name
  • email address
  • postal address
  • telephone number
  • country where you are based
  • Social media ID
  • your comments/questions
  • services/markets you are interested in

We may also collect personal information from telephone calls and/or other correspondence with you.

What do we do with the information we collect?

The information we capture is used for various purposes. The main purpose is to provide you with our services (whether available via the website or offline). We also use the information for:

  • website development
  • understanding how our visitors interact on the website
  • understanding what our clients are interested in
  • understanding what potential clients are interested in
  • dealing with enquiries/concerns
  • marketing our services and people to you
  • market research
  • service development
  • internal record keeping

Marketing

We would like to provide you with information about our services and other information which we think you may find interesting. We may send you such information by post, email and/or telephone, unless you have asked us not to do so.

We will not provide your personal information to other organisations for marketing purposes without your explicit consent.

If at any time you do not want your information used for direct marketing purposes, please contact us or follow the unsubscribe link in our marketing email messages.

Who do we share this information with?

We may share your personal information with companies acting on our behalf who will only use the information to provide that service. However, we will retain control of your data and any third party service provider that we use must act in accordance with our instructions. We may also share your personal information with a purchaser or potential purchaser of our business.

In some circumstances, we may have to disclose your personal information by law, because a court or the police or other law enforcement agency has asked us for it.

How to get copies of or amend the information we have collected

You may request details of the personal information that we hold about you under data protection laws. If you would like a copy of the information held about you please write to us at oasys@arup.com or at: Data Protection Officer, 13 Fitzroy Street, London, UK, W1T 4BQ. Please note that we may charge a small £10 administration fee for information requests.

If you think any information we have about you is incorrect or incomplete, please email us as soon as possible. We will correct or update any information as soon as we can.

top ]


Data Security

We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect, including locked cabinets, electronic password protection and pass card access to buildings.

If at any point you suspect or receive a suspicious communication from someone suggesting they work for Oasys or a website claiming to be affiliated with Oasys, please forward the communication to us or report the incident by email to oasys@arup.com or in writing to Oasys, 13 Fitzroy Street, London, UK, W1T 4BQ as soon as possible.

top ]


Website Terms and Conditions

The contents of this web site are protected by copyright and other intellectual property rights under international conventions. No copying of any words, images, graphic representations or other information contained in this web site is permitted without the prior written permission of the webmaster for this site.

Oasys accepts no responsibility for the content of any external site that links to or from this site.

top ]


Software Licensing Terms

Terms and Conditions of Purchase

The full conditions of purchase and maintenance for all Oasys software are set out in the Oasys Software Licence and Support Agreement. All prices are subject to TAX at the current rate.

Prices and specifications are subject to change without notice – please ask for a written quotation.

Although every care has been taken to ensure the accuracy of all information contained herein, the contents do not form or constitute a representation, warranty, or part of any contract.

Superseded Versions of Terms and Conditions

Oasys keeps copies of all superseded versions of its terms and conditions.

Maintenance & Support Services

Twelve months support and maintenance is included with most products. Thereafter maintenance is typically 20% of the current sales price.

An annual maintenance service is available for most programs after the first year.

This service includes:

  • telephone/fax/email/web based support
  • free software updates available via internet download
  • personalised output header for many products

Xdisp Change Log

All notable changes to Xdisp will be documented within the change log.

New Features

Xdisp 19.4: New Features

  • New 64 bit version.
  • Utility damage assessment can be performed for jointed and unjointed utilities.
  • Improved utility damage assessment solver

Xdisp 19.4: Minor Enhancements

  • Option to skip duplicate locations while importing and exporting displacements.
    [ME XDISP-31](Added 29 October 2015; released in Xdisp 19.4 Build 4)
  • Import of Pdisp data files insofar as is feasible(i.e. displacement data, background data, imported displacements and displacement results.
    [ME XDISP-37](Added 3 June 2016; released in Xdisp 19.4 Build 4)
  • Gateways are dockable panes.
    [ME XDISP-39](Added 22 March 2016; released in Xdisp 19.4 Build 4)
  • Option to input the font percentage for printing the tabular output to a paper/pdf.
    [ME XDISP-48](Added 08 June 2016; released in Xdisp 19.4 Build 4)
  • Adding additional options (Wizard, Translate All, Crop) to the context menu of background data table.
    [ME XDISP-50](Added 03 May 2016; released in Xdisp 19.4 Build 4)
  • Grid View of Tabular Output.
    [ME XDISP-57](Added 25 May 2016; released in Xdisp 19.4 Build 4)
  • Optional stripey output in Tabular Output (shading of alternate rows of tables).
    [ME XDISP-60](Added 03 June 2016; released in Xdisp 19.4 Build 4)
  • Displacement polylines could be input, which can be used for specific utility damage.
    [ME XDISP-61](Added 20 May 2016; released in Xdisp 19.4 Build 4)
  • Inform user that Tabular Output “is being prepared. Please wait.” in case the lack of information causes them to feel the program has crashed.
    [ME XDISP-81](Added 28 September 2016; released in Xdisp 19.4 Build 6)
  • Displacement warnings in the analysis progress window may be duplicated if repeated analyses are run.
    [ME XDISP-89] (Released in Build 9)
  • The analysis progress dialog would better prohibit horizontal scrolling, and wrap its warning messages rather than scroll both horizontally and vertically.
    [NCR XDISP-90] (Released in Build 9)
  • Removal of warning in Displacement Data table re numbers of intervals to prevent possible repetitive warning. Moved to pre-analysis checks. (As NCR PDISP-92).
    [NCR XDISP-91] (Released in Build 9)
  • Horizontal displacement option (as resultant of X and Y) added to 3D Graphics and CSV output. Already in Plan View.
    [NCR XDISP-106] (Released in Build 9)
  • Xdisp’s display of undeflected displacement grids on the 3D graphics is unhelpful as a simple filled rectangle rather than mesh.
    [NCR XDISP-110] (Released in Build 9)
  • The 3D graph view of ground movement curves (polynomial or linear curve fits) may be initiated with inappropriately small or large scaling and data point markers, requiring laborious rescaling by the user. (Some further work required.)
    [NCR XDISP-111] (Released in Build 9)
  • Amendment of 3D Graphics background from light yellow to white (as Pdisp).
    [NCR XDISP-113] (Released in Build 9)
  • Xdisp may give many similar warnings if a model contains many tunnels with the same name. It would be better to impose a limit on the number of such similar warnings.
    [NCR XDISP-114] (Released in Build 9)
  • Update to licensing.
    [NCR XDISP-115] (Released in Build 9)

Fixes

  • Reference used for utilites should be mentioned in the the help file.
    [NCR XDISP-21](Fixed 11 February 2016; released in Xdisp 19.4 Build 4)
  • Program is crashing when the polygon (polygonal excavation) is closed by the input of first coordinate again in the end.
    [NCR XDISP-26](Fixed 15 February 2016; released in Xdisp 19.4 Build 4)
  • Young’s modulus and Poisson’s ratio input not required in the acceptance criteria and parameters table.
    [NCR XDISP-28](Fixed 23 February 2016; released in Xdisp 19.4 Build 4)
  • Displacement lines, points and grids with duplicate names should be identified before analysis, and should be displayed as warnings.
    [NCR XDISP-32](Fixed 22 April 2016; released in Xdisp 19.4 Build 4)
  • Xdisp may crash when tunnels and displacement lines are deleted in the 3D Graphics editor.
    [NCR XDISP-34](Fixed 19 January 2016; released in Xdisp 19.4 Build 4)
  • The 3D Graphics Settings Wizard (Displacements’ page) is unusable when large numbers of imported displacements are available.
    [NCR XDISP-41](Fixed 08 April 2016; released in Xdisp 19.4 Build 4)
  • Blank entries in the “Vertical Offsets…” column of the “Specifc Structures” Table View leading to no building damange calculations being performed, and a misleading reference to settlements being less than the sensitivity.
    [NCR XDISP-41](Fixed 13 April 2016; released in Xdisp 19.4 Build 4)
  • “F1” on Utility data dialogs is not routing to the help file.
    [NCR XDISP-41](Fixed 05 April 2016; released in Xdisp 19.4 Build 4)
  • Xdisp does not always recognise the level of a displacement point as being equal to the level specified in the excavations’ dialog “If surface movement curves… apply them between the surface and x m” checkbox.
    [NCR XDISP-44](Fixed 14 April 2016; released in Xdisp 19.4 Build 4)
  • When listed in the Tabular Output, imported displacements show an unnecessary “Line no.” column, with meaningless figures. This should be a reference index to the Imported Displacements table.
    [NCR XDISP-52](Fixed 06 May 2016; released in Xdisp 19.4 Build 4)
  • Deletion of ground movements curves corrupts their indexing for excavations, and may lead to a “black” table of data in the excvations data dialog.
    [NCR XDISP-56](Fixed 25 May 2016; released in Xdisp 19.4 Build 4)
  • ResultsView is refreshed unnecessarily when some tables (Acceptance riteria, specific buildings…) are opened.
    [NCR XDISP-58](Fixed 04 June 2016; released in Xdisp 19.4 Build 4)
  • Criteria value is printed in the tabular output even when “No” is selected against it in the input table.
    [NCR XDISP-59](Fixed 04 June 2016; released in Xdisp 19.4 Build 4)
  • Xdisp’s Help files (pdf and chm) still refer to the non-existing lever-arm in the utilities (specific and generic) tables.
    [NCR XDISP-62](Fixed 03 August 2016; released in Xdisp 19.4 Build 6)
  • Specific utility wizard, when initially loaded, doesn’t show the selected option in the ‘Jointed’ combo box (instead it shows plain text).
    [NCR XDISP-64](Fixed 03 August 2016; released in Xdisp 19.4 Build 6)
  • Although duplicate points may be used to model stepped excavations along straight sides, if they are used at corners then zero displacements may result in the sweep around those corners.
    [NCR XDISP-65 & NCR XDISP-76](Fixed 04 August 2016 & 26 August 2016; released in Xdisp 19.4 Build 6)
  • The Utility Strain calculation options are not being saved to the file.
    [NCR XDISP-68](Fixed 22 August 2016; released in Xdisp 19.4 Build 6)
  • Xdisp may calculate slightly incorrect horizontal movements (typically overestimating) around a corner of an excavation whose adjoining sides have different ground movement curves applied.
    [NCR XDISP-72](Fixed 25 August 2016; released in Xdisp 19.4 Build 6)
  • Help file information for csv export of utility damage results is incomplete.
    [NCR XDISP-77](Fixed 01 September 2016; released in Xdisp 19.4 Build 6)
  • If building damage results are chosen for display in the Tabular Output then the “Combined Segments” table is shown always, even though combined segments may not have been set up.
    [NCR XDISP-80](Fixed 28 September 2016; released in Xdisp 19.4 Build 6)
  • Xdisp crashes in some cases when specific utilities associated with displacement polylines are analysed.
    [NCR XDISP-82](Fixed 06 October 2016; released in Xdisp 19.4 Build 6)
  • Xdisp 19.4 crashes when building damage assessment data is exported.
    [NCR XDISP-83](Fixed 18 October 2016; released in Xdisp 19.4 Build 6)
  • Xdisp doesn’t allow the user to view graphs for displacement polylines on the plan view.
    [NCR XDISP-84](Fixed 18 October 2016; released in Xdisp 19.4 Build 6)
  • In the plan view, displacement points on displacement polylines are visible only for the first segment.
    [NCR XDISP-85](Fixed 19 October 2016; released in Xdisp 19.4 Build 6)
  • Plan view doesn’t always support graphs for specific utilities associated with displacement polylines.
    [NCR XDISP-86](Fixed 20 October 2016; released in Xdisp 19.4 Build 6)
  • Licensing fix (commercial builds only).
    [NCR XDISP-109] (Released in Build 8)
  • Menu: Graphics -> Font presents old options of “Bigger” and “Smaller” only. New style scaling is not offered.
    [NCR XDISP-88] (Released in Build 9)
  • Graphical Input : In the z-view, buildings can’t be added if the displacement line is parallel to x-axis or y-axis.
    [NCR XDISP-94] (Released in Build 9)
  • Print and Print Preview buttons are disabled when the Tabular Output is displayed in the Grid View.
    [NCR XDISP-95] (Released in Build 9)
  • Xdisp may give incorrect ground movements arising from excavations if a sub-surface movement ground movement curve is used with linear interpolation.
    [NCR XDISP-108] (Released in Build 9)
  • Xdisp’s 3D Graphics may show “sawtooth” contours, with some areas uncoloured.
    [NCR XDISP-112] (Released in Build 9)
  • NCR XDISP-117 2D Plan, Buildings, Menus The “Buildings” button on the Plan toolbar is ineffective and has lost its drop arrow to select Specific or Generic Buildings. Build 10
  • NCR XDISP-118 3D Graphics 3D Graphics may open with a frame only, and no contents. Build 10
  • NCR XDISP-119 Import, Analysis When importing DXF data containing buildings, a building’s “end distance along line” may be set to be greater than the line’s length if the line is inclined. The program may crash when an analysis is performed.. Build 10

New Features

Xdisp 19.3: New Features

  • Graphical input, editing and deletion of model data via the 3D Graphics View.
  • Generic Building Damage Assessment.
  • Specific Utility Damage Assessment.
  • Generic Utility Damage Assessment.
  • Zoom to cursor position in the 3DGraphics view.
  • Improved granularity for selection of elements and displacement entities for display in the 3D Graphics View.
  • Excavations’ input views are now dialogs rather than form views.
  • The Page Setup dialog’s check-boxes are replaced by an expandable tree control, to select the contents to be displayed by the Tabular Output.
  • Multithreading of analyses to allow work on other data files while analysis proceeds in one.
  • Polyline entities to specify areas for generic building damage assessment and generic utility damage assessment.
  • Import of background data from dxf files. Imported data can be viewed in a table and in the 3D Graphics View.
  • Option in Excavations to allow the surface movement curves to be applied below the surface till a level specified.

Xdisp 19.3: Minor Enhancements

  • Displacement Data dialog should be accessible via the wizard button.
    [ME5325](Added 29 October 2010; released in Xdisp 19.3 (SP 1) Build 20)
  • The user should be warned when he tries to delete a displacement line on which a building rests.
    [ME6886](Added 09 September 2011; released in Xdisp 19.3 (SP 1) Build 20)
  • Single master table for tunnels and single master table for buildings. i.e. no tabs.
    [ME6887](Added 30 August 2011; released in Xdisp 19.3 (SP 1) Build 20)
  • Polylines table view doesn’t show more than 4 significant figures.
    [ME7169](Added 14 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Precise values of tunnels’ coordinates are not printed in tabular output as they are displayed in engineering format.
    [ME 8092](Fixed 07 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Functioning of the progress bar on the “Progress of Checks and Analysis” dialog needs improvement.
    [ME 8114](Fixed 17 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • An option should be provided to enable/disable the excavations which are input.
    [ME 8135](Fixed 26 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Generic Utility Damage and Generic Building Damage Results’ tables don’t get fitted properly when they are print previewed.
    [ME 8133](Fixed 01 July 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • START_TABLE and END_TABLE flags for utility damage results and building damage results are not positioned properly when the tabular output is exported to a csv file.
    [ME 8252](Fixed 26 July 2013; released in Xdisp 19.3 (SP 1) Build 28)
  • Volume Loss input for tunnels may now be input with negative values. This will generate ground movement away from tunnels. Results should be treated with caution and verified.
    [ME 8844](Fixed 12 March 2014; released in Xdisp 19.3 (SP 1) Build 32)
  • Polygonal excavations dialog could usefully allow more coordinates without the need to scroll.
    [ME XDISP-46](Fixed 15 April 2016; released in Xdisp 19.3 Build 49)
  • Revision to digital signature of installer.
    [ME XDISP-55](Fixed 21 April 2016; released in Xdisp 19.3 Build 49)

Fixes

  • Circular Excavation input allows input of negative diameter.
    [NCR 5379](Fixed 18 November 2010; released in Xdisp 19.3 (SP 1) Build 20)
  • Displacement entity legend remains, in the 3D Graphics View, even after deletion of the entity.
    [NCR 5651](Fixed 07 January 2011; released in Xdisp 19.3 (SP 1) Build 20)
  • Labelling of buildings may be drawn away from the building.
    [NCR 5875](Fixed 11 April 2011; released in Xdisp 19.3 (SP 1) Build 20)
  • Displacement length shown in the structures table is incorrect if the length unit is anything other than metres.
    [NCR 6663](Fixed 20 January 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • Program crashes if a set of displacements are imported into Xdisp from a csv file which has blank records at the end.
    [NCR 6724](Fixed 01 February 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • Buildings and their associated displacement lines may not coincide on the Plan View when zoomed.
    [NCR 6742](Fixed 03 February 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • Grid number displayed wrongly in the Tabular Output of results.
    [NCR 6828](Fixed 24 February 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • The Tunnels table view does not complete the ‘Layers’ field until the end of the line. It should complete as the k derivation method is selected.
    [NCR 6885](Fixed 21 December 2011; released in Xdisp 19.3 (SP 1) Build 20)
  • In “Displacement and Strain Results” table of the Results view, the units row is incorrect.
    [NCR 7019](Fixed 05 April 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • Xdisp may fail to plot line contours on the 2D Plan View for a displacement grid whose second point’s x value, or whose first pont’s y value is less than the second point’s y value.
    [NCR 7049](Fixed 19 April 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • Building Damage Results for segments in compression may be incorrect.
    [NCR 7135](Fixed 21 May 2012; released in Xdisp 19.3 (SP 1) Build 20)
  • File | Export | Building Damage Assessment Data… crashes Xdisp when run on Windows 7.
    [NCR 6261](Fixed 31 May 2012; released in Xdisp 19.3 (SP 1) Build 21)
  • “StandardDimensionsAndCriteria.xdd” is not shipped with the installer.
    [NCR 7162](Fixed 31 May 2012; released in Xdisp 19.3 (SP 1) Build 21)
  • Xdisp crashes when the data copied from excel sheet is pasted in Tunnels table view.
    [NCR 7165](Fixed 06 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Strains reported in Building Damage Export are incorrect.
    [NCR 7167](Fixed 07 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • The sub-surface movement curve graph cannot be zoomed in or out.
    [NCR 7152](Fixed 14 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Xdisp crashes when a Generic structures data record is copy pasted.
    [NCR 7207](Fixed 21 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Xdisp ignores checking last tunnel while setting up tunnel warnings.
    [NCR 7210](Fixed 22 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Xdisp fails to treat the settlement trough limit sensitivity as an absolute value (so applicable to both settlement and heave), thereby preventing hogging or sagging sections to be initiated for buildings whose end displacements are in heave.
    [NCR 7211](Fixed 22 June 2012; released in Xdisp 19.3 (SP 1) Build 23)
  • Xdisp crashes in the Ground Movement Curves’ View if a new curve is viewed without entering any coordinates.
    [NCR 5142](Fixed 06 December 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Apply button becomes enabled when the Displacements Page of the 3D Graphics Settings Wizard is made active even when there are no changes made to that page’s items.
    [NCR 5855](Fixed 06 December 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Xdisp freezes when entering a grid in a model which has results if the Plan View is kept open.
    [NCR 7225](Fixed 22 August 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • If a new row is added to a table view in a model which has results, then the program warns the user that results will be deleted. However, if the user clicks ‘cancel’ on that warning dialog, then results are not deleted and the data added.
    [NCR 7229](Fixed 04 December 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • The progress bar in Pre-analysis Dialog is not complete even after the analysis finishes.
    [NCR 7371](Fixed 30 August 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Input of displacement data via the table view gives the rogue warning: “The value in field 12 of record 1 is usually in the range of 2.10078e-312 to 3.18622e-307. Is it OK?”
    [NCR 5401](Fixed 04 December 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Xdisp wrongly gives an error message when the 3DGraphics View and a Ground Movement Curve are viewed at the same time.
    [NCR 7406](Fixed 14 September 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Instead of giving an error message Xdisp crashes if the user tries to analyse a file which has an excavation that refers to an incompletely defined ground movement curve.
    [NCR 7484](Fixed 30 October 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Headers of ground movement curves in the Ground Movement Curves Dialog are misleading for files with curves created in previous versions of the program.
    [NCR 7616](Fixed 20 November 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Pre-Analysis checks are not performed for horizontal ground movement curves.
    [NCR 7618](Fixed 20 November 2012; released in Xdisp 19.3 (SP 1) Build 24)
  • Xdisp may crash when polygonal excavation data is copied and pasted.
    [NCR 7715](Fixed 16 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • In some circumstances Xdisp fails to annotate the Plan View with results when clicked.
    [NCR 7716](Fixed 29 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • In Generic Utilities, while calculating the total tensile strain at a point, only the axial tensile strain reduction factor is used.
    [NCR 7736](Fixed 10 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • Xdisp fails to convert imported displacements or lengths/coordinates to the units chosen in the Units’ Dialog that is presented, on import, when the csv file of displacements does not speciy them directly.
    [NCR 7740](Fixed 10 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • The flag and level in the Excavations’ Dialogs which set “if surface movement curves are selected apply them between surface and x m” are not output in the Tabular Output.
    [NCR 7746](Fixed 16 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • In the Tabular Output (Specific Building Damage), only the specific vertical offset to which the results correspond should be printed rather than the entire list of offsets.
    [NCR 7757](Fixed 18 January 2013; released in Xdisp 19.3 (SP 1) Build 25)
  • Xdisp crashes when analysing an extremely fine meshed grid.
    [NCR 7829](Fixed 19 February 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Xdisp crashes when the user tries to do Generic Building Damage Assessment without any polyline defined.
    [NCR 7831](Fixed 19 February 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Xdisp crashes if a structure’s ‘End Distance Along Line’ value is same as the length of the displacement line associated with it.
    [NCR 8050](Fixed 07 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Line graphs exported via the Building Damage Assessment export function, may, on some hardware configurations, have their x axis label and legends cropped, so be difficult to read.
    [NCR 8079](Fixed 04 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Line graphs showing building displacements plot “Hogging” and “Sagging” labels that would be more easy to read if in line with the “Seg. n Start” and “Seg. n End” markers.
    [NCR 8080](Fixed 04 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Line graph sub-titles appearing directly above the legend are more difficult to read than directly below the title – as previously.
    [NCR 8081](Fixed 04 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Warnings should be given if a displacement point is below the crown of a tunnel or has a z/z0 of more than 0.8 – if that tunnel uses the Mair et al sub-surface displacement method.
    [NCR 8089](Fixed 06 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • In cases where displacements of ends of the same pipe are of different signs, incorrect flexural strains may be calculated.
    [NCR 8090](Fixed 07 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • START_TABLE and END_TABLE for Polygonal Excavations’ data are not positioned properly when the tabular output is exported to a csv file.
    [NCR 8093](Fixed 07 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Negative values are not considered while calculating the Maximum Displacements printed in the “Generic Utility Damage Results – Maximum Rotation” section of the tabular output.
    [NCR 8094](Fixed 07 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Automatic File backup option is not working in Xdisp.
    [NCR 8103](Fixed 13 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • In the “Generic Utility Damage Results – Maximum Rotation” section of the tabular output, maximum strains are incorrectly calculated.
    [NCR 8113](Fixed 18 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • One of the tables in the tabular output is incorrectly titled “Generic Utility Damage Results – Maximum Rotation”. Instead it should read “Generic Utility Damage Results – Maximum Values”.
    [NCR 8119](Fixed 18 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • In Generic BDA, for a non-zero offset, the first points of transects are not offset. This could lead to erroneous results.
    [NCR 8129](Fixed 21 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • If a displacement point lies at the level of a tunnel’s axis for which the Mair method is used to calculate displacements, Xdisp may incorrectly calculate zero horizontal displacement towards the tunnel.
    [NCR 8131](Fixed 21 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Displacement results in the Tabular Output along the displacement line, perpendicular to the line, and the angle of the line are shown at -1.#IND if a line is vertical.
    [NCR 8132](Fixed 21 June 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • If the results are deleted keeping the table view open, the building damage and utility damage results are still printed.
    [NCR 8144](Fixed 01 July 2013; released in Xdisp 19.3 (SP 1) Build 27)
  • Vertical (z) offsets for DXF imports are being applied to CIRCLEs but not other background DXF entities.
    [NCR 8204](Fixed 17 July 2013; released in Xdisp 19.3 (SP 1) Build 28)
  • When excavation geometries are imported from a DXF file, circular excavations are given a surface level that is 10m above the read-in base height, but polygonal excavations are given a surface level of 10m, irrespective of the level of the base. This is inconsistent.
    [NCR 8205](Fixed 17 July 2013; released in Xdisp 19.3 (SP 1) Build 28)
  • Xdisp takes an unsatisfactorily long time to perform data checks (due to unnecessary checking of displacement point levels vs tunnel crown always, though needed for Mair method only).
    [NCR 8251](Fixed 25 July 2013; released in Xdisp 19.3 (SP 1) Build 28)
  • Xdisp may appear to hang after an analysis has been started, while data checking is carried out and warnings being prepared – particularly if tunnels use the Mair et al method and some displacement data is below the crown of tunnels or gives z/z0 > 0.8.
    [NCR 8311](Fixed 19 August 2013; released in Xdisp 19.3 Build 29)
  • Xdisp should not offer to delete results if background DXF data is deleted via the 3D Graphics View’s context menu.
    [NCR 8333](Fixed 20 September 2013; released in Xdisp 19.3 Build 30)
  • Line contours on the 2D Plan View are all shown in the same colour.
    [NCR 8385](Fixed 19 September 2013; released in Xdisp 19.3 Build 30)
  • Line contours in the Plan View may be irregular in places, appearing to return upon themselves.
    [NCR 8396](Fixed 19 September 2013; released in Xdisp 19.3 Build 30)
  • Line contours may not be visible at all on the 3D Graphics View.
    [NCR 8397](Fixed 19 September 2013; released in Xdisp 19.3 Build 30)
  • The 3D Graphics View may open with the model minimised and distant if its coordinates are far from the origin or those of the input Grid Layout – whose coordinates are incorrectly included in determining the extent of the model.
    [NCR 8398](Fixed 19 September 2013; released in Xdisp 19.3 Build 30)
  • Contoured sub-surface ground movement curve graphs may have their legends repeated.
    [NCR 8399](Fixed 19 September 2013; released in Xdisp 19.3 Build 30)
  • The view of the graph of a sub-surface ground movement curve may open with the graph off screen, giving the impression that the graph has failed to draw, and requires scrolling and panning to bring it to the viewable area if one is aware of this bug.
    [NCR 8400](Fixed 20 September 2013; released in Xdisp 19.3 Build 30)
  • The Plan View may fail to display annotated results’ values when clicking the “Annotate” button and then a position for display on the displacement grid.
    [NCR 8407](Fixed 23 September 2013; released in Xdisp 19.3 Build 30)
  • Horizontal annotated results on the Plan View do not show the resultant value, but the value of displacement in the x direction.
    [NCR 8408](Fixed 23 September 2013; released in Xdisp 19.3 Build 30)
  • Line contour plots on the 3D Graphics View have confusing legends e.g. 10 : 20 mm rather than 10 mm to identify the 10 mm contour.
    [NCR 8409](Fixed 24 September 2013; released in Xdisp 19.3 Build 30)
  • The warning regarding too many contours in the Plan View cannot be cancelled. Instead a valid contour interval must be entered, rather than the current one simply re-applied on cancelling.
    [NCR 8486](Fixed 23 October 2013; released in Xdisp 19.3 Build 31)
  • Exporting CSV contours may ignore user-specified contour intervals.
    [NCR 8487](Fixed 24 October 2013; released in Xdisp 19.3 Build 31)
  • Circular excavations may be plotted in the incorrect location on the Plan View if length units are not metres.
    [NCR 8496](Fixed 21 October 2013; released in Xdisp 19.3 Build 31)
  • If the “Distance of N.A. from Edge of Beam in Tension” is set for a Generic Structure via the Wizard dialog rather than the Table View, then the data will be corrupted on closure of that dialog. Entering the data directly into the Table View is safe.
    [NCR 8497](Fixed 21 October 2013; released in Xdisp 19.3 Build 31)
  • Transect coordinates in the tabular output are displayed in SI units rather than in the user specified units.
    [NCR 8499](Fixed 22 October 2013; released in Xdisp 19.3 Build 31)
  • Polygonal excavations do not allow negative coordinates.
    [NCR 8501](Fixed 22 October 2013; released in Xdisp 19.3 Build 31)
  • Xdisp doesn’t throw any warning if the offset field of Generic Buildings is left empty.
    [NCR 8595](Fixed 12 March 2014; released in Xdisp 19.3 Build 32)
  • “StandardDimensionsAndCriteria.xdd” sample file’s name is misleading. It should be named “SampleDimensionsAndCriteria.xdd” instead.
    [NCR 8821](Fixed 06 March 2014; released in Xdisp 19.3 Build 32)
  • Xdisp uses a rogue z-displacement value of -0.001mm for the cases where it is zero.
    [NCR 8871](Fixed 20 March 2014; released in Xdisp 19.3 Build 32)
  • Xdisp does not consider imported displacements in assessing the damage of utilities (specific and geenric) and generic buildings.
    [NCR 9104](Fixed 24 June 2014; released in Xdisp 19.3 Build 33)
  • Utility’s axial strain calculation is not accurate.
    [NCR 9130](Fixed 24 June 2014; released in Xdisp 19.3 Build 33)
  • Displacement results’ section shows either no name or wrong name against a vertical line.
    [NCR 9340](Fixed 14 Nov 2014; released in Xdisp 19.3 Build 34)
  • In the plan view, “Combined strain vs Distance” graphs of a specific utility are wrong for the cases where axial strain reduction factors input for compression and tension are different.
    [NCR 9604](Fixed 14 Nov 2014; released in Xdisp 19.3 Build 34)
  • The titles in tabular output, “Along the Line” and “Perpendicular to the Line” should be modified to “Horizontal displacement along the line” and “Horizontal displacement perpendicular to the line” respectively.
    [NCR 9663](Fixed 01 December 2014; released in Xdisp 19.3 Build 35)
  • Xdisp allows 3D graphical input even when the analysis is in progress.
    [XDISP-10](Fixed 21 April 2015; released in Xdisp 19.3 Build 35)
  • Warning related to irregularly shaped excavations should be altered in the help file.
    [XDISP-11](Fixed 21 April 2015; released in Xdisp 19.3 Build 35)
  • Help file wrongly mentions that the Volume loss for inclined tunnels should be divided by the angle. It should be divided by the cosine of the angle.
    [XDISP-12](Fixed 21 April 2015; released in Xdisp 19.3 Build 35)
  • Wrong ‘d’ values of corner stiffening are shown in the tabular output.
    [XDISP-13](Fixed 21 April 2015; released in Xdisp 19.3 Build 35)
  • Vertical offsets are always shown in SI units in the tabular output.
    [XDISP-14](Fixed 21 April 2015; released in Xdisp 19.3 Build 35)
  • Building Damage Interaction chart’s title text doesn’t get updated when the units are changed. The user has to close and re-open the graph to see the updated text.
    [XDISP-15](Fixed 22 April 2015; released in Xdisp 19.3 Build 35)
  • X-axis title text of ‘Generic Building – Maximum tensile strain graph’ shows SI unit even though the user has specified a different unit system.The user has to close and re-open the graph to see the updated text.
    [XDISP-16](Fixed 22 April 2015; released in Xdisp 19.3 Build 35)
  • Displacements’ graph doesn’t get updated when the unit system is changed. The user has to close and re-open the graph to see the update.
    [XDISP-17](Fixed 22 April 2015; released in Xdisp 19.3 Build 35)
  • Titles in the graphs of specific and generic utilities don’t get updated when the units are changed. The user has to close and re-open the graphs to see the update.
    [XDISP-18](Fixed 22 April 2015; released in Xdisp 19.3 Build 35)
  • Radius of curvature value is always reported in SI units, though the header reports the user-selected unit.
    [XDISP-19](Fixed 22 April 2015; released in Xdisp 19.3 Build 35)
  • Rebuild with revised security library.
    (Fixed 21 September 2015; released in Xdisp 19.3 Build 38)
  • Xdisp may miscalculate deflection ratios, and therefore building damage categories, for segments which experience heave (-ve vertical displacement in the z direction).
    [NCR XDISP-33](Fixed 2 December 2015; released in Xdisp 19.3 Build 44)
  • Xdisp may incorrectly calculate zero horizontal ground movement if a displacement point is at the level of the tunnel axis, even though close to an excavation.
    [NCR XDISP-35](Fixed 22 January 2016; released in Xdisp 19.3 Build 48)
  • If the linear interpolation curve fitting method is used with surface movement curves, then the graph of the curve, and ground movement results, may be incorrect.
    [NCR XDISP-45](Fixed 15 April 2016; released in Xdisp 19.3 Build 49)
  • Excavation geometry error checking unnecessarily prohibits an excavation from having 2 coordinates at the same point.
    [NCR XDISP-47](Fixed 15 April 2016; released in Xdisp 19.3 Build 49)
  • Xdisp may crash if an excavation is entered with duplicate coordinates at neighbouring points on the excavation’s perimeter (e.g. to model a stepped base, using the same coordinate with 2 base levels).
    [NCR XDISP-49](Fixed 21 April 2016; released in Xdisp 19.3 Build 49)

New Features

Xdisp 19.2: New Features

  • Excavation corner stiffening
  • Circular excavations
  • Side-specific excavation ground movement curves
  • View positioning via e.g. Ctrl + Num 1 for bottom left

Xdisp 19.2: Minor Enhancements

  • Elements in the 3D Graphics View may now be labelled.
    [ME4522](Added 9 Mar 2010; released in Xdisp 19.2 Build 9)
  • Xdisp now enables the 3D Graphics View to be printed with a calculation sheet’s header and border.
    [ME4559](Added 8 Mar 2010; released in Xdisp 19.2 Build 9)
  • Improvement to lighting in the 3D Graphics View.
    [ME4870](Added 15 June 2010; released in Xdisp 19.2 Build 9)
  • Implementation of ‘ghost’ image in the 3D Graphics View when rotating a model with many elements.
    [ME4875](Added 16 June 2010; released in Xdisp 19.2 Build 9)
  • Implementation of ‘x view’, ‘y view’, ‘z view’ orientations for the 3D Graphics View.
    [ME4876](Added 17 June 2010; released in Xdisp 19.2 Build 9)

Fixes

  • Copy and paste from one row to another in the Structures� table or in the Displacement Data table may not always work, particularly in long tables.
    [NCR 4521](Fixed 9 March 2010; released in Xdisp 19.2 Build 9)
  • The 3D Graphics view doesn’t have a resource (menu), instead it takes that of the last opened view.
    [NCR 4703](Fixed 17 June 2010; released in Xdisp 19.2 Build 9)
  • Toggle “perspective/orthographic” is working only when the 3D Graphics view is re-sized.
    [NCR 4707](Fixed 3 May 2010; released in Xdisp 19.2 Build 9)
  • “Custom” type of centre of rotation does not work in 3D Graphics.
    [NCR 4715](Fixed 4 May 2010; released in Xdisp 19.2 Build 9)
  • Xdisp takes a long time to plot “Horizontal displacement” on the plan view.
    [NCR 4759](Fixed 11 May 2010; released in Xdisp 19.2 Build 9)
  • Xdisp outputs CSV contour data for all grids, even though only one is seleted for export.
    [NCR 4853](Fixed 10 June 2010; released in Xdisp 19.2 Build 9)
  • Xdisp may incorrectly warn that excavations overlap when an analysis is performed.
    [NCR 4950](Fixed 9 July 2010; released in Xdisp 19.2 Build 9)
  • Xdisp fails to export CSV results when a displacement grid’s extrusion depth is negative.
    [NCR 4181](Fixed 10 August 2010; released in Xdisp 19.2 Build 9)
  • The 2D Plan View fails to show contour plots for displacement grids which have negative extrusion directions.
    [NCR 5041](Fixed 10 August 2010; released in Xdisp 19.2 Build 9)
  • The help manual should include a description of how the sample sub-surface movement curve was generated.
    [NCR 4250](Fixed 11 August 2010; released in Xdisp 19.2 Build 9)
  • The Building Damage Interaction chart’s legend may truncate the category of building damage under the Maximum Tensile Strain item.
    [NCR 4415](Fixed 11 August 2010; released in Xdisp 19.2 Build 9)
  • Though “Mair et al” is chosen as a sub-surface analysis method, the analysis warnings and Output View may suggest the soil type has been set to “granular” incorrectly. However, the results are unaffected.
    [NCR 4819](Fixed 12 August 2010; released in Xdisp 19.2 Build 9)
  • Changes made to an excavation’s Surface Level and Contribution are not reflected if the coordinates’ table is modified.
    [NCR 4830](Fixed 12 August 2010; released in Xdisp 19.2 Build 9)
  • Xdisp may crash while renaming a ground movement curve if the cancel button is clicked during the renaming process.
    [NCR 4846](Fixed 13 August 2010; released in Xdisp 19.2 Build 9)
  • Xdisp does not plot contours for grids that have been extruded in the Global_X direction.
    [NCR 4205](Fixed 13 August 2010; released in Xdisp 19.2 Build 9)
  • Xdisp may crash while checking for warnings before beginning analysis if overlapping excavations are defined.
    [NCR 5443](Fixed 25 November 2010; released in Xdisp 19.2 Build 10)
  • Xdisp may fail to read Polygonal Excavations correctly from saved Xdisp data files – when those excavations were originally created by import from a DXF file, and when the polyline that describes the excavation has coincident start and end points. This may subsequently cause the program to crash when opening the Polygonal Excavations input view.
    [NCR 6154](Fixed 23 June 2011; released in Xdisp 19.2 Build 12)
  • The Input Data Wizard is not accessible from the Buildings Table View. When attempting access the program warns “Attempted an unsupported operation.”
    [NCR 5071](Fixed 28 May 2010; released in Xdisp 19.2 Build 13)
  • Xdisp may warn the user, in the Circular Excavation input dialog when changing the height of the surface, that an excavation’s surface level is below its base when this is not the case.
    [NCR 5355](Fixed 18 November 2010; released in Xdisp 19.2 Build 13)
  • The Volume Loss column of the Tunnels Table View may show a “k Derivation” drop list instead, when in the “Analysis Parameters” tab. The data is displayed correctly, and can be edited, by viewing it in the “All Tunnel Data” tab.
    [NCR 5660](Fixed 1 February 2011; released in Xdisp 19.2 Build 13)
  • Xdisp may crash performing building damage assessment on buildings whose lengths are very close to the lengths of the displacement lines to which they refer.
    [NCR 5863](Fixed 30 March 2011; released in Xdisp 19.2 Build 13)
  • Data that is copied into the tunnels TableData that is copied into the tunnels Table View may be displayed incorrectly in the Analysis Parameters tab. e.g. the Ground Loss column has show a k Derivation choice, and the k Derivation column may show a k value.
    [NCR 6208](Fixed 14 July 2011; released in Xdisp 19.2 Build 13)
  • Xdisp may crash when the last Circular Excavation is deleted in the Circular Excavations view and the “Apply” button clicked.
    [NCR 6209](Fixed 14 July 2011; released in Xdisp 19.2 Build 13)
  • File | Export | Building Damage Assessment Data… crashes Xdisp when run on Windows 7.
    [NCR 6261](Fixed 5 August 2011; released in Xdisp 19.2 Build 14)
  • The manual describes Boscardin’s k derivation formula incorrectly as “i = 0.5 z0 + 0.25 metres” and “i = 0.24z0 + 0.5 metres” for cohesive and granular soils respectively, rather than “i = 0.5z0” and “i = 0.25z0“.
    [NCR 6272](Fixed 15 August 2011; released in Xdisp 19.2 Build 15)
  • If the Mair method is selected then no ground movements are calculated below the centre-line of the tunnel.
    [NCR 6275](Fixed 18 August 2011; released in Xdisp 19.2 Build 15)
  • Xdisp may crash in Windows 7 when performing DXF import.
    [NCR 6287](Fixed 25 August 2011; released in Xdisp 19.2 Build 16)
  • Xdisp fails to import displacement results for grids or lines from csv files.
    [NCR 5221](Fixed 11 October 2010; released in Xdisp 19.2 Build 17)
  • Xdisp may fail to import some displacements that have been exported from Pdisp 19.2 Build 3.
    [NCR 6367](Fixed 19 Sep 2011; released in Xdisp 19.2 Build 17)
  • The help manual should be more explicit that the source of the O’Reilly and New formula of i = 0.28z – 0.12 for granular soils is Figure 4 of O’Reilly and New’s paper as opposed to the text, which shows a less precise Equation 13 of i = 0.28z – 0.1.
    [NCR 6485](Fixed 10 Nov 2011; released in Xdisp 19.2 Build 18)
  • The default values for excavation corner stiffening parameters p1* and p2* would more sensibly be 67 and 25 respectively, rather than 100 and 50.
    [NCR 6486](Fixed 10 Nov 2011; released in Xdisp 19.2 Build 18)
  • The surface movement curves’ dialog’s “Apply” button is not activated when the type of curve fit is changed from “Polynomial” to “Linear”.
    [NCR 6488](Fixed 14 Nov 2011; released in Xdisp 19.2 Build 18)
  • Xdisp does not allow files to be opened by dragging them from Windows Explorer over the open program interface.
    [NCR 6483](Fixed 7 Nov 2011; released in Xdisp 19.2 Build 18)
  • Surface movement curve listings in the Tabular Output always show a polynomial equation, even when “Linear” curve fitting has been selected..
    [NCR 6490](Fixed 14 Nov 2011; released in Xdisp 19.2 Build 18)
  • When zooming into Xdisp’s Plan View, the axes’ labels may show insufficient significant figures e.g. all “177600.”
    [NCR 6494](Fixed 17 Nov 2011; released in Xdisp 19.2 Build 18)
  • Line graphs may ‘squash’ legend and title text vertically when displays are set to low resolutions, so lines may partially overlay eachother.
    [NCR 6582](Fixed 12 Dec 2011; released in Xdisp 19.2 Build 18)
  • The Mair et al method should calculate zero soil movement for displacement points below the invert of a tunnel.
    [NCR 6495](Fixed 5 Dec 2011; released in Xdisp 19.2 Build 18)
  • If the New and Bowers method is chosen for sub-surface ground movements, then only “User-defined k” should be offered as the k derivation method and not O’Reilly and New or Boscardin.
    [NCR 6497](Fixed 6 Dec 2011; released in Xdisp 19.2 Build 18)
  • Xdisp may crash when a building’s displacement graph is queried if the displacements are all less than the sensitivity limit.
    [NCR 6451](Fixed 12 Dec 2012; released in Xdisp 19.2 Build 18)
  • Building Damage Assessment export fails if file names contain trailing spaces.
    [NCR 6575](Fixed 7 Dec 2011; released in Xdisp 19.2 Build 18)
  • Xdisp crashes in Windows 7 if the DXF import dialog is cancelled.
    [NCR 6047](Fixed 17 May 2011; released in Xdisp 19.2 Build 18)
  • Surface movement curve listings in the Tabular Output always show a polynomial equation, even when “Linear” curve fitting has been selected.
    [NCR 6490](Fixed 14 November 2011; released in Xdisp 19.2 Build 18)

New Features

Xdisp 19.1: New Features

  • Import of displacement results from CSV
  • “One click” export of building damage assessment results’ tables and graphs
  • Extension of building damage interaction chart to compressive strains
  • Implementation of Harris and Alvarado tunnel method
  • Taylor adjustments to Mair et al tunnel method

Xdisp 19.1: Minor Enhancements

  • If two or more imported displacement lines start at the same point, Xdisp would only import the displacement at that point for the first line. Xdisp now: (1) collects all the imported displacements from the file and at the time of analysis checks for coincident points; (2) assumes results are entered in the import data file with tag POINT_RESULT instead of entering grid, line and point results with separate tags (GPOINT_RESULT, LPOINT_RESULT, POINT_RESULT); (3) sums all imported displacements with the value calculated by Xdisp, when there are multiple entries of displacements at a point in the import file; and (4) adds imported displacements to the values calculated by Xdisp for all the points in the model with coincident co-ordinates (irrespective of type of data i.e grid, line or point.)
    [ME4481](Added 15 Feb 2010; released in Xdisp 19.1 Build 13)
  • Added horizontal displacements resolved along the building line to the export of building damage assessment data.
    [ME4495](Added 15 Feb 2010; released in Xdisp 19.1 Build 13)
  • Warning given if sub-structure crosses an excavation since building damage results in that portion should be treated with caution.
    [ME4499](Added 16 Feb 2010; released in Xdisp 19.1 Build 13)
  • Displacement lines report, in the Tabular Output: “Displacement Parallel to Line”; “Displacement Perpendicular to Line”; and “Angle of Line to Global Axis”.
    [ME4500](Added 16 Feb 2010; released in Xdisp 19.1 Build 13)
  • Xdisp modified to use the displaced horizontal distances when calculating points of inflexion and therefore segment lengths for building damage calculations. The program previously used un-strained horizontal distances when determining points of inflexion. The tabular output reports segment lengths according to their pre-strained situations. This change will be insignificant in the vast majority of cases.
    [ME4501](Added 16 Feb 2010; released in Xdisp 19.1 Build 13)

Fixes

  • Xdisp may fail to import displacement data correctly. Displacement data whose coordinates should match those in the data file may be omitted.
    [NCR 4383](Fixed 18 Dec 2009; released in Xdisp 19.1 Build 10)
  • Unnecessarily double-spaced lines of data appear in the Tabular Output’s table of “Building Damage Results – Critical Values for All Segments within Each Sub-Structure”.
    [NCR 4401](Fixed 5 Jan 2010; released in Xdisp 19.1 Build 11)
  • Upon clicking a coordinate in the Displacement Data table view the coordinate displays itself to more decimal places than have been entered by the user.
    [NCR 4402](Fixed 5 Jan 2010; released in Xdisp 19.1 Build 11)
  • Exported Building Damage Results may be misleading if horizontal strain for a sub-structure’s segment is in compression. Maximum combined tensile strains (total bending, total diagonal and max.) do not consider the compressive horizontal strain value.
    [NCR 4403](Fixed 6 Jan 2010; released in Xdisp 19.1 Build 11)
  • The Tunnels Table View will not allow “granular” soil to be set. On setting it and closing the view, the soil reverts to “cohesive”.
    [NCR 4450](Fixed 2 Feb 2010; released in Xdisp 19.1 Build 13)
  • If the O’Reilly and New sub-surface k deriviation method is chosen, then Xdisp incorrectly sets i using the user-specified k value, irrespective of whether the user-defined option has been set. It should use that k value if user-defined is set, but should otherwise derive k from the i value according the O’Reilly and New derivation formula.
    [NCR 4452](Fixed 2 Feb 2010; released in Xdisp 19.1 Build 13)
  • Xdisp may incorrectly calculate and report displacements within excavations where those displacements arise from tunnelling, but correctly does not allow them from excavations.
    [NCR 4498](Fixed 16 Feb 2010; released in Xdisp 19.1 Build 13)
  • Xdisp crashes when the number of intervals along a displacement line is zero.
    [NCR 4435](Fixed 9 Feb 2010; released in Xdisp 19.1 Build 13)
  • “Sagging” and “Hogging” labels sometimes not clearly visible on the line graph of sub-structure displacements.
    [NCR 4480](Fixed 12 Feb 2010; released in Xdisp 19.1 Build 13)
  • The displacements that are reported in the Tabular Output as perpendicular to displacement lines may show the wrong sign.
    [NCR 4485](Fixed 18 Mar 2010; released in Xdisp 19.1 Build 14)
  • The program may crash while performing analysis including building damage assessment.
    [NCR 4648](Fixed 15 Apr 2010; released in Xdisp 19.1 Build 15)
  • Displacement point coordinates are converted to scientific if their values are too long for their column in the Tabular Output. Grids which are made up of points whose values are large, but differ by small increments, may be listed with indistinguishable point values.
    [NCR 4649](Fixed 15 Apr 2010; released in Xdisp 19.1 Build 15)
  • Xdisp may give the warning ‘encountered invalid argument’ and crash, when the Tabular Output is opened when line results are not listed as the first displacement data items, i.e. before grids and points.
    [NCR 4656](Fixed 16 Apr 2010; released in Xdisp 19.1 Build 15)
  • Exporting displacement contours to CSV may fail unexpectedly (though the contours can be viewed in the Plan or 3D Graphics View) with the warning “The specified contour interval is inappropriate for Grid n and X/Y/Z/Resultant Direction. Contours will not be output for that combination.”.
    [NCR 4658](Fixed 20 Apr 2010; released in Xdisp 19.1 Build 15)

Require more information?

  • This field is for validation purposes and should be left unchanged.

Newsletter Sign up

Please fill out your details below to receive the latest oasys news.
  • This field is for validation purposes and should be left unchanged.