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 a Godot 3D Ambient Emitter Being Too Quiet From a Wrong Unit Size

Q: What causes a Godot 3D ambient emitter being too quiet from a wrong unit size?

The AudioStreamPlayer3D's Unit Size is far too small for your world scale, so the inverse-distance attenuation drops the volume to almost nothing just a few meters from the emitter.

Quick answer: Increase Unit Size to match your world scale (the distance at which the sound is at its reference volume) and pick an attenuation model that fits, so the bed is audible across its intended area.

Unit Size sets the distance scale of the 3D falloff. If it is tiny relative to your meters-per-unit, the sound vanishes almost immediately. Matching it to world scale restores audible range.

How to fix it

1. Raise the unit size

Increase AudioStreamPlayer3D.unit_size so the reference distance matches how far the ambience should carry; a value of 1 in a large world makes sounds drop off in a meter or two.

2. Pick the right attenuation model

Choose an attenuation model (inverse, inverse-square, logarithmic, or disabled) appropriate to the bed; inverse-square falls off very fast and can feel too quiet for ambience.

3. Set a max distance

Use Max Distance to cap the audible range so distant ambience culls cleanly, and balance Unit Size against it so the curve covers the zone you want filled.

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.

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