Repository navigation
OpenLauncher v2.3.4
What's new in v2.3.4
Try OpenLauncher v3
- New button under Updates: Try OpenLauncher v3. It installs the newest v3 preview into the same folder. Your workspace and settings are kept, and edited name files are backed up first.
- Git clones switch to the
testingbranch instead. Uncommitted changes go to a git stash and local commits to a backup branch first. - If there's no preview yet, OpenLauncher says so.
- Git clones switch to the
- Going back is one click: in v3, Updates > Back to stable installs the latest stable release (or switches a clone back to
main). - Nothing changes unless you choose it. Previews are GitHub pre-releases, so normal updates and setup keep installing the stable release.
Setup
OpenLauncher-Setup.batcan install a specific release: setOCM_SETUP_TAG(for examplev3.0.0-beta.1). Only releases from this repository, and the checksum is verified as usual.
Git clones
- Force update no longer makes a backup branch for commits that are already on GitHub or already backed up.
- Updates also work in single-branch clones.
Install
- Download OpenLauncher-Setup.bat below and double-click it.
Windows may warn about a downloaded file: choose More info / Run anyway if you trust it. - Pick the install folder (default: %LOCALAPPDATA%\OpenCAFDMap). Setup checks for Python 3.10+
(it can install it with winget), downloads OpenCAFDMap.zip, verifies its SHA-256 and
creates Desktop / Start menu shortcuts. - In OpenLauncher: set your E-Sys folder and press Start E-Sys with Open CAFD Map. No build is needed for E-Sys;
Build definitions is only required for the BimmerCode Backup Editor and the command-line tools.
Upgrading: use Update launcher in OpenLauncher (v2.3.1+), or run setup again; your workspace and settings are kept.
Manual install: extract OpenCAFDMap.zip anywhere and run OpenLauncher.bat.
Definition updates (names) arrive through OpenLauncher's Check for updates without reinstalling.
Full Changelog: v2.3.3...v2.3.4