bbhost v0.2.21

• See what limits your frame rate. F10 has a new Performance meter, off by default. Under the FPS counter it shows, second by second, what holds the frame rate - the GPU, the game's main thread, the threads that prepare its draws, the renderer, or the frame cap - and what would hold it next, with how busy each one is (#186).
• Logs that say why. About once a minute, and each time you change areas, the log gets a perf summary: line: the frame rate, what held it and how busy each part was. If the game runs slower than you expect, send that log: it shows whether your GPU or your CPU is the limit, and where. docs/performance.md explains the lines. It costs about a tenth of a percent of one CPU core (#186).
• Radeon graphics on Windows: about 15% faster. Depth buffers now keep the layouts AMD's driver compresses and clears quickly, instead of one general layout. On a Radeon 680M at the Central Yharnam lamp the frame rate goes from 60.2 to 68.6 fps at 960x540 and from 27.1 to 31.3 at 1920x1080. Other Radeon graphics under AMD's Windows driver should gain the same way; NVIDIA, Intel and the Steam Deck draw as before (#186).
• Higher frame rates above 60 fps. At 90, 120 and Uncapped, a job in the game's draw preparation long enough to hold up the whole frame is now split, as the engine's PC builds split it. On a fast PC (an RTX 4070 at 1080p) the Cainhurst courtyard goes from about 90 to 109 fps at 120 (+20%); the other places tested run as before. At 60 and below nothing changes (#186).
• The GPU particles cost less. Their draw counts are now worked out once for a run of particle updates instead of after each one: at the Cainhurst courtyard the particles take about a quarter less GPU time. Particles whose trail is off draw only their four corners (#186).
• Online. A co-op or invasion connection that drops within half a second of being made is no longer reported to the game as connected after it went down (#186).