What causes hardware detection picking the integrated GPU on a hybrid laptop?

On switchable-graphics laptops the process can be bound to the integrated GPU, so your detection sees weak hardware and defaults to Low even on a powerful machine.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Auto-Detected Quality Choosing the Integrated GPU on Laptops

Quick answer: Request the high-performance GPU at startup, then detect hardware so your default-quality logic reads the discrete GPU the game will actually run on.

A gaming laptop with a strong dGPU defaults to Low because detection ran on the integrated chip. The process was on the wrong GPU. Opt into the high-performance GPU before detecting.

How to fix it

1. Opt into the discrete GPU

Export the high-performance GPU hints (NvOptimusEnablement / AmdPowerXpressRequestHighPerformance) so the OS binds your process to the dGPU before you query it.

2. Detect after binding

Run hardware detection after the device is created on the correct GPU, so VRAM and GPU name reflect the chip the game uses, not the iGPU.

3. Always allow override

Auto-detection is a starting guess; always let the player change quality manually and persist that choice over future auto-detection.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.