Terms & Conditions

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.

All data is stored in secure electronic systems accessible only to Oasys staff with both valid network login credentials and specific authorisation to access the system.  Our systems further limit data access by role to ensure data is available only to those who have a specific need to see it.

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 [email protected] or in writing to Oasys, 8 Fitzroy Street, London, UK, W1T 4BJ as soon as possible.

Data Security Notice Updated 27th February 2020

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 desktop software are set out in the Oasys Software Licence and Support Agreement.

The full conditions of purchase and maintenance for Oasys Gofer and Oasys Giraphe are set out in the Gofer SaaS Agreement  and the Giraphe SaaS 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

Support and maintenance is included with all subscription licences for their full duration.

Annual maintenance contracts are available for software under a perpetual licence, prices are based on a percentage of the most recent list price.

This service includes:


top ]



Cookies Policies

View available cookies policies below:


top ]


MassMotion 9.5 introduces usability improvements and a new tool for sharing simulation results to stakeholders and clients

MassMotion and MassMotion Flow version 9.5 released

MassMotion Viewer

The headline new addition in the MassMotion v.9.5 release is a powerful viewer application for sharing MassMotion results. Free to download, the MassMotion Viewer can be installed on any computer running Windows 7 or 10, and used with Oculus Rift. It will open any MassMotion or Flow results file and display a playback of a previously recorded simulation. Opening and running an animation is straightforward and requires no prior knowledge of pedestrian simulation software. For an immersive experience for the end user or client, an Oculus Rift can be used alongside your computer.

The Viewer gives complete control of what the recipient sees, avoiding any unwanted misunderstandings. If you wanted to breakdown what the viewer would see even further, you can export simulation ‘slices’ from MassMotion or Flow.  Slices are a subset of a simulation database file and can drastically reduce file size by keeping only the segment of a result set that would be useful when communicating results with stakeholders and third-parties.

Download the MassMotion Viewer from its product page


Storing and recalling viewpoints within scenes is made easier with new bookmark objects that replace the saved view feature of earlier releases. The new bookmarks can control viewpoint, simulation time, object visibility, and view settings. They can be imported/exported just like any other object making it easy to share viewpoints between projects and users, ensuring consistency.

Customised Journey Scheduling

Defining crowds, agent counts and agent journeys has been improved with new OD based options for specific journeys, normal circulation and evacuation. Specify agent counts by origin and/or destination within the model, and take advantage of greater control over the rates and times at which agents are created. Existing MassMotion projects that used the Trip Matrix are automatically upgraded to use this new feature with equivalent settings.

Improved BIM Functionality and Visualisations

MassMotion 9.5 can now export geometry suitable for use in other 3D packages. New in-built tools have also been implemented for fixing any anomalies in legacy projects from older MassMotion versions.

Oasys has a track record of releasing new features as quickly as possible, and MassMotion 9.5 comes close on the heels of MassMotion 9.0 which broke new ground by making it remarkably quick and easy to create a 3D model by combining existing 2D and 3D CAD files and adding objects using snap tools. Oasys introduced even smarter agents and gave users more scope to test new scenarios and events on MassMotion’s ever-more-realistic crowds.

Oasys commercial manager Nigel Rees said: “We know from user group feedback that engineers are using MassMotion tools to dig deeper into the way people will respond to design features; and that the sheer power and speed of MassMotion analysis gives them the freedom to experiment with more variables. It just makes sense for them to be able to bookmark, export and share insights with everyone on the project team.”

A full list of changes can be found in the change log.


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.