Repository navigation
OpenLauncher v2.3.0
What's new in v2.3.0
E-Sys 3.x support [Alpha]
Open CAFD Map's names and labels now work in E-Sys 3.x (tested with 3.35.3 on Java 8), not just 25.x:
- Labels in the CAF and FDL views: groups, functions and value names come from the same definitions and name database as 25.x.
- CAF and NCD files: values read from an NCD (Ausgelesen) are labelled too, and those nodes expand normally.
- On-demand definitions: a CAFD version that has no definition yet gets BMW's untrimmed names immediately and full labels a few seconds later, the same as on 25.x.
E-Sys 3.x keeps an open CAFD in an older model, which OpenLauncher recognises separately. E-Sys 25.x is handled exactly as before.
The OpenLauncher section (Compare NCD, Cheat Sheet) still needs E-Sys 25.x, because 3.x has no navigation bar to add it to.
Fixed
- Closing E-Sys shortly after starting it is no longer reported as "E-Sys stopped during startup"; OpenLauncher now says "E-Sys closed."
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: 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.2.2...v2.3.0