An open-source plugin for MX Bikes, GP Bikes, and Kart Racing Pro with HUDs, immersion, and streaming/broadcasting features.

Example HUD layout. All elements are fully customizable.

Features

• Customizable HUD layouts with drag-and-drop positioning, hotkeys, color themes, and auto-switching session profiles
• Live race information: standings, timing with gap-to-PB visualization, track map, proximity radar, event log, and online lap records
• Telemetry and lap analysis with splits, personal bests, lap consistency trends, and fuel consumption tracking
• Streamer-friendly features including a web overlay for OBS, Discord Rich Presence, and live controller visualization
• First-person helmet overlay with telemetry-driven tilt and suspension vibration, plus configurable controller rumble
• Rider tracking with custom colors/icons, persistent stats and personal bests across sessions, and FMX freestyle trick scoring
• Modding support: custom textures, fonts, icons, web overlay theming, and INI-level configuration

Get Started

Download and install the plugin to begin customizing your HUD.

Quick Start

1. Install the plugin
2. Launch the game and load a track
3. Right-click drag to reposition elements
4. Press Tilde (~) (the key below Esc) or click the settings button in the top-right to customize visibility, scale, opacity, and more

See Installation for detailed setup instructions.

Contents

• Installation
• Controls
• Configuration
• HUDs & Widgets
• Web Overlay
• Tips & Tricks
• Advanced Settings
• Modding
• Troubleshooting
• Feedback & Issues

Installation

Requirements:

• MX Bikes beta21 or newer / GP Bikes beta22b or newer / Kart Racing Pro Release 14 or newer

Automatic Installation

1. Download the latest installer mxbmrp3-Setup.exe
2. Run the installer - it will:
   • Auto-detect your MX Bikes, GP Bikes, and Kart Racing Pro installations (Steam or standalone)
   • Let you choose which games to install for
   • Install to the correct plugins folder for each game
   • Handle upgrades automatically (preserves your settings)

Manual Installation

1. Download the latest release archive mxbmrp3.zip

2. Find your game's plugins folder:

   • Steam: Right-click the game in your library > Manage > Browse local files > open plugins
   • Standalone: Navigate to your game installation folder (e.g., C:\Program Files\[Game]\) > open plugins

3. Extract the plugin files:

   • Copy the DLO for your game to the plugins\ folder:
     • mxbmrp3.dlo for MX Bikes
     • mxbmrp3_gpb.dlo for GP Bikes
     • mxbmrp3_krp.dlo for Kart Racing Pro
   • Copy the mxbmrp3_data\ folder to the plugins\ folder

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

   Your directory should look like this after installation (files vary slightly by game):

   [Game]/
   │   mxbikes.exe / gpbikes.exe / kart.exe
   │   ...
   │
   └───plugins/
       ├── mxbmrp3_data/        ← Add this folder (from release)
       │   ├── fonts/           ← Font files (.fnt)
       │   ├── textures/        ← Texture files (.tga)
       │   ├── icons/           ← Icon files (.tga)
       │   └── web/             ← Web overlay files (HTML/CSS/JS)
       ├── mxbmrp3.dlo          ← Add this (MX Bikes only)
       ├── mxbmrp3_gpb.dlo      ← Add this (GP Bikes only)
       ├── mxbmrp3_krp.dlo      ← Add this (Kart Racing Pro only)
       ├── proxy_udp64.dlo      ← Keep (native game file)
       ├── proxy64.dlo          ← Keep (native game file)
       ├── xinput64.dli         ← Keep (native game file)
       └── telemetry64.dlo      ← Keep (GP Bikes only)
   

After Installation

Launch the game and load into a track - the plugin only becomes active once you've entered a session (it does not run in the main menus). Some elements are enabled by default and can be repositioned or configured via the settings menu. See Tips & Tricks for useful setup ideas. If nothing appears, see Troubleshooting.

Controls

Mouse

• Move Mouse - Show cursor and settings button (auto-hides after inactivity)
• Left Click - Interact with settings menu and HUD elements
• Right Click & Drag - Reposition elements

Keyboard Shortcuts

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

• Tilde (~) - Toggle settings menu

Configuration

Use the settings menu (Tilde or the settings button in the top-right) 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:

• General - Profiles, preferences, grid snapping
• Appearance - Font categories and color theme customization
• Hotkeys - Keyboard and controller bindings
• Riders - Track specific riders with custom colors and icons
• Rumble - Controller vibration feedback effects
• Helmet - First-person helmet overlay configuration
• Updates - Check for new versions and install updates in-game
• Individual HUD tabs - Per-element visibility, scale, opacity, and options

All settings are automatically saved between sessions.

Profiles

Four separate profiles store complete HUD layout configurations:

• Practice - Practice and warmup sessions
• Qualify - Pre-qualify, qualify practice, and qualify sessions
• Race - Race 1, Race 2, Straight Rhythm sessions
• Spectate - Spectating or viewing replays

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

HUDs & Widgets

All HUDs and widgets are configurable via the settings menu or directly in the INI file.

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
Lap Log	Historical lap times with PB indicators
Ideal Lap	Best sector times and theoretical ideal lap
Lap Consistency	Lap time consistency analysis with trend visualization
Telemetry	Throttle, brake, suspension graphs
Records	Online lap records (CBR or MXB-Ranked) with personal bests (MX Bikes only)
Pitboard	Pitboard-style lap information display
Session	Session info (type, track, format, server, weather)
Timing	Split and lap times with gap comparisons
Gap Bar	Visual gap-to-PB bar with position markers
Notices	Race status notices (wrong way, blue flag, PB alerts, last lap, finished)
Event Log	Timestamped feed of race events (session changes, fastest laps, penalties, finishes, pit activity)
FMX	Freestyle trick detection with scoring and chain combos (MX Bikes and GP Bikes only)
Stats	Riding stats with columns for last lap, session, and all-time totals
Performance	FPS and plugin CPU usage

Widgets

Widget	Description
Position	Race position
Lap	Current lap number
Time	Session time/countdown
Clock	Real-time clock
Gear	Current gear
Speed	Current speed
Bars	Vertical telemetry bars (throttle, brake, suspension, etc.)
Lean	Bike lean angle with arc gauge
G-Force	Lateral/longitudinal G-force gauge with peak marker
Fuel	Fuel calculator with consumption tracking
Speedo	Analog speedometer
Tacho	Analog tachometer
Gamepad	Controller visualization
Tyre Temp	Front and rear tyre temperatures (GP Bikes only)
ECU	Engine map, traction control, engine braking and anti-wheeling (GP Bikes only)

Web Overlay

The plugin includes a built-in HTTP server that streams live race data to a browser-based overlay, designed for use as an OBS Browser Source.

Setup

1. Enable the web server in Settings > General > Web Server (the port number is shown when active)
2. In OBS, add a Browser Source with URL http://localhost:8080 (default port - use the port shown in step 1 if changed)
3. Set width/height to match your stream resolution (e.g., 1920x1080)
4. The overlay auto-connects and displays a standings tower, event log, and rider focus card

Settings Panel

The overlay includes a built-in settings panel for configuring display options without editing files:

• In OBS, right-click the Browser Source and select Interact to get mouse access
• Move your mouse to reveal a gear icon in the top-right corner, then click to open the panel
• Configure compact times, tower size, event/chip filters, focus card, font size, and more
• Drag the header bar to reposition the tower
• All settings are saved to the browser's localStorage and persist across reloads

Colors and fonts sync automatically from your in-game settings. To customize the overlay's HTML, CSS, or JS, see Modding > Web Overlay Files.

Tips & Tricks

Track records - The Records HUD fetches online lap records from CBR or MXB-Ranked. Enable "Auto-fetch" in Settings > Records to automatically load records when you enter a track. Records also work while spectating.

Click-to-spectate - Left-click on any rider on the Map HUD or Standings HUD to switch the spectate camera to that rider.

Streaming setup - Enable the Session HUD (Settings > Session) to show the server name, track, and session type on screen for your viewers. The Pitboard and Gamepad widgets also work well on stream - both have fully customizable textures, and the Gamepad widget shows your live controller inputs. Pair with Discord Rich Presence (Settings > General) to show your current session and track in your Discord profile. For a broadcast-style overlay, see Web Overlay below.

Web overlay for OBS - The plugin includes a broadcast-style overlay for streaming. See Web Overlay for setup and configuration.

Update in-game - When a new stable release is available, the plugin notifies you on startup and you can install it directly from Settings > Updates - no manual download or reinstall. Don't want the check? Set the update mode to "Off".

Power-user INI tweaks - Many additional options are available by editing the INI file directly. The file is well-commented and organized by HUD section. Each HUD section also supports per-element color and font overrides. Colors use ABGR hex values; fonts use the font filename (without .fnt) of any file in the fonts/ folder. For example:

[StandingsHud]
classicLayout=1            ; remove number plates and brand color strips

[SpeedWidget]
color_primary=0xff00ff00   ; green text (ABGR format)
font_title=RobotoMono-Bold ; Roboto Mono Bold font

Use the Color Override Picker to convert RGB colors to ABGR format. See Advanced Settings for how to edit and hot-reload the INI file.

Remove the stock pitboard - This is a game tweak, not a plugin setting. Create an empty file called pitboard.cfg in [Game]\misc\hud\ (create the directories if needed). This removes the default 2D pitboard while keeping the small 3D pitboard in the game world. Delete the file to restore it.

Show/hide the rider stand icon - This is a game setting, not a plugin setting. Enable it under Simulation > "Show Rider Stand". To customize the icon or its position, extract rider.cfg and riderstand.tga from misc.pkz\misc\helpers\ to [Game]\misc\helpers\ and edit them there.

Show/hide the game's native gear indicator - This is a game setting, not a plugin setting. Toggle it under Simulation > "Show HUD". Disable it if you'd rather use the plugin's GearWidget instead. To customize the graphics or position, extract gear.tga, hud.cfg, LCD.fnt, and switch.tga from misc.pkz\misc\hud\ to [Game]\misc\hud\ and edit them there.

Advanced Settings

All plugin settings are stored in mxbmrp3_settings.ini in your user data folder.

In-game vs INI-only settings:

• Most settings are configurable via the in-game settings menu
• Some power-user options are only accessible by editing the INI file directly
• INI-only settings are documented with inline comments

INI structure:

• [HudName] - Base/default settings for a HUD
• [HudName:Practice], [HudName:Qualify], [HudName:Race], [HudName:Spectate] - Profile-specific overrides (only values that differ from base)

Editing the INI file:

With the game closed (recommended):

1. Exit the game completely
2. Edit mxbmrp3_settings.ini
3. Launch the game to apply changes

Hot reload (for rapid iteration):

1. Disable Auto-Save in Settings > General
2. Edit the INI file while the game is running
3. Use the Reload Config hotkey to apply changes (bind it in Settings > Hotkeys)

If Auto-Save is enabled, changes made to the INI while the game is running will be overwritten.

Modding

To customize MXBMRP3, place your files in Documents\PiBoSo\[Game]\mxbmrp3\. This is separate from the plugin install folder (plugins\mxbmrp3_data\), so your customizations are preserved across plugin updates. Do not edit the bundled files in plugins\mxbmrp3_data\ directly - they will be overwritten on update (with the exception noted for custom.css below).

Custom Assets

Add custom fonts, textures, and icons by placing them in the appropriate subfolder:

mxbmrp3/
├── fonts/       ← Custom .fnt files
├── textures/    ← Custom .tga textures
├── icons/       ← Custom .tga icons
└── web/
    └── logos/   ← Sponsor/logo PNGs for the web overlay slideshow

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. Restart the game after adding or modifying assets.

Custom Textures

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.

Pitboard - Drop a custom .tga file (e.g., pitboard_hud_2.tga) into the textures\ subfolder. It will be auto-discovered and selectable in Settings > Pitboard > Texture.

Gamepad - The Gamepad widget ships with Xbox and PlayStation layouts. To customize them, copy gamepad_widget_1.tga (Xbox) or gamepad_widget_2.tga (PlayStation) from plugins\mxbmrp3_data\textures\ to the textures\ subfolder and edit them. Source design files (PSD) are available in assets/.

Helmet - The helmet overlay uses two textures: helmet_upper_1.tga (visor rim/top) and helmet_lower_1.tga (chin bar). Author at screen resolution with transparent visor openings and ~10% bleed on all sides (extra opaque border beyond the visible area) so tilt and vibration don't expose hard edges.

Custom Fonts

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.

Custom Icons

Icons (.tga files) placed in the icons\ subfolder are discovered alphabetically and available for tracked rider customization in Settings > Riders.

Web Overlay Files

The overlay files are plain HTML, CSS, and JS. To customize them, place modified files in Documents\PiBoSo\[Game]\mxbmrp3\web\ - user files override the bundled versions on startup and are preserved across updates.

• style.css - Layout variables (spacing, sizing, tower width). Colors are synced from the game.
• custom.css - Optional file you create yourself for style overrides. Loaded after style.css, so anything here wins on specificity ties. Use this for small theme tweaks instead of forking the full stylesheet - edits apply on the next browser reload (after the next game restart, since the file is synced from Documents on startup). For live iteration, you can instead place custom.css directly in plugins\mxbmrp3_data\web\ and edit it there - it's the one web asset not bundled or replaced by the installer/updater, so browser-refresh applies your changes with no game restart. Pick one location; if you keep copies in both, the Documents copy overwrites the plugins copy on next game start.
• index.html - Overlay structure
• app.js - The CONFIG block at the top defines defaults for all settings. These are overridden by the settings panel (stored in localStorage).

Data Files

File	Description
mxbmrp3_settings.ini	All HUD settings (positions, visibility, options)
mxbmrp3_tracked_riders.json	Tracked riders with colors and icons
mxbmrp3_rumble_profiles.json	Per-bike rumble effect profiles
mxbmrp3_stats.json	Unified stats, personal bests, and odometer data

Troubleshooting

HUD Not Appearing

• Check the Installation requirements for your game's minimum version
• Verify the DLO file and mxbmrp3_data\ are in the correct plugins\ folder. Games have two directories - the game installation (contains the game .exe) and user data (Documents\PiBoSo\[Game]\). Plugins go in the game installation, not Documents.
• Use the correct DLO for your game: mxbmrp3.dlo (MX Bikes), mxbmrp3_gpb.dlo (GP Bikes), or mxbmrp3_krp.dlo (Kart Racing Pro)

Installer Detected the Wrong Game Directory

• If you have multiple installations (e.g., standalone and Steam), the installer may pick the wrong one. Verify the plugin ended up in the plugins\ folder next to the game .exe you actually launch. If not, run the installer again and select the correct path, or install manually.

Text or Icons Not Appearing

• Ensure mxbmrp3_data\ folder is in the plugins\ folder alongside the DLO file (see directory structure)
• The mxbmrp3_data\ folder contains fonts, textures, and icons required for rendering
• If you moved or renamed this folder, restore it from the release archive

Gamepad Widget Appears Cut Off

• Go to Settings > Widgets tab and click "Reset Widgets" to correct the button positions.

Elements Appearing Twice (Ghost/Duplicate)

• Check for duplicate MXBMRP3 DLO files - only one of mxbmrp3.dlo (MX Bikes), mxbmrp3_gpb.dlo (GP Bikes), or mxbmrp3_krp.dlo (Kart Racing Pro) should exist in your plugins folder. Other plugins' DLO files are fine.

Elements Overlapping

• Drag elements to reposition them
• Use settings menu to adjust scale

Controller or Rumble Not Working

• Verify the correct controller is selected in Settings > General
• If you accidentally deleted xinput64.dli from the plugins folder, controller input may stop working
• To restore: verify game files integrity (Steam) or reinstall the game

Web Overlay Not Working

• If the settings show "Error" and "Port ... may be in use", another application is using the same port
• Change the port in Settings > General > Web Server Port (e.g., to 8081)
• Remember to update your OBS Browser Source URL to match the new port

Game Fails to Launch, Crashes, or Shows Black Screen

• See the MX Bikes Troubleshooting Guide for general game issues (crashes, mods, plugins, RAM, controllers)
• If the Windows Event Log shows mxbmrp3.dlo as the faulting module, see Feedback & Issues

Feedback & Issues

Bug reports, feature requests, and questions are all welcome. Open an issue on GitHub or leave a comment on MXB-Mods.

A short description of what you were doing when the issue happened (track, session type, bike, and any reproduction steps) helps a lot.

For crashes, please attach both files from Documents\PiBoSo\[Game]\mxbmrp3\crashes\ — the plugin writes them automatically whenever it catches an unhandled fault:

• mxbmrp3_crash_<timestamp>_<pid>.dmp — the minidump (state at the moment of crash)
• mxbmrp3_crash_<timestamp>_<pid>.log — a snapshot of the plugin log captured at crash time

Grab the matching pair (same timestamp/pid) for the crash you want to report. Note that the live mxbmrp3_log.txt is overwritten each time the game launches, so the paired .log snapshot is the only surviving record once you restart.

---

Development

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

• CLAUDE.md - Quick-start guide for developers and AI assistants
• ARCHITECTURE.md - Comprehensive technical documentation with diagrams

Building from Source

Requirements: the v143 platform toolset (ships with Visual Studio 2022 or the standalone Build Tools for Visual Studio 2022), a Windows 10/11 SDK, and C++17.

1. Clone the repository:

   git clone https://github.com/thomas4f/mxbmrp3.git
   cd mxbmrp3

2. Open mxbmrp3.sln in Visual Studio (2022 is easiest), pick a configuration (all x64), and build (Ctrl+Shift+B):

   Configuration	Game	Output
   All-Release / All-Debug	All three (default)	every .dlo below
   MXB-Release / MXB-Debug	MX Bikes	build/MXB-Release/mxbmrp3.dlo
   GPB-Release / GPB-Debug	GP Bikes	build/GPB-Release/mxbmrp3_gpb.dlo
   KRP-Release / KRP-Debug	Kart Racing Pro	build/KRP-Release/mxbmrp3_krp.dlo

License

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

Acknowledgments

• bh5o - Pitboard texture
• Husk - Gamepad widget source design files
• HornetMaX - MaxHUD, which served the MX Bikes community for over a decade

Thanks to everyone in the MX Bikes community who tested, reported bugs, and shared ideas.

Support

MXBMRP3 is free and open-source, and will stay that way. If it's added something to your time in the game and you'd like to chip in toward continued development, you can do so here:

No perks, no priority, no expectations. Just appreciated.