Added in 1.0.10

Profiles, custom colors, and everyday controls

Named HUD profiles

Save a combination from Appearance, give it a name, and switch between saved setups on Profiles. Each profile keeps your HUD layout, enabled gauges, units, sizing, opacity, orientation, and complete color combination. Apply, Update, Rename, and Delete let you manage your setups. Tire calibration and saved screen positions stay separate, along with telemetry, startup, update, debug, and hotkey settings.

A full color editor

Select an element from the list in Extras, then use the color wheel, saturation, brightness, opacity, or exact ARGB input. Customize the app accent, backgrounds and surfaces, HUD border, boost and tire-gauge gradient, and the independent traction hook cue color. Save the combination to a profile from Appearance without changing telemetry calculations.

Live torque and session peaks

Torque appears beside horsepower on the Wheel Speed Ready card with matching styling and smoothing. Choose Nm or lb-ft. Top speed, peak power, and peak torque sit below the live readings. Reset all three together, or let them reset when you change cars.

Update notifications and release details

Optional startup checks look for updates no more than once every 24 hours. A Dashboard banner announces a newer release, and its GitHub release summary appears before download confirmation. Manual checks remain available. Nothing installs automatically, and the version, size, and SHA-256 checks remain in place.

A customizable HUD hotkey and support tools

  • Assign a global shortcut to show or hide the overlay without opening Wisp.
  • Enable local debug logging in Diagnostics and export a ZIP for an issue. The more detailed reports introduced in 1.0.12 are described below.
  • Read release notes directly from Wisp's sidebar.
  • Use the small GitHub shortcut in Extras if you want to leave Wisp a star.

Fixed in 1.0.10

HUD placement, tachometer fallback, and color controls

  • Detached boost and tire-temperature gauges retain their saved positions across restarts and updates, including placements on secondary displays.
  • Profile changes restore the correct saved placement when switching layouts or Native Digital and Analogue styles. The selected torque unit is saved and applied too.
  • Expired native tachometer samples no longer repeatedly interrupt RPM fallback motion when the native reader stalls.
  • The traction hook cue works across Native HUD styles, and stale slip evidence is cleared after stopping.
  • Color-wheel clicks and drags work throughout the wheel. Slider changes no longer move the selected wheel position, and dark background colors remain editable with readable surfaces.
  • The color dropdown is replaced by a themed element list and larger editor. Debug logging controls match the rest of Wisp. The duplicate profile-save button and save-dialog outline are removed.
  • Simultaneous debug-log actions no longer wait indefinitely.
  • A failed telemetry-listener start no longer leaves UI callbacks running.

Improved in 1.0.12

See where a problem starts

Optional local debug logging records incoming and processed telemetry separately, packet freshness, UI dispatcher delays, native-data freshness and failures, composition gaps, focus changes, and Wisp's CPU and memory usage. Measurements share consistent timestamps, and background collection continues during a stalled UI.

Each export includes a readable summary: what happened and when, the measurements behind the finding, the likely affected component, what remains uncertain, and the next useful diagnostic step. Normal menus, hidden overlays, and ordinary telemetry disconnection are distinguished from faults.

What a report cannot tell you

Game FPS and GPU presentation latency are not measured. A report can help narrow a problem to part of Wisp, but it cannot guarantee the exact cause of every Windows or driver issue. When evidence is insufficient, the report says so.

Local and optional

Capture a problem, then choose what to share

Enable local debug logging in Diagnostics, reproduce the problem, and export the debug ZIP. Note roughly when it happened and whether you were driving, opening settings, or switching windows. Review the report before attaching it to a GitHub issue.

Collection is opt-in, stays local, stops after 24 hours per activation, and is bounded in storage. Wisp does not upload the report automatically.

Fixed in 1.0.12

Native HUD recovery and update confirmation

  • Fixed a Native HUD recovery case after opening settings during a race. Wisp can recover when the game's secondary local-provider flag is cleared, while still requiring the existing compatibility checks and a unique match to the live car, RPM, and maximum RPM.
  • Removed the outer outline from the update confirmation dialog. Release details and explicit download confirmation are unchanged.