mxbmrp3

MXBMRP3 - Usage Survey Report

Data window: 2026-06-27 → 2026-10-31 (127 days, 110 observed)

Generated by tools/analytics_report.py from Aptabase exports - do not edit.

At a glance  
Unique installs 19,933
Downloads 93,951
Releases since Nov 2025 43
Avg active/day 2,477
Launches 1,032,264
Countries 111

Unique installs: plugin copies that have reported since 1.26, each counted once however often it is updated. Downloads: installer and zip from GitHub, updates included.

Games

Game Installs Launches Share of launches
MX Bikes 19,622 1,019,624 98.8%
GP Bikes 216 10,474 1.0%
Kart Racing Pro 95 2,166 0.2%

Activity over time

Daily charts omit partial export days (2026-06-27, 2026-10-31); totals include them.

Curves pool all games (GP Bikes and Kart Racing Pro are 1% of launches).

Installs seen

Active installs: new versus returning

The first weeks are existing users upgrading, not new ones; averages use the last 30 full days.

Downloads

Downloads per day

Launches per active install

When people ride

Session length

Retention

A floor: an install that stops playing looks the same as one that removed the plugin. The report’s first week (existing users arriving) is not counted.

Lifetime launches per install

Geography

Installs by country (top 15)

Achievements

Achievement tiers earned per install

Achievements unlocked per install

Achievements by tier reached

Hidden achievements - 31 of the 32 earned by anyone (spoilers) Hidden achievements by tier reached

Feature & HUD adoption - MX Bikes

MX Bikes only (19,622 installs). (GP Bikes 216 and Kart Racing Pro 95 have too few for their own.)

Features (feat_*)

HUD adoption (hud_*)

Widget adoption (widget_*)

Not charted: Pointer (always on); Spotter (follows the spotter, see Features).

Operating system

OS Installs
Windows 11 78% (14,394)
Windows 10 21% (3,932)
Linux / Proton / Wine 1% (217)
Other Windows <1% (1)

18,544 of 19,933 installs report an OS

Plugin version adoption

Each install counts once, at its most recent version; 8 of 19,933 run the prerelease channel.

Release line Released Unique installs Downloads
1.34 2026-10-26 <1% (52) 90
1.33 2026-10-24 10% (1,977) 3,136
1.32 2026-10-10 12% (2,354) 4,795
1.31 2026-10-03 6% (1,167) 3,255
1.30 2026-09-06 26% (5,222) 9,691
1.29 2026-08-26 7% (1,440) 6,056
1.28 2026-07-30 21% (4,149) 5,462
1.27 2026-07-12 11% (2,183) 7,641
1.26 2026-06-28 7% (1,389) 3,856
1.25 2026-06-21   2,147
1.24 2026-06-14   2,435
1.23 2026-05-30   3,818
1.22 2026-04-26   6,578
1.21 2026-04-05   4,742
1.20 2026-03-30   1,574
1.19 2026-03-28   648
1.18 2026-03-22   368
1.17 2026-03-15   726
1.16 2026-03-08   1,217
1.15 2026-02-11   4,398
1.14 2026-01-24   5,608
1.13 2026-01-18   2,113
1.12 2026-01-11   3,202
1.11 2026-01-05   1,838
1.10 2025-12-29   1,950
1.9 2025-12-23   1,304
1.8 2025-12-16   1,183
1.7 2025-12-13   524
1.6 2025-12-09   1,210
1.5 2025-11-29   2,386
Total   19,933 93,951

Version migration

Crashes (upstream / stability)

Analysed: 104,764 of 107,572 crash reports (1.27.5+ builds, full diagnostics). Excluded: 2,797 from earlier builds and 11 from dev tooling.

Recorded faults landed outside the plugin (in the game or another module), not necessarily the root cause. Known crashes are grouped by cause, the rest by module.

Crash rate by game

Game Installs 1.27.5+ launches Crash reports Launches with a crash report
GP Bikes 186 8,728 1,044 12.0%
Kart Racing Pro 86 1,944 397 20.4% *
MX Bikes 17,891 866,478 103,323 11.9%

* Kart Racing Pro has 86 installs: a few machines can set this rate.

Crashes by cause

The Plugin (MXBMRP3) slice (59 crashes) is where the fault landed, not proof the plugin caused it.

Access-violation type Reports
read 79% (82,389)
write 18% (19,288)
execute 2% (2,361)
not recorded <1% (726)

Most common crashes

66% (69,224) of reports match the known-crash list.

Crash Share Fix / workaround
Offline track-load crash (bad string in per-profile data) 32% (33,359) ✔
Physics contact blow-up (bad table index) 17% (17,466) -
OpenGL render buffer write (vertex-fill overrun) 9% (9,483) ✔
Session teardown null dereference (leaving a session / connecting) 7% (7,314) -
Session-teardown crash via input/message pump (stale pointer) <1% (699) -
Null dereference in network / session-end code <1% (545) -
Out-of-range array index read at session end <1% (357) -
64-bit pointer truncated to 32-bit (stack above 4 GB) <1% (1) ✔

✔ = a documented workaround.

Not yet catalogued

The other 34% (35,540), most frequent first. unknown+0x0 is an address in no loaded module (likely freed memory).

Fault (module + offset) Category Share
mxbikes.exe+0x22765c Game 4% (4,587)
mxbikes.exe+0x1d742c Game 3% (2,852)
unknown+0x0 Unknown 2% (2,319)
mxbikes.exe+0x1a29ae Game 2% (2,271)
mxbikes.exe+0x255f1f Game 1% (1,100)
mxbikes.exe+0x1eea9c Game <1% (872)
mxbikes.exe+0x1902be Game <1% (864)
mxbikes.exe+0x10ced3 Game <1% (818)
mxbikes.exe+0x2889e0 Game <1% (792)
mxbikes.exe+0x255ef0 Game <1% (788)

About this data

The plugin only sends anonymous, aggregate telemetry (no personal data - see the privacy note in the main README). Reporting began in 1.26 (a few stray older builds send only a basic launch event) and expanded through 1.27, so older versions report fewer fields. Percentages are always taken over the installs that actually report a given field, and each chart notes how many installs that is, so incomplete rollout is never shown as a real trend.

Definitions. Unique install - a unique install_id (regenerated if the analytics file is deleted, so a wipe-and-reinstall reads as a new install). Launch - one plugin start (app_started). Active install - an install that launched on a given day. Crash report - one fault caught by the crash handler, saved on crash and sent on the next launch (≈ one per crashed launch). Each install belongs to one game (the plugin installs separately per game); its game, country, and version are its most recently seen values.

Developer/test machines are excluded report-wide (3 installs, 1,778 events): they launch every dev build and deliberately trigger crashes to validate the telemetry, which would otherwise read as phantom plugin crashes.

Unidentified launches are excluded report-wide (7,291 of them, 27% of what the install total would otherwise be, from at least 118 machines): a plugin whose analytics file had become unreadable minted a throwaway id on every launch, so each launch arrived as a brand-new install that never returned. Their launches go with them (1% of launches). The plugin now repairs the file, so this shrinks as those installs update.

What each release line reports (share of its launches):

Release line Launches Features HUDs / widgets OS version Update channel Panel theme Crash detail
1.25 1 0% 0% 0% 0% 0% 0%
1.26 128,782 100% 100% 0% 100% 0% 0%
1.27 177,195 100% 100% 100% 100% 0% 85%
1.28 196,018 100% 100% 100% 100% 0% 100%
1.29 114,323 100% 100% 100% 100% 100% 100%
1.30 265,240 100% 100% 100% 100% 100% 100%
1.31 50,063 100% 100% 100% 100% 100% 100%
1.32 75,016 100% 100% 100% 100% 100% 100%
1.33 25,218 100% 100% 100% 100% 100% 100%
1.34 408 100% 100% 100% 100% 100% 100%