Artifacts
Binary compatibility
Linux binaries are generated by the Steam Runtime 3 ‘sniper’ SDK, compiling with GCC 14. This makes executables compatible with a variety of distributions. The Steam Runtime environment itself can be used to increase compatibility at runtime if needed. Static libraries should only be used when compiling in the same environment.
Window binaries are built with Visual Studio 2022.
All native binaries are compiled for the x86-64 architecture.
Horizon
Those are the core components of Horizon and are all required to run the engine. See the introduction for more details on the architecture.
Protocol
- npm (TypeScript):
@siradel-oss/horizon-protocol - Linux native package (C++)
- Windows native package (C++)
API
Core
Other
Scene dump
This is a TypeScript library to save and load Horizon scene dumps to and from JSON, base64 or binary data.
Monitoring protocol
Use this to deserialize monitoring messages. See Monitoring the engine.
Monitoring client
This application connects to and monitors a Horizon client using WebSocket.
Testing kit
This archive contains tools to run visual tests inside of Horizon. It contains a viewer that opens a scene dump and takes a screenshot of the loaded scene, an image comparator, and a scene dump migration tool. See the documentation in the archive.
Protocol Buffers definitions
The Horizon protocol & monitoring protocol .proto files are available directly in the source tree. These can be useful for creating tooling, or new integrations with languages other than the ones we ship libraries for already.
- Horizon protocol:
//hrz/protocol. - Horizon monitoring protocol:
//hrz/monitoring.
Documentation
Your are reading it right now, but you may want a local copy.
Gallery
Interactive demos showcasing the engine’s capabilities.