Comparison

neoOMSI and openOMSI

Both neoOMSI and openOMSI aim to replace the legacy 32-bit OMSI 2 engine with a modern 64-bit simulator. Here is a clear, factual comparison of their features and design priorities so you can choose what fits your setup.

Technical comparison

FeatureneoOMSIopenOMSI
Development & AvailabilityMaintained independently with binary releases on GitHub. Upstream attribution is preserved in the NOTICE file.Public repository developed by community contributors under the AGPL-3.0 license.
Design FocusStrict fidelity with original OMSI 2.2.032 behavior, testing vehicle scripts, physics, and timetables against the reference game. See the compatibility guide.Explores new engine extensions, experimental lighting modes, and additional plugin formats.
Release CadenceStaged releases tested against original OMSI 2 behavior to prevent regressions on existing maps.Rapid update cycle with frequent releases and preview snapshots.
PlatformsWindows (x64, ARM64), macOS (Apple silicon, Intel), and Linux (x64, ARM64).Windows (x64, ARM64), macOS (Apple silicon, Intel), Linux (x64, ARM64), and experimental Android builds.
Virtual Reality (VR)PCVR headsets on Windows through OpenXR, with 3D cockpit tracking and spatial UI menus.PCVR headsets on Windows through OpenXR.
Graphics & UpscalingDirectX 12, Vulkan, and Metal with NVIDIA DLSS and AMD FSR upscaling on Windows.DirectX 12, Vulkan, and Metal with multiple visual presets, including experimental physically based lighting.
AudioSteam Audio integration with 3D positional audio, engine sound occlusion, and cabin reverb.Directional stereo sound.
Scripts & PluginsExecutes original OMSI vehicle scripts and standard Windows plugin DLLs.Executes original OMSI vehicle scripts and Windows plugin DLLs, with experimental Lua and WebAssembly plugins.
Dedicated ServersStandalone headless server packages for Linux (x64, ARM64) and Windows without GUI or GPU dependencies.Dedicated server mode included within the main game package.
Mod SupportLoads add-ons from folders or .zip archives via a dedicated Mods folder, keeping original OMSI 2 files untouched.Loads add-ons from folders or archives (.zip, .7z, .rar) without modifying original OMSI 2 files.

For current openOMSI downloads and documentation, visit the openOMSI GitHub repository.

Testing both engines

Because both engines read your OMSI 2 files without changing them, you can install and test both side by side without duplicating your game assets.

  1. Download neoOMSI from the download page and extract it into any separate folder on your PC.

  2. Launch neoOMSI and select the same OMSI 2 installation folder you use with openOMSI. Both engines read the content without modifying it.

  3. Place any custom add-ons into neoOMSI's Mods folder, or manage them on the launcher's Mods page.

  4. Both engines can safely coexist on your computer. You can use whichever engine best fits your preferences and hardware.

Common questions

openOMSI is well suited if you want to experiment with new capabilities like Android mobile builds, experimental lighting, or new plugin formats. neoOMSI is geared toward players looking for reliable desktop bus simulation: it focuses on reproducing original OMSI 2.2.032 behavior, with integrated Steam Audio 3D sound, DLSS and FSR upscaling, and dedicated server downloads.

neoOMSI originated from an earlier version of openOMSI, but has since diverged into an independent engine focused specifically on desktop simulation stability, verified OMSI 2 behavior, and standalone dedicated servers.

Yes. Both engines read your existing OMSI 2 installation without modifying it. You can extract each into its own folder, point both to the same OMSI 2 directory, and use them independently.

Yes. Both engines are built to read original OMSI 2 files. Custom add-on folders and archives can be placed in neoOMSI's Mods folder without altering your base installation.

No. The two engines use independent network protocols and synchronization code. Multiplayer sessions require everyone to run the same engine.

No. Both codebases have diverged substantially since the initial fork and are developed separately. Attribution for original upstream code is maintained in the NOTICE file.