OMSI 2

openOMSI

openOMSI is a from-scratch recreation of the bus simulator OMSI 2, written in Rust: 64-bit, multithreaded, with a modern renderer. It loads existing OMSI 2 maps, buses, scenery and mods as they are. Early development.

Original Dev: MR Software / Aerosoft
Port Maintainer(s): openOMSI-org

What You Need

  1. Requires an installed copy of OMSI 2 (Steam or retail) with its stock content. openOMSI will not start without it.

    • OMSI 2 install folder
    Verify Your Files (Client-Side) 100% In-Browser
    Privacy guarantee: Files never leave your device. File names, headers, and checksums are checked locally in your browser.

    Drag & drop file(s) here or browse from your device

    Matches your files against this port's requirements and calculates SHA-256 hashes.

    File Requirements Checklist (1 required):

    • OMSI 2 install folder (Folder requirement)
  2. Target hardware: Snapdragon 865 or newer or equivalent (64-bit ARM64, Android 8+).

  3. Controls ready out of the box

    On-screen touch controls work immediately. Physical Bluetooth and USB-C controllers are also supported.

Clean-Room Rust Engine Architecture and wgpu Vulkan Rendering

openOMSI, developed by the openOMSI-org community (release v0.3.43), is an ambitious clean-room open-source engine recreation of MR Software and Aerosoft’s acclaimed 2013 public transit simulator, OMSI 2: Der Omnibussimulator. The original Windows simulator was constructed using 32-bit Delphi and legacy DirectX 9, architectural constraints that left it notoriously single-threaded and susceptible to out-of-memory crashes due to the 32-bit 2 GB address space limit. openOMSI completely discards that legacy technical debt, rewriting the entire simulation core from scratch in memory-safe, multithreaded Rust. Rendering is managed through the wgpu graphics abstraction framework, which outputs high-performance, native Vulkan API calls on 64-bit ARM (aarch64) Android hardware.

Native Parsing for Berlin-Spandau Maps, Bus Scripts, and IBIS Systems

The engine’s parser was engineered specifically to maintain drop-in compatibility with decades of existing simulation assets. It natively ingests stock and community files, reading .map road network files, .bus physics models and operational scripts, cabin instrument panels, timetable databases, and AI traffic dispatch routines without alteration. Drivers can explore historical routes like the classic 1986-1994 Berlin-Spandau network, operate authentic double-decker buses, interact with complex Integrated On-Board Information System (IBIS) ticket ticketing units, and load community vehicle add-ons. The modernized graphics engine provides four distinct rendering presets: Vanilla (matching the original flat aesthetic), Standard, Enhanced, and Enhanced+, which incorporates physically based rendering (PBR), dynamic real-time atmospheric lighting, and high-resolution shadow cascades.

Deploying Stock Steam and Retail PC Assets via docs/ANDROID.md

Because openOMSI functions strictly as an engine recreation, it contains no proprietary game assets. You must supply legal files from your own licensed PC copy of OMSI 2, obtained via Steam or original retail DVD. Locate your computer’s game directory and verify the presence of essential core folders: Vehicles/, Sceneryobjects/, Splines/, Maps/, and Fonts/. Copy this entire root folder onto your Android device’s local storage. Download and install openOMSI-v0.3.43-android-arm64.apk from GitHub Releases (compatible with Android 8.0 or newer). Finally, launch the app and link the asset location according to the setup instructions detailed in the repository’s docs/ANDROID.md guide.

Active-Alpha Hardware Requirements, Tiered Presets, and Controls

The project is currently in early active-alpha development, meaning features and optimizations are evolving rapidly. Hardware with a Qualcomm Snapdragon 865 or newer 64-bit SoC paired with Vulkan support is recommended to handle complex multi-bus AI scheduling and geometry density. Standard vendor GPU drivers run cleanly without specialized driver modifications (turnipRecommended: false), though dialing settings down to the Vanilla or Standard rendering tiers provides the steadiest frame rates on thermal-constrained devices. Input systems support direct touch interaction for cockpit switches and steering, connected hardware USB or Bluetooth keyboards for authentic cab hotkey operation, and standard physical gamepads.