mxbmrp3

A customizable, open-source HUD plugin for MX Bikes displaying real-time race information and telemetry.

MXBMRP3 HUD Screenshot Example HUD layout showing standings, map, telemetry, and widgets. All elements are fully customizable.

Features

Get Started

Download and install the plugin to begin customizing your HUD. Most users should use the automatic installer. Use the ZIP for manual installation.

Download Installer Download ZIP

See Installation for setup instructions.

Contents

Installation

Requirements:

Automatic Installation

  1. Download the latest installer mxbmrp3-Setup.exe
  2. Run the installer - it will:
    • Auto-detect your MX Bikes installation (Steam or standalone)
    • Install to the correct plugins folder
    • Check for and offer to install Visual C++ Redistributable if needed
    • Handle upgrades automatically (preserves your settings)

Manual Installation

  1. Download the latest release archive mxbmrp3.zip
  2. Find your MX Bikes plugins folder:
    • Steam: Right-click MX Bikes in your library → Manage → Browse local files → open plugins
    • Standalone: Navigate to your MX Bikes installation folder (e.g., C:\Games\MX Bikes\) → open plugins
  3. Extract the plugin files:
    • Copy mxbmrp3.dlo to [MX Bikes]/plugins/
    • Copy the mxbmrp3_data/ folder to [MX Bikes]/plugins/

    Do NOT delete the existing game files (proxy64.dlo, proxy_udp64.dlo, xinput64.dli) - these are native MX Bikes files, not old plugin versions.

    Your directory should look like this after installation:

    MX Bikes/
│   mxbikes.exe
│   ...
│
└───plugins/
    ├── mxbmrp3_data/        ← Add this folder (from release)
    │   ├── fonts/           ← Font files (.fnt)
    │   ├── textures/        ← Texture files (.tga)
    │   └── icons/           ← Icon files (.tga)
    ├── mxbmrp3.dlo          ← Add this (from release)
    ├── proxy_udp64.dlo      ← Keep (native game file)
    ├── proxy64.dlo          ← Keep (native game file)
    └── xinput64.dli         ← Keep (native game file)

After Installation

Launch MX Bikes - the plugin will load automatically. Some elements are enabled by default and can be repositioned or configured via the settings menu. If nothing appears, see Troubleshooting.

Controls

Mouse

Keyboard Shortcuts

Keyboard and controller hotkeys can be customized in Settings > Hotkeys. By default, only the settings menu hotkey is configured:

Configuration

Use the settings menu (Tilde key or [=] settings button) to configure all HUDs and widgets. Hover over any setting to see its description - all controls have in-game tooltips explaining their function.

The settings menu provides:

All settings are automatically saved between sessions.

Profiles

Four separate profiles store complete HUD layout configurations:

Auto-switch (disabled by default) automatically changes profiles based on session type.

HUDs & Widgets

All HUD and widget settings are documented via in-game tooltips - hover over any control in the settings menu to see its description.

HUDs

HUD Description
Standings Live race positions with gaps, status, and tracked rider indicators
Map Top-down track map with rider positions (click to spectate)
Radar Proximity radar with approach alerts and distance arrows
Timing Split and lap times with gap comparisons
Gap Bar Visual gap-to-PB bar with position markers
Pitboard Pitboard-style lap information display
Lap Log Historical lap times with PB indicators
Ideal Lap Best sector times and theoretical ideal lap
Records Online lap records (CBR or MXB-Ranked) with personal bests
Telemetry Throttle, brake, suspension graphs
Performance FPS and plugin CPU usage
Rumble Controller rumble effect visualization

Widgets

Widget Description
Lap Current lap number
Position Race position
Time Session time/countdown
Session Session type
Speed Speed and gear
Speedo Analog speedometer
Tacho Analog tachometer
Bars Telemetry bars (throttle, brake, clutch, RPM, suspension, fuel)
Fuel Fuel calculator with consumption tracking
Lean Bike lean angle with arc gauge
Notices Race status notices (wrong way, blue flag, last lap, finished)
Gamepad Controller visualization

Modding

Custom Assets

Add custom fonts, textures, and icons by placing files in your MX Bikes user data folder:

Documents/PiBoSo/MX Bikes/mxbmrp3/
├── fonts/       ← Custom .fnt files
├── textures/    ← Custom .tga textures
└── icons/       ← Custom .tga icons

On game startup, the plugin syncs these files to the plugin’s data directory (plugins/mxbmrp3_data/). User files with the same name as bundled assets will override them. This keeps your customizations separate from the plugin installation, so updates won’t overwrite your files. Restart the game after adding or modifying assets.

Textures use the naming convention {element_name}_{number}.tga (e.g., standings_hud_1.tga). They’re auto-discovered and selectable via the Texture control in each HUD’s settings.

Fonts (.fnt files) are auto-discovered and assignable to categories (Title, Normal, Strong, Marker, Small) in Settings > Appearance. To generate fonts, use the fontgen utility provided by PiBoSo. See this forum post for details. An example configuration is provided in fontgen.cfg.

Icons (.tga files) are discovered alphabetically and available for tracked rider customization.

Data Files

Plugin data is stored in Documents/PiBoSo/MX Bikes/mxbmrp3/:

File Description
mxbmrp3_settings.ini All HUD settings (positions, visibility, options)
mxbmrp3_personal_bests.json Personal best lap times per track/bike/category
mxbmrp3_tracked_riders.json Tracked riders with colors and icons

Troubleshooting

HUD Not Appearing

Black Screen on Game Startup

Elements Appearing Twice (Ghost/Duplicate)

Elements Overlapping

Controller Not Working

For bug reports or feature requests, open an issue on GitHub.

Development

Built with C++17, Visual Studio 2022, MX Bikes Plugin API, and Claude Code.

Building from Source

Requirements: Visual Studio 2022+, Windows SDK 10.0, Platform Toolset v143

  1. Clone the repository: 
    git clone https://github.com/thomas4f/mxbmrp3.git
cd mxbmrp3
  2. Open mxbmrp3.sln in Visual Studio 2022
  3. Select Release configuration (or Debug for development)
  4. Build the solution (Ctrl+Shift+B)
  5. Output: build/Release/mxbmrp3.dlo

Roadmap

Ideas under consideration (no guarantees): extended telemetry (g-force), event log, HTTP data export for OBS overlays.

Licensed under the MIT License. See THIRD_PARTY_LICENSES.md for bundled asset attributions.

Feedback and contributions are welcome.

This site is open source. Improve this page.