
Line of Sight
Demonstrates terrain map line-of-sight (LOS) system for BLUEFOR, OPFOR and CIV agents.
The RIDE platform contains several example scenes that feature one or multiple capabilities of the API.
New example scenes are added to the project regularly.
Explore the /Assets/Ride/Examples/ directory in your local version for additional scenes not yet listed in this documentation.
The Level Select standalone release may feature certain Examples that currently do not have distributed source files.
The RIDE platform contains several example scenes that feature one or multiple capabilities of the API.
Explore the /Assets/Ride/Examples/ directory in your local version for additional scenes not yet listed in this documentation or not featured in the current LevelSelect scene listing.
New example scenes are added to the project regularly.

Demonstrates terrain map line-of-sight (LOS) system for BLUEFOR, OPFOR and CIV agents.

Create listeners for events and dispatch events in simulations.

Demonstrates loading of terrain maps into a specific scene with REST features.

Demonstrates how to load, display, and switch between different languages

Use the RIDE API to implement your own logging.

Interface systems for moving agents in scenarios.

Master scenario events list injection (MSELI) allows you to create arbitrary events in the simulation and provide them with execution orders and conditions for their execution during the scenario.

Create a navigation mesh from local OWT data for agent pathing.

Demonstrates the integration of cloud-based Natural Language Processing services for comparison within a Q & A format.

This example demonstrates how to use Google and Facebook OAuth authentication systems within RIDE.

Displays how to create particle systems from prefabs, scene objects, resources, and RideIDs.

Demonstrates autonomous agents using behavior trees (BT) in order to make decisions about patrolling and attacking.

Logs pedagogical events during an active simulation for later analysis.

This example scene shows how to create an interactive tour around a terrain using scenario events and custom AI behaviors.

Track the movement of individual agents and groups as they move in and out of defined polygonal regions.

Demonstrates how to host a RESTful service in RIDE so that it can be accessed via an HTTP request from a web browser.

Demonstrates how to spawn and move opposing agents.

The RIDE ATLAS (Aerial Terrain Line of Sight Analysis System) integration represents an improved package of ATLAS rebuilt within RIDE.

Provides the ability to record a session and then play back that session recording.

Provides the ability to record a session in a one vs. one match over the network and the ability to play back that session recording.

This example demonstrates how to set up a network environment with controllable characters using the RIDE API and Photon asset package.

Demonstrates how to open, send data over, and close a TCP socket in RIDE.

Load OWT Terrain from disk, create agents from prefabs or from the scene.

Demonstrates how to use Microsoft speech recognition in RIDE.

Demonstrates how to use the “A* Pathfinding” option as a new movement system type for units.

Instance Red/Blue agents through script at runtime.

Demonstrates a code-driven set of general and custom agent behaviors for a unit.

Command agents with basic real-time strategy (RTS) control type input. Displays a selector marquee in a specified color, with selected agents displaying a circular icon at their base.

Demonstrates how to setup a scene to use VHMsg (ActiveMQ wrapper) in RIDE.

This example demonstrates how to load and play audio clips in RIDE.

Shows how to leverage commodity audio-visual sensing AI services through REST calls, using RIDE’s common web services system.

This example demonstrates how to examine and run unit tests on various Machine Learning models residing within/outside RIDE backed with Unity Barracuda framework.

Demonstrate various ICT S&T research lines in a well-known format with very specific pass/fail parameters and training objectives.

This scene demonstrates how one might analyze side-by-side the performance of two approaches for agent cover behaviour: scripted vs. Machine Learning (ML).

Demonstrates how to reset a camera’s position and rotation at run-time using RIDE’s ICamera system.

Demonstrates how to use RIDE’s tween (in-betweening) system to move a camera.

Define the unit spawn parameters of opposing Blue and Red agents. Autonomous behaviors enable each side to navigate obstacles and engage via line-of-sight in order to reach a waypoint.

“DataMono” characters built by using bootstrappable data components for entities.

Collects the available UI elements (widgets) in RIDE.

Demonstrates how to use RIDE systems to send and receive Distributed Interactive Simulation (DIS) messages.

Spawn individual agents or squads, and then commandeer any single unit with full first-person fire/movement controls.

Shows how to upload and download files from cloud services AWS S3 and Azure Blob.

Demonstrates various tools for real-time terrain analysis.

Demonstrates the dynamic navigation of different unit types to an arbitrary waypoint under a severe weather event affecting ground conditions.

Establish groups for agents and relationships between the groups.

If the CommandLineParser.cs script is in the scene, and you create a build of the scene, then you can process all the ScenarioParameters and run your simulation with or without graphics.

Demonstrates the systems for real-time interpretation of scenario events and narrative summarization.

Demonstrates terrain map line-of-sight (LOS) system for BLUEFOR, OPFOR and CIV agents.

Create listeners for events and dispatch events in simulations.

Demonstrates loading of terrain maps into a specific scene with REST features.

Demonstrates how to load, display, and switch between different languages

Use the RIDE API to implement your own logging.

Interface systems for moving agents in scenarios.

Master scenario events list injection (MSELI) allows you to create arbitrary events in the simulation and provide them with execution orders and conditions for their execution during the scenario.