Open 3D Engine
A modular 3D game engine for interactive experiences, featuring a physically-based renderer, physics simulation, and asset workflows
&
| + | Familiar Build System | Uses CMake to generate build files and manage dependencies while organizing the process for building, testing, and packaging projects. |
|---|---|---|
| + | Physically-based Photorealistic Renderer | Processes scene data using physical models to output visual results and supports current rendering pipelines for accurate scene construction. |
| + | Flexible Runtime Scripting | Provides environments (such as Script Canvas and Lua) that allow runtime modifications of logic without needing to recompile the project code. |
| + | Real-time Physics Simulations | Performs simulations for collisions and dynamic interactions during runtime by incorporating various physics solutions, ensuring interactive behavior in scenes |
| + | High-performance Math | Uses optimized libraries and SIMD-based functions to conduct numerical and geometric operations, supporting the calculations needed in rendering and simulation. |
| + | Extensible Visual 3D Content Editor & Scripting Tools | Provides a visual interface for editing 3D scenes and managing scripts while allowing users to modify content and logic through integrated editors and Python support. |
| + | Robust Networking | Manages the synchronization of data and communication across projects using TCP and UDP protocols, supporting multiplayer setups with player-hosted and dedicated server configurations. |
| + | Terrain Performance | Manages large-scale landscape data and asset streaming to support the creation of extensive virtual worlds while maintaining runtime performance. |
| + | Data-driven Asset Workflows | Uses industry-standard file formats and JSON configuration to import, convert, and process assets asynchronously, streamlining asset integration in projects. |
| + | Prefab Support | Groups entities and configuration data into reusable packages, which simplifies the assembly of repeated elements and enables dynamic instantiation in scenes. |
| + | Simplified Project Management | Uses command-line scripts and JSON configuration files to manage project structure and integrate components, facilitating the organization of projects and customizations via Gems. |
| + | Flexible Code & Data Templates | Provides predefined structures for code and data, assisting in the setup of projects and the addition of new modules while maintaining consistency in project organization. |
| + | White Box Tool | Offers an environment for quickly prototyping level design and testing gameplay mechanics, which allows users to evaluate ideas in a simplified setting before full asset integration. |
| + | File Tag System | Assigns tags to assets for inclusion or exclusion during processing. Benefit: Offers control over asset bundling and packaging. |
| + | Event Bus System | Provides messaging channels for components to exchange signals. Benefit: Supports communication across engine parts without direct dependencies. |
| - | Toolchain Fragmentation | Uses separate tools and modules that are managed independently. This separation requires users to coordinate integration across components manually. |
| - | Configuration Process Challenges | The setup requires coordination of file types and scripts. This process extends the time needed to initialize and manage projects. |
System Requirements
Version ↓
| # | Minimum | Recommended |
|---|---|---|
| 1 |
| |
| 2 | Quad-core (4 cores) 64-bit x86-capable Intel or AMD processor, 2.5 GHz, with the SSE 4.1 SIMD instruction set | Hexa-core (6 cores) 64-bit x86-capable Intel or AMD processor, 2.5 GHz, supports the SSE 4.1 SIMD instruction set |
| 3 | 16 GB RAM (8GB RAM may be acceptable if you limit the number of threads used for compilation) | 32 GB RAM |
| 4 |
| SSD with 1 TB of free disk space |
| 5 |
|
|
| 6 | 1366 x 768 pixel screen resolution | 1366 x 768 pixel screen resolution |
| # | Minimum |
|---|---|
| 1 |
|
| # | Minimum |
|---|---|
| 1 |
|
Ratings
Not available, but we appreciate help! You can help us improve this page by contacting us.
Developer
Written in
C, C++, Python, Roff, CMake
Initial Release
6 July 2021
Repository
Categories
Alternatives
Notes
A bit of relevant history:
- Based on CryEngine licensed to Amazon by Crytek GmbH in 2015, Amazon released its game engine called Amazon Lumberyard. 1 2
- Amazon Lumberyard received its last commit on Sep 29, 2022, and was archived on Oct 4, 2022. 3
- In 2021, Amazon and Linux Foundation announced that some code of the engine would be used to create a new game engine called Open 3D Engine, managed by Open 3D Foundation (which is run by Linux Foundation). 4