LogoLogo
API Status
  • 👋Welcome
  • 🌐What is Morpheus Platform?
    • Interoperability
  • â„šī¸Help
    • 📗Glossary
    • 🆘Support
    • Firewall problems
    • EULA
  • CREATION
    • 🎮Unreal Development
      • ⚡Get Started
        • âš’ī¸Download the Editor
        • âĢUpload Content
        • 🌎Creating your own map
        • 📝Morpheus Base Project
        • ❓Differences from Unreal
          • 🧍Character Configuration
        • 📡Morpheus Networking
          • Introduction to Morpheus Networking
          • Network Levels
          • Replicated Properties
          • RPCs
          • Morpheus Render Targets
          • Morpheus Array
          • Networking FAQ
          • Replicating Sublevels
      • 📚Features & Guides
        • 📒Example Plugin
          • Nameplates
          • In-game roles
          • Resizing
        • 🏊Actor Pooling
        • 🔊Audio
        • 🎭Avatars
          • Creating an Avatar
          • Attachments
            • MML Attachments
          • Custom Animation Variables
          • Importing an NFT collection
          • Capsules and Mesh Transforms
        • 🤖Bots
        • đŸŽ™ī¸Chat
          • Unreal Text Chat
        • đŸŽ›ī¸Control Panels
          • Control Panel Configuration
          • DJ booth mission control
          • Observer Controls
        • 🔉Crowd Audio
        • đŸ¤ŧCrowd Rendering
          • Legacy Animated Crowd
            • Animated Crowd Console Commands
            • Attaching static meshes to crowd members
          • Crowd Materials
          • Performance Parameters
          • Live Config Settings
          • Crowd Animation
            • Crowd Anim Blueprint
              • User Guide - Crowd Anim Blueprint
              • Reference Guide - ABP Nodes
                • Animation Playback
                • States and State Machines
                • Variables
                • Transitions
                • Special
                • Blends
                • Additional Notes
        • 🍱Helpers & Extras
          • "Instanced Objects" in Blueprints
          • Objects with "world context"
          • Making DataAsset classes
          • Duplicate Objects
          • The Bootflow Subsystem
          • The "Wait For Condition" System
          • Advanced Graphics settings
          • Listening to inputs on UObjects
          • Morpheus UserID
          • World Services
          • M2Extras: Skins System
        • đŸ–Ĩī¸Loading Screen
        • ⚡Live Config
          • Editing for a World
          • Editing Locally
          • Default Settings
          • Accessing via Blueprint
          • Adding New Settings
          • Overriding Defaults
          • Using Arrays
        • 🧊MML
        • đŸ•ēMotion Capture
        • 📡Networking
        • đŸ“ĸNotifications
        • Raycastable Crowd
        • 🌐Singletons
        • 📱Streaming & Multiplatform
          • GFN on mobile
        • đŸ–Ĩī¸UI
          • "UI Mode"
        • đŸ—ƒī¸User Collections
          • Creating a New Object Definition
          • Accessing from Unreal
            • Creating Objects Definitions
            • Transfer Objects
            • User Collection Views
            • Receiving Updates
        • đŸ“ēVideo Players
          • Embedded Video Player
          • Millicast video streaming
            • How to Setup an In-Game Video Stream
            • Picture-in-Picture mode
          • Streaming Video Player
            • How to Setup a URL Video Player
            • Picture-in-Picture mode
        • 🐞Visual Debugging
          • Inspector
        • đŸĒŸWeb UI
        • Online Services
          • KV Store Service
        • 💠Web Requests
          • Http Requests
            • Legacy HTTP Nodes
          • JSON Handling
          • WebSockets
          • Identity Validation
          • Allowed External URLs
          • Walkthrough Example
            • Example Counter Service
        • âœˆī¸World Travel
          • World Travel in the editor
        • Avatar Physics Assets
        • Action Gameplay Helper Components
      • 🔑Workflows
        • â†—ī¸Upgrade the Editor
          • đŸ–Ĩī¸Version History
        • âš™ī¸Editing Project Settings
        • 📈Profiling
        • đŸ§ēMarketplace Importing
        • đŸ› ī¸Extra Workflows
          • Setup Play-in-Editor
          • Setup Local Asset Validation
          • Adding Gameplay Tags
          • Validating Game Assets
          • Custom Connection Modes
          • Connect Editor to a World
          • Common Issues
      • 📚Useful Reading
        • ⭐Best Practices
    • 🌎Worlds
      • 📩Invite Players
        • Setting Role Groups
      • Persistent Worlds
      • Always on Worlds
    • 📅Running events
      • ✅Large scale events - Checklist
      • 👾Anti-Cheat (EAC)
      • 🎮Player Entry
        • 📱React Native
        • Steam
        • đŸ’ģHardware Reqs
      • đŸŽĨBroadcast
        • 📹OBS Integration
      • Failover
      • 🏁Capacity And Queue Management
  • ADMINS
    • đŸ‘ĒAccess Control
      • Adding metaverse contributors
      • Creating a new project
    • 💲Pricing
      • Development Support
      • Included Usage & Overages
      • Cloud Streaming
      • Access Modes
      • War Room Support
      • Platform SLA
    • âš™ī¸Settings
      • đŸ—ƒī¸Projects
  • APIs and Tooling
    • đŸ–Ĩī¸API Reference
      • Accounts
      • Events
      • Key/Value Store
      • Organizations
      • Realtime
      • User Profile
      • World Builder
      • Worlds
    • đŸ’ģTemplate Web App
      • đŸ’ĸModeration
    • Pixel Streaming
    • 🚀Launcher
  • Integrations
    • 📊Analytics
      • Sending events from web
      • 🎮Sending Events from Unreal
    • đŸ’ŦChat
      • 🎮Integrating Pubnub with your Unreal Project
      • Adding Moderation to Chat
Powered by GitBook
On this page
  • Optimise for the worst case
  • Project structure

Was this helpful?

  1. CREATION
  2. Unreal Development
  3. Useful Reading

Best Practices

For Massive Interactive Live Events (MILEs)

Optimise for the worst case

Unintuitively, in the Morpheus stack we care far more about the realistic worst case scenario performance than we do the average.

Optimisations that improve the average case (or even worse, best case!) may look good during development, but really only hide the impact of the worst case we may see in practice. To that end:

We should keep our best and worst case performance as close as possible.

This gives us predictable behaviour and increases the confidence in our testing. For example:

  • Sending RPCs at fixed intervals even without payload

  • Sending junk chat messages to always run up to our chat rate limit

This does not mean we do not care about the average case, only that we prioritise the worst. For scenarios longer than a MILE, optimising the average case performance may help for cost saving reasons.

Player behaviour invariance

Game performance is primarily influenced by what players do in the game. The worst case performance is some function of all the different actions players can take in a game.

In order to understand the performance of our games, we need to know and test the worst case player behaviour (see above). This means making the best case and worst case performance due to players as close as possible. To achieve this:

Player behaviour must have as little impact on performance as possible.

This does not mean limiting players' actions or freedom in games; instead, it means that regardless of what players choose to do the system load is similar.

Examples of how we achieve this:

  • Every player in Morpheus sees the closest N players regardless of distance

  • Every client in Morpheus sends RPCs at 10Hz whether there is data to send or not

Be wary of metres

If you are thinking about designing a system which cares about how far away things are, especially players, it likely isn't density invariant. The worst case performance will be significantly worse than the best case.

For example:

  • If players check out other players within 10m of themselves, then every player will see everyone if they all go to the same spot

  • If your world is split into grid squares and a player sends a chat message to every player in the same square, then every message will be received by everyone if they go to the same grid square

Use budgets rather than units.

  • Check out the nearest 50 players rather than any within 10m

  • Send chat messages to the nearest 50 players rather than to others in the same grid square

Project structure

Morpheus Platform aims to structure projects as closely to native Unreal Engine as possible and supports development within the project content folder. We encourage new projects to be structured in a way in which:

  • The majority of content is stored within the project content folder

This is the project structure used by our internal projects and as such, this structure is the most widely tested and least likely to lead to avoidable issues.

Due to legacy reasons, some older projects may have content entirely within plugin(s) but this is not a current limitation of the platform. Ultimately, the choice for project structure is down to the user.

PreviousUseful ReadingNextWorlds

Last updated 1 month ago

Was this helpful?

Plugins are used to define libraries of

🎮
📚
⭐
shareable content