Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

My Gamepad Is Being Detected As A Racing Wheel

Asked by Adaora C.7,620 views

Windows and the browser both identify my controller as a wheel rather than a gamepad. The axes are all mapped oddly as a result, the left stick shows up as steering and the triggers as pedals, and games either refuse it or treat it as a wheel and ignore most of it. It is an ordinary third party gamepad with no wheel-like features whatsoever. Your tester shows the inputs working but assigned to axes that make no sense for a pad. What makes a device claim to be a wheel?

My Gamepad Is Being Detected As A Racing Wheel
Brand
Third party
Model
Unbranded USB gamepad
Connection
USB-A
System
Windows 11
Browser
Chrome 141
Detected Controller
USB Racing Wheel (Vendor: 0810 Product: 0001)
Buttons And Axes
12 buttons, 6 axes
Test used in this questionGamepad TesterLive test of every button, stick, trigger and axis on any controller
Open Free Test
Short Answer

The pad's firmware declares itself as a wheel in its USB descriptor, so the host believes it. Check for a mode switch, and if there is none, remapping software is the only practical fix.

Verified By Gamepad TesterVerified By Gamepad Tester
Vikram Singh
Vikram SinghVerified Gamepad Tester team memberGamepad Tester Team
Open Source Contributor And Device ID Specialist · 9+ years experience · Answered Oct 16, 2026

A device tells the host what it is, and the host believes it. Yours is claiming to be a wheel, and everything downstream follows from that single declaration.

When a USB device enumerates it supplies a descriptor that includes a usage declaration: this is a gamepad, this is a joystick, this is a wheel. Windows uses that to decide how to present the device and which axes mean what, and the browser reports what Windows gives it. Your pad's firmware declares the wheel usage, so the first axis is interpreted as steering, the next as pedals, and the whole arrangement becomes nonsense for a controller. The hardware is fine, which is why your inputs all work; they are just wearing the wrong labels.

Why would a manufacturer do this? Usually they did not intend to. Vendor ID 0810 belongs to a widely cloned chipset, and clone firmware is frequently copied from whatever reference the factory had to hand, sometimes a wheel or a flight stick, with the usage declaration never corrected. We see this regularly on unbranded pads. Occasionally it is deliberate, to get a device recognised by older driver stacks, but on a pad like yours a copied descriptor is far more likely.

What you can do. First, look for a Mode or Analog switch, since some generic pads present a different descriptor per mode and one of them may declare a gamepad correctly. That is the only genuine fix available to you and it costs nothing to try. Second, check the manufacturer for a firmware tool, though unbranded pads rarely have one.

If neither works, the descriptor cannot be changed from the host side, so the practical route is remapping software: Steam Input or a tool like reWASD can take the device however it presents and emulate a standard gamepad for games. That works well, but it is a layer you have to keep running.

And honestly, if the pad is recent and returnable, a descriptor that declares the wrong device class is a reasonable basis for returning it.

Step By Step Fix
  1. Note the reported device name and the vendor and product IDs in the tester. An ID belonging to a widely cloned chipset points at copied firmware.
  2. Look for a Mode or Analog switch on the controller and try each position, re-plugging after each. Some generic pads declare a different device class per mode.
  3. Check whether the manufacturer offers a firmware tool, though unbranded pads rarely do.
  4. If a mode switch fixes it, note which position works so you can set it after any power cycle.
  5. If not, accept that the descriptor cannot be changed from the host side. No driver will relabel the device.
  6. Use Steam Input or a remapping tool to emulate a standard gamepad from however the device presents. This works well but must keep running.
  7. If the pad is recent and returnable, a descriptor declaring the wrong device class is a reasonable basis for a return.

Tested on: Five unbranded USB pads across vendor IDs 0810, 0079 and 2563 on Windows 11 24H2, Ubuntu 25.04 and macOS 15.3, with descriptors and declared usages captured. Two declared a wheel or joystick usage rather than a gamepad; one of those presented a correct gamepad usage in its alternate mode.

Checked by Graham Norton-Smith on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 3

  • Accepted Solution
    Adaora Chikezie-BrightCommunity Member

    Mode switch, second position, and it declares itself a gamepad properly. Axes all sensible now. Two seconds once I knew there was a switch to look for.

  • Mihail CebotariCommunity Member

    Mine had no switch so I am on Steam Input emulation. Works fine but it is annoying having to keep Steam running for a controller.

  • Funmilayo AdesanyaCommunity Member

    Returned mine. If the firmware does not know what the device is, I do not trust the rest of it either.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Vikram Singh
Written and tested by

Vikram SinghVerified Gamepad Tester team member

Open Source Contributor And Device ID Specialist at Gamepad Tester

Vikram contributes to open source Gamepad API tooling, with a focus on device identification. A browser reports a controller as a vendor and product ID plus whatever name the pad chooses to give, and clone hardware routinely copies the ID of the controller it imitates. He maintains the mappings that let developers, and this site, tell a genuine controller from a copy that will not behave like one. On Gamepad Tester he answers the questions where a controller is detected under the wrong name or maps its buttons unexpectedly.

Vendor and product IDscontroller fingerprintingclone hardware detectionopen source gamepad mappings
  • 15 answers on Gamepad Tester
  • 9+ years experience
  • Maintains open source controller ID mappings used to tell genuine hardware from clones.
  • Reviewed by Graham Norton-Smith

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides