A customizable HUD, drift angle gauge, second-screen dashboard, and run analysis tool for Forza Horizon 6.
Supports Steam and Xbox app / Microsoft Store editions on Windows PC.
Download Wisp 2.1.2 ·
Website ·
Changelog ·
Architecture
Support Wisp: Ko-fi ·
Buy Me a Coffee
A small performance hotfix bounds memory use for colored boost pressure numbers by reusing digit images as colors and pulse opacity change. Their appearance and existing needle behavior are preserved.
Read the Wisp 2.1.2 release notes.
The four supplementary analogue dials match at 100% and stay aligned when resized. Power and torque have separate size sliders, boost and tire sizing works while attached, and a 50–200% G-force meter size control applies across attached, detached, and Combined layouts. Previews follow these settings; existing sizes, profiles, and positions are preserved.
The power and torque features introduced in 2.1 are described below.
Power & torque · Dashboard · Drift gauge · Runs · Appearance · Gallery · Install
See live BHP and torque beside the speedometer, with native-style dials, needles, peak markers, and peak readouts. Turn either gauge on or off in Appearance > Gauges > Engine output. Attach each one to the speedometer, or detach it and use Edit HUD layout to place it separately. Torque follows your Nm or lb-ft preference. See the gauges in gameplay.
Use the separate Power gauge size and Torque gauge size sliders to resize each dial. Under More options, adjust smoothing and a fixed range for each car. Set from this run uses the peaks Wisp has observed plus 10%; the scale then stays fixed while driving. These are observed readings, not the car's rated maximum output. After retuning, reset the peaks and make another pull before setting the range again.
The Gauge start, Gauge middle, and Gauge end colors apply across boost, tire temperature, power, and torque. Optional colored numbers follow the same palette. Smoothing defaults to 250 ms; negative output is hidden unless you enable Show negative power and torque. Recorded telemetry retains its original values.
Fresh installations start with Native Analogue and all gauges enabled, with matching sizes for the four supplementary dials. Updates preserve existing settings, profiles, tire calibration, and saved runs.
Read the Wisp 2.1 release notes.
The dashboard has a new layout built around a curved tachometer, large speed and gear readings, and live power and torque. Use Display mode as a borderless dashboard on a second monitor. Fill the screen or resize it to share the monitor with something else. Press F11 from Dashboard to switch modes, or Esc to leave. Driver assists distinguish Disabled, Enabled, and Active.
Add a drift gauge above the action to see your angle and the share of the verified Drift Zone angle bonus you are using. The scoring-angle range starts at 10° and the angle bonus reaches its ceiling at 59.4°. A 20–40° drift already corresponds to roughly 80–90% of that maximum angle bonus; more angle is not automatically a better run. Speed, your line, and whether the game awards points still matter.
Choose the guidance in Appearance > Gauges. Adjust its size and position, enable dark shading for bright skies, or add a black background with adjustable opacity. The gauge keeps its ticks and readings without an outer frame. Below 5 mph ground speed (about 8 km/h), it hides the angle, marker, and bonus so a stationary car on a slope or spinning its wheels does not show misleading drift guidance.
Record a drive from Dashboard or Runs, or use a recording shortcut. Set a countdown or timed stop, mark moments while driving, then add a name, tune label, and notes. Recordings stay on your PC and can last up to ten minutes.
Search saved runs by name or tune label. Names, tune labels, and notes save automatically, with a quiet Saving… / Saved indicator. Switching runs keeps your pending edits; if saving fails, Retry lets you try again.
One Show graphs button opens the workspace. Overview, Engine, and Tires & handling group related measurements. Show or hide graphs, reorder them, and choose their width. Review statistics as cards or a table. A shared cursor and selectable time range make it easier to inspect the same moment across speed, inputs, RPM, power, torque, boost, G-force, and tire temperatures.
Compare two runs overlaid or side by side, with distinct colors and line styles. Match an acceleration speed range, inspect power and torque against RPM, or compare tire heat and cornering load. Summaries explain the measured differences and call out gaps or different starting conditions.
Use Import runs for individual .wisprun files or a Wisp library ZIP.
Export all backs up the library, and Delete all has confirmation and Undo.
Use the Export menu for a shareable run file or raw CSV, and Save image
for a graph report. Imports skip identical runs and reject conflicting duplicates
without overwriting existing data. Wisp does not identify tunes automatically
or record gameplay video.
Appearance now groups Layout, Gauges, Colors, and Behaviour with a larger live HUD preview. Set your accent, backgrounds, text, borders, glow, surface opacity, corner rounding, and spacing. G-force dot and trail colors are independent, and the G-force meter can be disabled in every layout.
Optional background particles follow your accent or a separate color. They do not react to the mouse or change your selected background color, and can be paused or hidden. The dashboard adds accent lighting and particles along its rim. Fresh installations use the setup wizard's palette; updates retain your colors and saved data. Prefer the previous interface? Enable Use legacy interface in Appearance > Layout, then restart Wisp.
Common settings stay visible, with detailed adjustments under More options. Click the existing connection status to see whether Forza is detected, whether telemetry is arriving, and why the overlay is hidden, with the relevant next step.
An optional quick tour introduces the drift gauge, Display mode, Runs, and Appearance. Start from the welcome banner or choose Replay the quick tour in Release Notes.
Download Wisp 2.1.2 · 2.1.2 release notes · Changelog
Interface screenshots show the build used to develop Wisp 2.0. Their original version labels are retained; the gameplay gallery also shows the new 2.1 gauges.
Wisp shows the speed implied by the driven wheels rather than only the car's ground speed. The difference becomes visible during wheelspin, burnouts, drifting, lockup, and loss of grip.
FH6 Data Out supplies the local telemetry stream. Wisp learns the effective rolling radius of the current tires, applies the correct driven-wheel model for FWD, RWD, or AWD, and presents the result in a lightweight Windows overlay.
- Wheel-indicated speed with separate front and rear calibration for staggered AWD setups.
- Digital and Analogue Native HUD layouts for combustion and electric cars.
- A live boost gauge for confirmed turbocharged and supercharged cars. Digital mode adds a rail below the tachometer, while Analogue mode offers a 0 to 70 PSI or 0 to 5 bar dial.
- PSI or bar readouts, a learned per-car color scale, optional colored pressure numbers, attached or detached Analogue placement, a custom three-point gauge gradient, and an independent Digital option that uses the stock tachometer material.
- Front and rear tire-temperature gauges for both Native layouts. Digital mode uses two markers in one neutral rail with no colored fill, while Analogue mode uses two solid-color needles in one dial. Values support Fahrenheit and Celsius.
- Independently optional power and torque dials with live BHP, Nm or lb-ft, peak markers, attached or detached placement, adjustable smoothing, and fixed ranges saved per car.
- Live RPM, gear, driver assists, electric power, regeneration, and redline state when the installed FH6 build supports those sources.
- Standalone or Native-attached G-force display with a longer motion trail.
- A borderless second-screen dashboard with a resizable Display mode.
- Drift angle and verified angle-bonus guidance, or a custom target and tolerance.
- Application styling, individual G-force dot and trail colors, and saved HUD profiles for layouts and gauge colors.
- Local run recording, configurable graphs, overlaid or side-by-side comparisons, report images, CSV, shareable run files, and whole-library backup and import.
- Optional update discovery on every open and daily while running, a customizable HUD visibility shortcut, and bounded local debug logging with ZIP export for issue reports.
Actual Wisp captures with custom colors. Click the 2.1 gameplay image to inspect the original-resolution HUD. The 2.0 interface captures retain their prerelease version labels.
If the Analogue tachometer lags or hitches, enable CPU rendering in Diagnostics. Right-click Wisp's tray icon, choose Exit Wisp, then reopen it to apply the change. CPU mode reuses unchanged dial-background pixels while the needle and live readings continue updating.
GPU rendering remains the default. CPU mode can increase CPU usage, and Windows still uses the GPU to compose the overlay. Other gauges keep their existing renderers. This option does not guarantee that every rendering-lag report is resolved.
- Windows 10 or Windows 11, 64-bit.
- Forza Horizon 6 for Windows PC from Steam, the Xbox app, or Microsoft Store, with Data Out enabled.
- Set Forza Horizon 6's display mode to Fullscreen.
Native process-derived HUD state supports Steam FH6 build 6.440.853.0 and
Xbox app / Microsoft Store PC build 3.440.853.0. Previous bundled maps remain
available for installations that have not updated FH6. See
Compatibility and Update Safety for the
complete bundled-build list and validation rules. Data Out reception and dashboard
calculations remain independent of those contracts. Wisp runs on Windows alongside
the game, not on Xbox consoles or a cloud-gaming session.
The installer is self-contained and installs for the current user. It does not require administrator access or a separate .NET runtime.
- Open the Wisp 2.1.2 release.
- Download and extract Wisp-Setup-2.1.2.zip.
- Keep the installer and its
.sha256file together. - Verify the installer checksum, then run the installer.
- Complete the required setup wizard on first launch.
[WINDOWS POWERSHELL]
$installer = Get-ChildItem .\Wisp-Setup-*.exe | Select-Object -First 1
(Get-FileHash -LiteralPath $installer.FullName -Algorithm SHA256).HashCompare the result with the value in the adjacent .sha256 file. The current
installer is unsigned, so Windows may show an unfamiliar-publisher warning.
Wisp checks for updates whenever it opens and every 24 hours while it remains running, including while waiting in the tray. Turn off Automatically check on open and daily in Extras to disable those checks. You can also select Check for updates there to check immediately. Automatic checks discover releases; they never download or install an update without your confirmation.
An accepted release must be public, stable, and immutable. Numeric tags must match the installer's normalized version, and GitHub must provide the installer's exact byte length and SHA-256 digest. Downloads are limited to the canonical GitHub release URL and GitHub's HTTPS release-asset hosts. Wisp shows the release summary and asks you to confirm the download, installation, and restart. After confirmation, it downloads the installer and verifies its length and digest before starting installation. The separate update helper repeats those checks, waits for Wisp to exit, runs the current-user installer silently, validates the installed version, and then restarts Wisp.
The updater uses GitHub's anonymous release endpoint and contains no repository credential. If GitHub's release API or artifact delivery is unavailable, the check reports that the update service is unavailable. The installer remains unsigned whether it is started manually or through Wisp.
A verified in-place update preserves a completed setup. A fresh installation always opens the setup wizard before the dashboard or overlays are available.
In Settings > HUD and Gameplay:
- Enable Data Out.
- Set the IP address to
127.0.0.1. - Set the port to
5500, or to the listener port selected in Wisp. - Keep the car moving briefly while the setup wizard validates the stream.
The wizard also confirms the display mode and stock HUD setting before it opens the dashboard or driving overlays.
Wheel-indicated is the default. FH6 does not report tire size, so Wisp learns effective rolling radius from clean, straight driving with grip. The value stays unavailable until the current tire profile is trustworthy.
FH6 speed uses the packet's vehicle-speed value directly and does not require tire learning. See Wheel-Speed Model for the complete calibration and drivetrain rules.
Native HUD layouts start at FH6's bottom-right HUD position. Disable the stock speedometer to avoid overlap, then use Edit HUD layout if a custom display needs different placement or scale.
The Native provider opens the supported FH6 process with query/read access only. It does not inject code, hook rendering, call game functions, or write process memory. Changed or unknown game build identities disable the affected process-derived state rather than reusing data from another build.
See Compatibility and Update Safety for the supported builds, validation boundary, and update behavior.
- Telemetry is accepted only from
127.0.0.1. - Settings and tire profiles remain in the current user's local application data.
- The installer is not code-signed.
- A changed FH6 build identity requires a reviewed compatibility map and may require an application update.
- FH6 exposes no tune identifier. Relearn the current tires after changing wheel or tire diameter.
- Software-only WPF captures do not reproduce the live Native HUD shaders.
Use a Git checkout and the .NET 8 SDK selected by global.json. Building the
native renderer also requires Visual Studio C++ build tools for x64 and a
Windows SDK containing fxc.exe; the application build compiles and copies
Wisp.NativeRenderer.dll automatically. Python 3.12 or later runs the offline
compatibility-audit tests; CI pins Python 3.14.7. Inno Setup 6 is needed only to
package an installer.
Review the contribution and permission requirements before preparing changes. Installer packaging requires Git and a clean checkout; a downloaded source ZIP is not sufficient. See Validation for the packaging checks and Shaders for rebuilding shader bytecode after HLSL changes.
[WINDOWS POWERSHELL]
dotnet restore Wisp.sln --locked-mode -p:NuGetAudit=true -p:NuGetAuditMode=all
dotnet format Wisp.sln --verify-no-changes --no-restore --verbosity minimal
dotnet test Wisp.sln --configuration Release --no-restore --nologo --disable-build-servers -m:1 -p:UseSharedCompilation=false
python -m unittest discover -s tools/tests -p "test_*.py" -vTo build the self-contained installer:
[WINDOWS POWERSHELL]
.\installer\Build-Installer.ps1- Boost Gauge
- Tire Temperature
- Run files and library archives
- Wisp 2.1.2 release notes
- Wisp 2.1.1 release notes
- Wisp 2.1 release notes
- Wisp 2.0 release notes
- How Wisp Was Built
- Wheel-Speed Model
- Compatibility and Update Safety
- Validation
- Shader maintenance
- Contributing
- Security Policy
Wisp is proprietary, source-available software. Official unmodified binaries may be used personally and non-commercially under the Wisp Proprietary Source License.
Forza Horizon 6 © Microsoft Corporation. Wisp is an unofficial community project and is not endorsed by or affiliated with Microsoft.
The Native HUD content under src/Wisp.App/Assets/Native is based on publicly
circulated Forza Horizon 6 material. Views2k claims no ownership of Microsoft
Game Content. See Third-party notices and the
Microsoft Game Content Usage Rules.








