Post #1
S
Online now
- Joined
- 07.11.2026
- Messages
- 1
- Reactions
- 0
- Location
- 🇺🇸
USUnited States
Hi! I've been working on Open CAFD Map (a fully open repo for coding data) and OpenLauncher, a free, open-source launcher for E-Sys (3.30.x - 26.x) (similar idea to commercial launchers). It works alongside your existing E-Sys and makes coding readable again by replacing the "." inside CAFDs with a combination of verified and dynamically calculated names and definitions, plus FA/VO tools, NCD diffs, сhеаt sheets, and backups.
The main reason I started working on it is because I think there should be more options, options that are free and don't re-invent the wheel since the two other big paid launchers already do what they do really well and people don't need another paid launcher that costs $100.
If you just want to code your own BMW once or twice and actually see what FDL edits you're making, I don't think you should have to spend $100+ on software, rely on an outdated old launcher, or pay somebody every time you want to change one small thing (unless you specifically want an all-in-one suite with 140+ workshop functions). Or maybe you just want a simple lightweight launcher that doesn't follow the naming convention of the iPhone.
Compatibility: Java 8 and 11 versions of E-Sys (3.30.x - 26.x), though anything pre-22.x has very limited support at the moment.
What's in it so far:
We've reached a pretty respectable level of verified coverage on F- and G-chassis vehicles, and v3.0.0 is still being tested and developed, so I'm not saying everything is perfect yet. I'm actively fixing bugs and growing the database as more CAFDs get mapped.
If anybody here wants to test it, no PCID, activation, or trial timer needed. Just grab it from GitHub, try it out, and send logs if you hit anything weird.
Seriously, it's free, and always will be. No HWIDs and activation codes, no trials, no monthly/annual payments, or lifetime purchases.
I mainly want people to actually use it, test different cars/modules/E-Sys builds, and tell me what works, what doesn't work, and what could be better.
Download HERE (Releases) · Docs · GitHub
More competition and more options for BMW coding is a good thing.
The tool only functions with your own installation of E-Sys and PsdZData, neither of which are provided with the tool.
The main reason I started working on it is because I think there should be more options, options that are free and don't re-invent the wheel since the two other big paid launchers already do what they do really well and people don't need another paid launcher that costs $100.
If you just want to code your own BMW once or twice and actually see what FDL edits you're making, I don't think you should have to spend $100+ on software, rely on an outdated old launcher, or pay somebody every time you want to change one small thing (unless you specifically want an all-in-one suite with 140+ workshop functions). Or maybe you just want a simple lightweight launcher that doesn't follow the naming convention of the iPhone.
Compatibility: Java 8 and 11 versions of E-Sys (3.30.x - 26.x), though anything pre-22.x has very limited support at the moment.
What's in it so far:
- Zero E-Sys patching: Renames nodes in memory only when launched via OpenLauncher; nothing is installed into or modified inside your E-Sys folder.
- In-E-Sys FA / VO Helper (v3 preview): Tick lists for SALAPA options, HO-words, and E-words backed by 8,456 shipped type keys, with live production-window checks, KIS conflict detection, and PsdZ target-SVT / missing-CAFD checks.
- In-E-Sys Compare NCD: Side-by-side NCD diffing (including across different CAFD versions) with highlighted changes and TSV export.
- In-E-Sys сhеаt Sheet: Community and custom сhеаt sheets alongside E-Sys's FDL Editor, with version compatibility checks (✓ / ● / ◐ / ✎ / ✗) and manual Save/Code control.
- FA / SVT auto-backup: Automatically saves versioned XML copies of every FA and SVT read from the vehicle.
We've reached a pretty respectable level of verified coverage on F- and G-chassis vehicles, and v3.0.0 is still being tested and developed, so I'm not saying everything is perfect yet. I'm actively fixing bugs and growing the database as more CAFDs get mapped.
If anybody here wants to test it, no PCID, activation, or trial timer needed. Just grab it from GitHub, try it out, and send logs if you hit anything weird.
Seriously, it's free, and always will be. No HWIDs and activation codes, no trials, no monthly/annual payments, or lifetime purchases.
I mainly want people to actually use it, test different cars/modules/E-Sys builds, and tell me what works, what doesn't work, and what could be better.
Download HERE (Releases) · Docs · GitHub
More competition and more options for BMW coding is a good thing.
The tool only functions with your own installation of E-Sys and PsdZData, neither of which are provided with the tool.