Open source
Built for the community.
OPEN SOURCE FOR OMSI 2 BY THE COMMUNITY
OmsiLaunch is an open-source session control and orchestration layer for OMSI 2.
A flexible infrastructure for defining, preparing, and managing OMSI 2 sessions with more possibilities.
WHAT IS OMSILAUNCH?
OmsiLaunch is an open-source control and orchestration layer designed for OMSI 2. It integrates tools, manages processes, handles configuration, and prepares the environment for a consistent, flexible experience.
It is not a graphical launcher. OmsiLaunch can be used by your own interface, scripts, or integrations. Control is the core. Flexibility is the goal.
Built for the community.
Works with different tools and workflows.
A complete session-orchestration layer.
For what exists today — and what comes next.
CORE CAPABILITIES
Define the map, entry point, situation, date, time, vehicle, and other parameters in a structured way.
Prepare the state and start OMSI 2 without relying on UI click automation.
Start, monitor, wait for, stop, and track sessions predictably.
Maps, situations, vehicles, repaints, HOFs, and other supported sources.
Apply temporary changes while preserving unknown data and restoring the original environment.
Snapshots, cleanup, restoration, and recovery are part of the session design.
HOW IT WORKS
Your tools and workflows describe a session. OmsiLaunch handles the orchestration behind it: preparation, process, integration, configuration, and restoration.
You define what should happen. OmsiLaunch handles how that session reaches OMSI 2.
Tools.
Configuration.
Everything connected.
OPEN SOURCE. FOR THE COMMUNITY.
OmsiLaunch is being developed as an open project focused on the OMSI 2 community. Code, documentation, technical decisions, and contributions are intended to be part of the project's evolution.
Free to use, study, modify, and share under the terms of the license.
A project created to strengthen tools and ideas around OMSI 2.
The architecture is evolving. New possibilities are still ahead.
Follow development, read the technical documentation, and take part in the next steps.
Understand the architecture