Comparison
neoOMSI vs openOMSI
neoOMSI started as a fork of openOMSI, the Rust recreation of OMSI 2. Both play the maps, buses and mods of your OMSI 2 installation. This page shows how they differ and how to switch.
At a glance
| Feature | neoOMSI | openOMSI |
|---|---|---|
| Origin | Fork of openOMSI, developed independently | The original project |
| License | GPL-3.0-or-later (inherited openOMSI code stays MIT) | MIT |
| Written in | Rust | Rust |
| Graphics | wgpu: DirectX 12, Metal, Vulkan | wgpu: DirectX 12, Metal, Vulkan |
| Needs OMSI 2 | Yes, plays your installed copy | Yes, plays your installed copy |
| Platforms | Windows, macOS, Linux, Android | Windows, macOS, Linux, Android |
| Dedicated server | Yes, Windows and Linux | Yes |
| Compatibility target | OMSI 2.2.032, verified subsystem by subsystem | Full compatibility with existing OMSI 2 content |
| Status | Early release | Early release |
openOMSI details are taken from its own GitHub repository.
Where neoOMSI comes from
neoOMSI was originally forked from openOMSI by usonskyyyy. The code it inherited stays under the MIT license and is credited in the NOTICE file.
Since then neoOMSI has been its own project, with its own releases, issue tracker and documentation. Everything it adds is licensed under GPL-3.0-or-later, which requires anyone who distributes a modified version to publish its source code too.
What neoOMSI focuses on
Verified behavior
Every subsystem is compared with OMSI 2.2.032 and only counts as done once it matches and is covered by regression tests. See Compatibility.
Clean-room code
No proprietary source code, decompiled binaries or copyrighted assets. neoOMSI only reads the files of your own OMSI 2.
Documented triage
Bugs are classified and verified against the original game before they are fixed. See Issue triage.
A build for every change
Every change to the main branch is built for all platforms and published. See Releasing & versioning.
Switching from openOMSI
Download neoOMSI for your system from the download page and unpack it into its own folder.
Start neoOMSI and point the launcher to the same OMSI 2 folder you used with openOMSI.
Copy your add-ons into the
Modsfolder next to neoOMSI, or add them on the launcher's Mods page.Pick a map, a bus and a duty, and drive. Your OMSI 2 files stay unchanged, so openOMSI keeps working too.
Questions about neoOMSI and openOMSI
No. neoOMSI started as a fork of openOMSI and is now a separate project with its own name, license, releases and issue tracker.
Yes. neoOMSI was originally forked from openOMSI by usonskyyyy. The code inherited from openOMSI stays under the MIT license and is credited in the NOTICE file of the neoOMSI repository. Everything neoOMSI adds is licensed under GPL-3.0-or-later.
No. neoOMSI is developed independently and is not endorsed by the openOMSI maintainers.
Yes. Both read the maps, buses and mods of an installed copy of OMSI 2, and neither ships game content of its own.
Download neoOMSI for your system, unpack it into its own folder and point the launcher to the same OMSI 2 folder you used before. Copy your add-ons into the Mods folder next to neoOMSI. Your OMSI 2 files are never changed, so you can keep openOMSI installed alongside it.
openOMSI is published on GitHub at github.com/openOMSI-Project/openOMSI. neoOMSI builds are on the neoOMSI download page.