General Archives - RIDE https://ride.ict.usc.edu/category/general/ Rapid Integration & Development Environment Sat, 25 Apr 2026 05:39:53 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 https://ride.ict.usc.edu/wp-content/uploads/2020/05/cropped-RIDE_Logo_Icon_250x-32x32.png General Archives - RIDE https://ride.ict.usc.edu/category/general/ 32 32 How RIDE Benefits STE https://ride.ict.usc.edu/getting-started/faq/ste-benefits/?utm_source=rss&utm_medium=rss&utm_campaign=ste-benefits Sat, 06 Jun 2020 07:30:07 +0000 https://ride.ict.usc.edu/?page_id=309 Partnerships across the DoD will lead to unique capabilities and knowledge that become foundational within the STE collaborative environment.

The post How RIDE Benefits STE appeared first on RIDE.

]]>
General

Benefits

Partnerships across the DoD will lead to unique capabilities and knowledge that become foundational within the STE collaborative environment.

Science & Technology

  • Save Time & Money by jump-starting research initiatives – days becomes hours, months become weeks.
  • Integrate and test efforts in a unified environment.
  • Unified Framework for TRL Levels, Integration potential, and metrics.
  • Shared code base, open and beneficial to all users.
  • Create reusable frameworks for testing and research.

Industry

  • Utilize, evaluate, and inform capabilities that are not currently supported or beyond SOW.
  • Enables continued iterations and testing independent of S&T or Vendor progress.
  • Assists in defining foundational components and verifying systems during dev process.

Government

  • Leverage existing investments and ensure re-use of capabilities.
  • Fuse disparate code for similar functionalities to reduce support costs.
  •  Increase automation and reduce resources necessary for development.
  • Simplify path to transition by maintaining RMF and ATO procedures to a single code base.

The post How RIDE Benefits STE appeared first on RIDE.

]]> Examples https://ride.ict.usc.edu/support/documentation/examples/?utm_source=rss&utm_medium=rss&utm_campaign=examples Wed, 13 May 2020 18:47:23 +0000 https://ride.ict.usc.edu/?page_id=165 The RIDE platform contains several example scenes that feature one or multiple capabilities of the API.

The post Examples appeared first on RIDE.

]]>
General

Examples

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.

Example Astar Pathing Image

A* Pathing

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

Example Agent Behaviours Image

Agent Behaviours

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

Example Agent Commands Image

Agent Commands

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.

RIDE Asset Lineup Soldiers

Asset Lineup

Collects available entity prefabs for inspection, modification and testing.

Example Audio Image

Audio

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

Example Face Image 2

Audio-Visual Sensing

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

Barracuda API Image 1

Barracuda API

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

Example Behaviour Comparison Image

Behaviour Comparison

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

Example Camera Home Image 00

Camera Home

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

Example Camera Tween Image

Camera Tween

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

Example Combat Image

Combat

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.

Example Movement Data Mono Image

DataMono Entities

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

Example DIS Image 01

DIS Messages

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

Dynamic Spawn Example Image

Dynamic Spawn

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

Example Ground Classification Weather Image 00

Ground Classification Weather

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

RIDE Logo Placeholder

Headless Mode

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.

Example Interpretation System Image 00

Interpretation System

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

Example Astar Pathing Image

A* Pathing

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

Example Agent Behaviours Image

Agent Behaviours

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

Example Agent Commands Image

Agent Commands

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.

Example Audio Image

Audio

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

Example Face Image 2

Audio-Visual Sensing

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

Barracuda API Image 1

Barracuda API

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

Example Behaviour Comparison Image

Behaviour Comparison

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

Example Camera Home Image 00

Camera Home

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

Example Camera Tween Image

Camera Tween

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

Example Combat Image

Combat

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.

Example Movement Data Mono Image

DataMono Entities

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

Example DIS Image 01

DIS Messages

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

Dynamic Spawn Example Image

Dynamic Spawn

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

Example Ground Classification Weather Image 00

Ground Classification Weather

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

RIDE Logo Placeholder

Headless Mode

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.

Example Interpretation System Image 00

Interpretation System

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

Example LOS Image

Line of Sight

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

Example Localization Image 02

Localization

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

RIDE Logo Placeholder

Logging

Use the RIDE API to implement your own logging.

Example MSELI Image

MSELI

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.

The post Examples appeared first on RIDE.

]]> RIDE License https://ride.ict.usc.edu/getting-started/obtain-ride/ride-license/?utm_source=rss&utm_medium=rss&utm_campaign=ride-license Tue, 12 May 2020 21:38:34 +0000 https://ride.ict.usc.edu/?page_id=110 All RIDE users are bound by the below RIDE license as well as all Bundled Components licenses.

The post RIDE License appeared first on RIDE.

]]>
General

RIDE License

All RIDE users are bound by the below RIDE license as well as all Bundled Components licenses.

USC ICT RIDE License Agreement

The Rapid Development & Integration Environment (RIDE) has been developed by the University of Southern California (USC) Institute for Creative Technologies (ICT). Use of RIDE requires a Distribution Agreement. Please email ride@ict.usc.edu for more information.


Government Purpose Rights (“GPR”)
Contract No. W911NF-14-D-0005
Contractor Name: University of Southern California
Contractor Address: 3720 S. Flower Street, 3rd Floor, Los Angeles, CA 90089-0001
Expiration Date: Restrictions do not expire, GPR is perpetual
Restrictions Notice/Marking: The Government’s rights to use, modify, reproduce, release, perform, display, or disclose this software are restricted by paragraph (b)(2) of the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause contained in the above identified contract. No restrictions apply after the expiration date shown above. Any reproduction of the software or portions thereof marked with this legend must also reproduce the markings. (see: DFARS 252.227-7014(f)(2))

No Commercial Use: This software shall be used for government purposes only and shall not, without the express written permission of the party whose name appears in the restrictive legend, be used, modified, reproduced, released, performed, or displayed for any commercial purpose or disclosed to a person other than subcontractors, suppliers, or prospective subcontractors or suppliers, who require the software to submit offers for, or perform, government contracts. Prior to disclosing the software, the Contractor shall require the persons to whom disclosure will be made to complete and sign the non-disclosure agreement at 227.7103-7. (see DFARS 252.227-7025(b)(2))

The post RIDE License appeared first on RIDE.

]]> Contact https://ride.ict.usc.edu/support/contact/?utm_source=rss&utm_medium=rss&utm_campaign=contact Tue, 12 May 2020 19:59:46 +0000 https://ride.ict.usc.edu/?page_id=66 Get in touch about a technical issue or custom distribution license.

The post Contact appeared first on RIDE.

]]>
General

Get in Touch

Reach out with a question, technical issue or custom distribution license inquiry.

 

USC ICT

12015 Waterfront Drive, Playa Vista, CA 90094-2536 USA

General Inquiry

The post Contact appeared first on RIDE.

]]> About https://ride.ict.usc.edu/about/?utm_source=rss&utm_medium=rss&utm_campaign=about Tue, 12 May 2020 19:28:10 +0000 https://ride.ict.usc.edu/?page_id=56 RIDE is being developed at the USC Institute for Creative Technologies, a non-profit University Affiliated Research Center. RIDE has been made possible by funding from the Army Cross Functional Teams (CFT) and the Office of Naval Research (ONR).

The post About appeared first on RIDE.

]]>
ICT Exterior image

RIDE: Rapid Integration & Development Environment

RIDE is a simulation environment that unites many DoD simulation efforts to provide an accelerated development platform and prototyping sandbox that will provide direct benefit to the Army’s Synthetic Training Environment (STE) as well as the larger DoD simulation communities.

RIDE combines a range of commonly used simulation features in a drag-and-drop development environment, including One World Terrain, NPC and vehicle placement, and AI behaviors.

RIDE is being developed at the USC Institute for Creative Technologies, a non-profit University Affiliated Research Center. RIDE has been made possible by funding from the Army Cross Functional Teams (CFT) and the Office of Naval Research (ONR).

The post About appeared first on RIDE.

]]> Support https://ride.ict.usc.edu/support/?utm_source=rss&utm_medium=rss&utm_campaign=support Tue, 12 May 2020 19:26:47 +0000 https://ride.ict.usc.edu/?page_id=54 This website contains several resources for working with the RIDE API and will expand as the API evolves. Please notify the team if you cannot find the information that you seek.

The post Support appeared first on RIDE.

]]>

Support

This website contains several resources for working with the RIDE API and will expand as the API evolves.

Please notify the team if you cannot find the information that you seek.

Quickstart

Learn how to start using RIDE in a sample project, or how to integrate its core components into a custom project.

Documentation

In-depth materials covering RIDE API and individual capabilities via Example scenes.

Contact

Get in touch about a technical issue, custom distribution license, or any questions regarding the use of RIDE.

Release Notes

Details changes made since the previous release of the RIDE platform to external collaborators and developers.

Due to the RIDE API being a free of charge service for the academic community, USC ICT can only offer limited support.

The RIDE API uses 3rd party software for which dedicated support structures often exist.

The post Support appeared first on RIDE.

]]> Getting Started https://ride.ict.usc.edu/getting-started/?utm_source=rss&utm_medium=rss&utm_campaign=getting-started Wed, 06 May 2020 17:59:16 +0000 https://ride.ict.usc.edu/?page_id=40 RIDE allows developers to collaboratively research and develop common training and simulation capabilities in a sandbox environment that has been designed to facilitate rapid prototyping.

The post Getting Started appeared first on RIDE.

]]>

Getting Started

RIDE allows developers to collaboratively research and develop common training and simulation capabilities in a sandbox environment that has been designed to facilitate rapid prototyping. Obtain RIDE here.

RIDE offers a range of interconnected features. To get started with development, review the Quickstart information, Tutorials and the Documentation pages.

The API has been designed to be independent of any particular game or simulation engine. The current implementation uses Unity, with other implementations under consideration.

RIDE allows developers to collaboratively research and develop common training and simulation capabilities in a sandbox environment that has been designed to facilitate rapid prototyping. Obtain RIDE here.

RIDE offers a range of interconnected features. To get started with development, review the Quickstart information, Tutorials and the Documentation pages.

The API has been designed to be independent of any particular game or simulation engine. The current implementation uses Unity, with other implementations under consideration.

Quickstart

Learn how to start using RIDE in a sample project, or how to integrate its core components into a custom project.

RIDE API Index

Technical reference manual for developers with all classes, functions, services, etc. in the RIDE API.

Examples

Each scene demonstrates a different capability of the RIDE API inside of the Unity platform.

Tutorials

Guides for how to create your own scenes and customize the RIDE standalone application.

Requirements

The necessary hardware and software specifications for utilizing the RIDE API.

FAQ

Ongoing collection of responses to questions posed by our diverse user base.

The post Getting Started appeared first on RIDE.

]]>