How do I create, save, and link on-board profiles per game for the Basilisk V3 X HyperSpeed?

Applies to: Razer Basilisk V3 X HyperSpeed
Last updated: 30 October 2025

Problem

You want per-game or per-app settings that load automatically and still work when you use a different PC. You need to know how to build software profiles, link them to games, and then write core settings to the mouse’s on-board memory so your essentials travel even without software.

Solution

Create software profiles for each game or workflow in your configuration app, then link them to game executables so they auto-switch on that machine. Next, write your must-have settings (DPI stages and default, polling rate, and critical button remaps) to the mouse’s on-board memory. Assign a convenient button to cycle profiles when software is not present, and keep a “Safe” hardware profile for fallback.

Step-by-step instructions

A) Plan your profiles

  1. List the games/apps that truly need different settings (for example: General, Shooter, MOBA, Editing).
  2. Decide the differences: DPI/default stage, polling rate, Hypershift layer, scroll-tilt actions, and any macros.

B) Create software profiles

  1. Open your mouse configuration app on Windows.
  2. Select the mouse, go to Profiles, and Add a new profile for each title or task.
  3. In each profile, set:
    • DPI stages and default
    • Polling rate
    • Button remaps and any Hypershift assignments
    • Scroll-tilt behavior
  4. Test the profile briefly in a live window to confirm the feel.

C) Link profiles to games or apps (auto-switch)

  1. In the Profiles section, use Linked Games or Application Linking.
  2. Browse to the game’s executable (.exe) or app.
  3. Confirm auto-switching works by launching the game and watching the profile change in the app.

D) Write essentials to on-board memory (hardware profile)

  1. Open On-board Memory or Hardware Profiles.
  2. Choose a hardware slot.
  3. Save the key elements you need away from software: DPI stages and default, polling, and your primary remaps.
  4. Close the software (or move the receiver to another PC) and verify that DPI, default stage, and core remaps persist.

E) Make profile switching easy without software

  1. Pick a seldom-used button and assign Cycle Hardware Profiles (or similar) so you can switch on the fly.
  2. Keep a paper or digital cheat sheet that lists which slot equals which profile until it’s muscle memory.
  3. If you prefer a single “do-everything” hardware profile, save that one in Slot 1 and use software profiles only where you have the app installed.

F) Build a “Safe” fallback profile

  1. Create a profile with standard left/right/middle clicks, sensible DPI (for example 1200), and 500–1000 Hz polling.
  2. Save it to a hardware slot. If a shared PC or dock behaves oddly, switch to this profile first.

G) Maintain and back up

  1. Export your software profiles after major changes.
  2. Note which hardware slot maps to which use case.
  3. After firmware or OS changes, quickly re-verify that on-board settings still apply off-software.

Optional methods or tools

  • Per-game DPI/eDPI sheets: Keep a small table of your DPI and in-game sensitivities so you can recreate them quickly.
  • Hypershift mini-maps: Use the same Hypershift layout across games (for example, hold = utility actions) to reduce relearning.
  • Second receiver: If you use multiple PCs, keeping a labeled receiver per system makes testing and profile verification faster.

Best practices or tips

  • Keep the number of profiles modest. Four well-defined profiles are easier to manage than ten overlapping ones.
  • Standardize your button logic. For example, forward side button = interact across every profile; Hypershift + forward = reload/tool switch.
  • Save only the essentials to on-board memory. Complex macros are best left to software profiles where you can debug or update easily.
  • Name profiles clearly (e.g., “Shooter-LowDPI-1000Hz” or “Office-HighDPI-250Hz”) so you know the key differences at a glance.
  • After big OS or driver updates, quickly re-test auto-switching and on-board behavior before a match or presentation.

Consistent profiles start with a clear plan. Define what truly changes per title—usually DPI/default stage, polling rate, and a few button roles—then keep everything else as consistent as possible. This limits context switching and keeps muscle memory intact as you move between games and apps.

On-board memory is your travel insurance. By writing the core feel of your mouse to hardware, you get predictable control even on systems without software. Pair that with a labeled cycle button and a Safe fallback profile, and your Basilisk V3 X HyperSpeed will feel right at home whether you are on your main rig, a laptop, or a borrowed PC.