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 Godot Textures Using VRAM Compression When Lossless Is Needed

Q: What causes Godot textures using VRAM compression when lossless is needed?

The import mode is set to VRAM Compressed (an S3TC/BPTC/ASTC block format), which introduces visible block artifacts on sharp UI and pixel art that should be lossless.

Q: How do you fix Godot textures using VRAM compression when lossless is needed?

In the Import dock set the texture's Compress Mode to Lossless (and Mode to none/2D) for crisp UI and pixel art, reserving VRAM Compressed for large 3D surface textures.

Quick answer: In the Import dock set the texture's Compress Mode to Lossless (and Mode to none/2D) for crisp UI and pixel art, reserving VRAM Compressed for large 3D surface textures.

Godot's VRAM Compressed mode keeps textures small in GPU memory but is block-based and lossy, which ruins crisp UI and pixel art. Lossless compression keeps the image exact at a modest disk cost. Pick per asset based on how the texture is used.

How to fix it

1. Select the texture and open Import

Click the texture in the FileSystem dock and open the Import tab. Check the current Compress > Mode; VRAM Compressed is what causes the blockiness.

2. Switch UI/pixel art to Lossless

Set Compress > Mode to Lossless for sharp 2D art, and disable mipmaps and filtering for pixel art, then click Reimport.

3. Keep VRAM Compressed for 3D

For large 3D albedo and detail textures, leave VRAM Compressed on to save GPU memory, since block artifacts are hidden by surface detail and distance.

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

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.