Terms & Conditions


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


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

MassMotion FAQs

Find the answer to frequently asked questions from existing users.

Most popular FAQs

MassMotion uses Windows Media technology for generating videos and images. On some versions of Windows (N/KN) the Windows Media Feature Pack may need to be downloaded and installed separately.

The links below were updated as of 20th April 2018.

Media Feature Pack for N versions of Windows 10


Media Feature Pack for N versions of Windows 8.1


Media Feature Pack for N versions of Windows 8


Media Feature Pack for Windows 7 N or KN with Service Pack 1


MassMotion is supplied with a number of sample files, which you will find under the installation directory (the default being C:\Program Files\Oasys\MassMotion xxx\Samples).

As users without Admin rights cannot edit anything in the Program Files folders, and bearing in mind that any software updates will overwrite the files anyway, you are best off copying the Samples folder to a suitable location elsewhere on your local drive. Then to run a simulation, open up the model file (*.mm) with MassMotion or Flow, then edit the Project Settings so that the results folder is the same as the new model directory. You will then be able to simulate and analyse the models as normal.

The sample models include the following:


A small shopping centre, where agents enter the mall, visit between 1 and 3 shops then leave.


Emergency evacuation of the same shopping centre


This folder contains both an example small airport and an IFC file containing the model geometry.


A simple journey model to demonstrate how barriers do and do not interact with floors


A sample elevator controlled by two Gate events, allowing the agents to use the Paths within the lift enclosure


A small train station controlled by a MassMotion Timetable, as per the example in the help file


Three streets with pedestrian crossings. Note that there are regular MassMotion objects in here which are hidden and visualization objects that are not, and have been imported with bitmaps on the surfaces. Note that to see the agents you will need to switch off the default graphical window option of hiding agents on hidden floors.


This is a model of a subway station interchanging with buses at the road level.

Follow these steps to create a single MassMotion object from multiple pieces of reference geometry:

  1. Select the relevant unused imports / reference geometry
  2. Change to Face Selection mode (Y)
  3. Pick the required faces to convert
    • Tip: use CTRL or SHIFT + click to select rather than a drag window as you might not want to convert the faces underneath
  4. Right click on them and select Use To Generateand the appropriate object type
    • Note that you may need to adjust the final result if a stair, ramp, or escalator as this method will not automatically create the “landing” areas

If you want to combine MassMotion objects together then do the following:

  1. Select the relevant geometry objects
  2. Change to Face Selection mode (Y)
  3. Pick the required faces to convert
  4. Right click on them and select Extract Asand the appropriate object type
    • If you have selected all the faces in any object then you will be asked whether you want to delete the originals
    • To keep the original objects use Duplicate As or Use To Generate

MassMotion is now independent of Softimage. Follow the following steps to work on the models in the latest version.

  1. Open the model (*.emdl) using the MassMotion 7.0 workbench in Softimage
  2. On the Simulation tab, validate and export all data. This will create a Project.mmxsi file in the project directory
  3. Open Project.mmxsi using your latest version of MassMotion or Flow
  4. Filter the object list with “workbench”. Select all the resulting items, right click and open the properties. Click [Convert Workbench Object(s)]
  5. Save the model in the new model format

The IFC import into MassMotion has the advantage that the incoming geometry is automatically categorised into the appropriate type: floor, link, stair, etc. It can do this because the IFC file format includes both geometric data and the metadata from the original model. For example, in a CAD model you would just draw a slab outline with lines, but in a building model the slab object includes properties such as thickness, material type, finishes, and so on. The IFC format preserves this data and MassMotion uses it to map the object types in accordance with the import dialog.

There are three other major factors to consider during the import: orientation, scale, and location.


MassMotion uses the same axis set as Autodesk’s Softimage, in which the Z axis is horizontal (screen depth) and the Y axis is in the vertical direction. Most CAD and building models, on the other hand, have the Z axis vertical. This means that the axes need swapping during the import. To do this set the appropriate selection on the second tab of the import wizard.


CAD and building models can be in any units you choose; MassMotion models are always in metres. This means that the import must convert any coordinates appropriately if your resulting model is to be the right size. The import should automatically detect the units from the IFC file, but if this does not work then you would need to either do a units conversion on export to metres if your originating program allows, or set the original units in the import wizard just like importing from a regular CAD file.


While CAD and building modelling programs are happy at working in large coordinates, analysis programs like MassMotion are not. Thus if your original model is located by a national scale coordinate system, you need to move the geometry to the origin either on export or import. The MassMotion import option allows you to define the point in the original model that will become 0,0,0 in the new, but changing this in Revit tends to give a better result. Note that this coordinate is in both the original units and axis orientation.

Other tips


Generally the resulting MassMotion model floors will be in one of two basic forms depending on how the building model was defined or exported.

One option is to export the physical slabs and walls, which will result in one large floor per storey divided by barriers. This will also mean that any doors will generally not translate correctly as links as they will only be on one floor; this is nothing to worry about as they are not needed in this case. The downside to this option is that the agents will not be aware of route choices across this floor and only go the shortest route regardless of congestion. You might find it necessary to add some divisions in the floors after import.

The second (and recommended) option is to export the rooms (or spaces), meaning that each will create a separate floor. Doors will now link these floors and give the agents the full route finding options.

Note that it is not recommended to convert both slabs and spaces as floors because this will likely lead to duplicate/overlapping floors. If you have both IfcSpace and IfcFloor objects, convert the IfcSpace by preference as this will enable the IfcDoor / Links to work


Partition walls are often modelled finished floor to the underside of the slab above, but a wall touching the underside of the floor geometry will still register as a barrier. This means that you may need to edit the walls after import to ensure that there is a gap between the wall tops and the underside of the floor. Check the obstruction and approach maps if you are not sure whether this affects your model.

Stairs and Escalators

Revit currently does not export escalators and some stair types to IFC. One option is to make a copy of the Revit model, change all the escalators to stairs, export that, then reset them back in MassMotion. This may apply to other building model programs. Another option is to select the imported escalator/stair object, then select relevant polygons and use those to generate the escalator/stair.


Unless you have created some custom objects in Revit (other building models are available) you will need to add portals, paths, and servers manually in MassMotion

When updating the MassMotion model after the inevitable changes to the original model, either delete all the imported geometry and reimport, or just the changes (if you know what they are).

All FAQs

The MassMotion SDK allows you to programmatically run simulations and interact with them as they run. You can

  • request that new agents be created
  • take direct control over existing agents
  • dynamically give or remove agent tasks

to achieve complex behaviours that would not otherwise be possible.

The SDK is available for C++, Python, C# and Java in one installable package.

Note that the SDK build must match the MassMotion build and will not function with MassMotion Flow.

See the SDK help file for full details.

The primary model and scenarios are stored in the .mm file. This information is also in the .mmdb result file along with the frame-by-frame agent simulation results. This means that you can open the .mmdb file directly to see both the geometry and simulation.

For this to work correctly you need to open the file with exactly the same build of MassMotion as was used to create the simulation run. If you use a more recent version then you will be able to see the geometry but no simulation. In this case save the model as a new .mm file, set the project path, and rerun the simulation.

MassMotion and Flow are high performance 64bit multi-threaded applications that are capable of effectively utilizing very high specification equipment. It is particularly important when running simulations that have very high concurrent agent counts (25,000+) that CPU core counts are maximised for processing speed and that solid state storage is provided for efficient database transactions. GPU performance is important for highly detailed 3D environments and for 3D playback of high agent count environments.


MassMotion and Flow use Windows Media technology for generating videos and images. On some versions of Windows (N/KN) the Windows Media Feature Pack may need to be downloaded and installed separately.


Recommended Minimum Specification:

  • Windows 64bit OS (Windows 7 & later)
  • 8-core Intel or AMD workstation/server class CPU
  • 16GB of RAM
  • OpenGL 4 workstation GPU from NVIDIA or AMD
  • 500GB Solid State Hard Drive
  • 2 1680×1050 display monitors
  • 3-button mouse


Minimum Specification:

  • Windows 64bit OS (Windows 7 & later)
  • Dual-core Intel or AMD workstation/server class CPU
  • 4GB of RAM
  • OpenGL 3.0 compatible GPU
  • 500GB Hard Drive
  • 1280×1024 display monitor
  • 3-button mouse

Travelators, or moving walkways, need to be modelled as horizontal escalators. As these need to span between floors, break the floor under the escalators and add Links to accommodate those agents who prefer to walk.

As the typical speeds of travelators is lower than the typical agent walking speed, they will tend to route around them by default. You can encourage agents onto travelators by adding a negative distance to make them more attractive, or adjust the tread speed to represent the split between standing and walking pedestrians.

You need to either include barriers under stairs, ramps, and escalators to stop agents walking though those areas. The quick way to do this is to

  1. select the stair (etc)
  2. change to Edge selection and select the edge where the stair meets the lower floor
  3. Grow this edge to create polygons under the stair
  4. change to polYgon selection and select the new faces
  5. right click and extract them as Barriers

Timetables in MassMotion are powerful, but also complex. They interrelate in the following manner:

MassMotion timetable files

Note that timetables are case-sensitive, so please ensure that you get the capital letters right.

Please refere to the help file for the details of the timetable files and some examples. You will also find an example file installed in the program folder C:\Program Files\Oasys\MassMotion X.X\Examples

A – show All model

S – camera navigation (Scene)

F – Focus 3D view on selection

Ctrl-A – select All in 3D View

Ctrl-D – Duplicate selected objects

Ctrl-Z – Undo

Ctrl-Y – Redo

Ctrl-S – Save

E – Edge select

T – vertex select (poinT)

Y – face select (polYgon)

Space – object select

K – Knife tool (for adding edges / dividing polygons)

M – Measuring tool

X – scale

C – rotate

V – translate

G – grow (translate)

Esc – cancel, clear selection, return to object select

Up-Arrow – playback from current time

Down-Arrow – pause at current time

Left-Arrow – step back one frame

Right-Arrow – step forward one frame


Softimage keyboard shortcuts

8 – scene explorer

[ – knife tool

Ensure that the Floor is split along the line of the array

Represent each ticket gate with a Link and the machinery with Barriers to ensure that the agents do not approach from the side

Set the Link to “Ignore Barriers” to ease the Agent’s movements if the gates are narrow (i.e. close to 500 mm wide)

Model the Link such that the goal line is in line with the edge of the Barriers to aid the Agents wayfinding

If the gate is for one direction only set the properties to Unidirectional

If the gate is two way set Priority Flow with the priority appropriately

Set a contact delay to represent the time taken to swipe or insert tickets

Bank the Links to ensure full saturation of the gates

To reduce “flip-flop” behaviour at the back of the queues set the Link queuing cost to a low value

Use Tokens to ensure that certain agents use either narrow or wide gate gates. There are two ways to achieve this:

  1. give most Agents an “AnyGate” Token; gate the regular Links; create an event that opens the gates at the start of the simulation for Agents carrying the “AnyGate” token
  2. give some agents a “WideGate” Token; create an Action that is applied to the Agents as they enter the Floor that tests for possession of that Token; this Action should give those Agents a Route command to use the wide gates
There are a number of reasons why your avatars may be invisible, depending on where you expect to see them.


  • Install the latest build of MassMotion


  • Check that the activity colour properties does not have the alpha channel set to 0)
  • Is the floor hidden and the ‘Hide Agents on Hidden Floors’ option selected in the view options
  • Update the graphics card driver (note that Windows Update and Device manager may incorrectly indicate that the driver is up to date – check for a more recent version on the graphics card manufacture’s website). This is the likely cause if your agents are invisible in the main window but show during a Debug simulation run.

Simulation Run

  • Is the Simulation Run hidden?
  • Does the Simulation Run have an agent filter that excludes all agents?
  • Is the Agent Colour set to one with a zero Alpha Channel?

Softimage workbench

  • In the simulation playback check that the ‘Execution > Display Type’ is set to’ Show All Agents’ and not filtered
  • Likewise in the simulation playback Appearance the Type is set correctly and that if you have changed the Agent Avatars to ‘Random – Subset of Avatars’ that the subset is not empty.
  • Try resetting the default Avatars using the menu command ‘MassMotion > File > Reset Default Avatars’. Note that if you do this then you only need to re-export from the Softimage workbench and do not need to re-run the simulation.
  • Ensure that the Avatars’ display is not set to ‘Hide’

When creating models in SketchUp for MassMotion, one thing you do need to be careful of is SketchUp’s helpful habit of joining any lines or surfaces that cross, because MassMotion needs them to be kept separate. To ensure that the model does not import as one big lump you need to group every object as soon as you have drawn it. This is a simple operation as you just double click on the surface to select it and the bounding lines, then right click and select Make Group. You can see your progress in the Outliner dialog.

If you need to edit anything in a group, you can double click on it to enable editing; double click somewhere else on the screen to return to the normal view. If necessary, you can also explode a group back to normal SketchUp elements.

While you can name these groups, the names are not carried through into MassMotion and thus only name them if you find it useful within the SketchUp environment. Likewise colours and materials are normally left behind.

Most SketchUp templates include a figure. It can be useful to leave them in the model when exporting to MassMotion as they will appear next to the MassMotion avatars, giving you an instant check that the scaling between the two programs is correct.

For complex models, you may find it helpful to use SketchUp’s layering, as this will make it easier to export the floors, links, etc. into separate files for easier categorisation in MassMotion.


There are several file formats available for the export, but I find that the .fbx and .ifc formats work well. FBX caries just the geometry information, while IFC also contains metadata saying what type of objects the graphics represent. To use IFC you need to apply IFC properties to the objects, which will make the subsequent generation of MassMotion objects easier following import. Do this, select the grouped object and in the Tray > Entity Info set the Type. If no categories are currently included in the model the Model Info > Classifications dialog will open. Click Import and choose IFC 2×3.skc. Close the Model Info dialog and select the desired IFC type. See the help file Reference > User Interface > Generating Objects from Geometry > Generating from IFC for the list of IFC types that MassMotion recognises.

It is important to set the following export options:

  • units = metres (MassMotion only uses metres and this will scale the SketchUp units)
  • swap axes, Y is up (SketchUp has the X and Y axes horizontal while MassMotion follows the Softimage convention of putting X and Z horizontal)
  • export selected only (this is useful rather than essential, as you can subsequently export just any changes rather than the whole model)

It depends on whether the objects (or Actors as Softimage calls them) are just Softimage actors or MassMotion ones, or if you are in the standalone MassMotion or MassMotion Flow.

MassMotion / MassMotion Flow

To delete – select and press the [Delete] key, or right click and select Delete

To copy – select and right click, select Duplicate, or use Ctrl+D

Softimage actors

Select and Ctrl+D to duplicate

Select and press [Delete] on the keyboard

MassMotion actors in Softimage

Select the graphics, [<-Find] on the MassMotion workbench to locate the data, then use the [Duplicate] button, also on the MassMotion workbench.

To delete use the same steps as above but use the [Delete] MassMotion workbench button.

Because MassMotion actors contain far more data than just the geometry, the Softimage commands Ctrl+D or Delete do not suffice as it would only copy of remove the geometry, leaving the MassMotion data behind.

Stay up to date, sign up to our Newsletter

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

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.