Always on Worlds

The Always on Worlds feature allows continuous operation of your virtual environments.

Please contact our support team to discuss if you want to enable this feature.

The MSquared team will assess your use case and make recommendations thereafter.

Caveats

There are several potential issues with leaving Worlds and Unreal running for extended periods of time, such as:

  • Spiralling costs due to Worlds left running.

  • Unrecoverable errors of Unreal or infrastructure.

  • Necessary maintenance of infrastructure.

  • Potential memory leaks.

  • Unexpected behavior due to limitations of single-precision floating-point numbers.

Examples of unexpected behavior

This happens because floats store numbers with a fixed number of significant digits, causing small differences to become unrepresentable at high magnitudes, leading to issues like timer overflows, world time wrapping, and anomalies in physics or animations.

As such, MSquared does not:

  • Guarantee uptime for running Worlds.

  • Guarantee persistence of state.

    • Users should use the M2 Persistence System to write custom data to our backend, and retrieve it to restore state when the world is starting up.

  • Send out automated notifications when Worlds encounter unrecoverable errors.

    • They will however be left in an โ€œErrorโ€ state so that such a scenario can be observed.

Note that scheduled maintenance and retirement of infrastructure will have an impact on new and existing running worlds.

Please refer to the relevant sections in the Worlds page to learn more about these disruptions and how to be notified.

Please refer to the glossary to learn more about the difference between persistent & always on worlds.

Last updated