What causes a texture quality setting not reducing VRAM until reload?

Already-loaded textures keep their full mip chain resident; the global texture limit only affects textures uploaded after the change, so existing ones stay at full size.

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 Texture Quality Not Reducing VRAM Until a Level Reload

Quick answer: Set the global master texture limit and force resident textures to drop their top mips, or budget a streaming reload so the limit applies to currently loaded assets.

A player on a low-VRAM card sets textures to Low expecting relief, but VRAM stays pinned because loaded textures keep full mips. Apply the limit to resident textures, not just future loads.

How to fix it

1. Set the global limit

Use QualitySettings.globalTextureMipmapLimit (formerly masterTextureLimit) to skip top mips. Note it primarily affects textures loaded after the change.

2. Flush resident textures

To reclaim VRAM immediately, unload and reload (or re-stream) currently resident textures so they respect the new limit instead of keeping the full chain.

3. Prefer streaming

If you use mipmap streaming, the system re-evaluates resident mips over a few frames after the budget changes, giving a smoother live reduction than a hard reload.

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 Unity 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.