Poker Time-Bank Alerts Miss 1 in 6 HUD Overlays at Table 2

Time-bank alerts in the tested poker client stack fail to render over the heads-up display in roughly one of every six observed table states, with the failure rate climbing to 17.4% once the overlay's opacity animation is active during the final three seconds of a player's clock. The figure comes from a 1,200-hand capture across 40 sessions on a single client build, and it matters less as a glitch report than as a measurement problem: the alert layer and the HUD are drawn on separate compositing paths, and where they intersect, the more latency-sensitive of the two loses.

The practical consequence is narrow but real. A player relying on the client's own time-bank prompt to pace decisions receives that prompt unreliably at precisely the moment the information has the highest value — the last few seconds before the clock auto-folds or auto-checks. The 1-in-6 figure is an average across table states; it is not evenly distributed, and the distribution is where the engineering story sits.

What the capture measured

The test rig logged every frame in which a time-bank indicator was scheduled to appear, then checked whether the indicator's pixels were present in the composited output. A scheduled-but-absent indicator counted as a miss. Sessions ran on a 1080p display at 60 Hz with the HUD configured to its default skin, no third-party overlay tools active, and hardware acceleration enabled throughout.

Three conditions were varied: HUD opacity (static versus animated), the number of HUD panels docked to the active seat, and whether the table window held focus. Misses clustered hard around the first two. With a static HUD and two or fewer docked panels, the miss rate fell to 4.1%. With an animated HUD and four or more panels, it reached 23.8% — nearly one in four.

The compositing path

The client renders the table, the HUD, and the alert layer as separate surfaces. The alert layer is the thinnest and the last to composite, which is deliberate: it carries time-sensitive information and should sit on top. But under animation, the HUD's opacity transitions trigger a re-composite of its surface each frame, and the alert layer's draw call is occasionally dropped when the two re-composites land in the same frame budget. This is not a rendering failure in the ordinary sense. The alert exists in the draw queue; it simply does not survive to the final frame.

The 17.4% headline figure is the aggregate. The conditional figures — 4.1% and 23.8% — are the ones a player or a product team can act on.

Why table 2 specifically

The title's reference to Table 2 is not incidental. The capture ran four tables concurrently in separate windows, and Table 2 carried the highest docked-panel count because the test harness pinned its hand-history panel there. That single configuration choice accounts for most of the variance between tables. Tables 1, 3, and 4, running two docked panels each, averaged 6.9% misses across the same sessions.

This is worth stating plainly because it reframes the problem. The alert system is not broken in general; it degrades under load, and the load in question is user-configurable. A player who docks four panels to the active seat has, without intending to, made their own time-bank prompt less reliable. That is a design failure, not a user error, but it does mean the fix and the workaround diverge.

The timing window that matters

Misses are not uniformly distributed across the time-bank window either. Of the 1-in-6 misses, 71% occurred in the final three seconds — the segment where the alert's opacity animation is most active and where the player's decision cost is highest. Earlier in the window, when the alert is static, the miss rate drops to 2.9%.

The pattern suggests the animation itself is the proximate cause rather than the alert layer's priority. A static prompt composites once and holds. An animated one competes for the same frame budget as the HUD's own transitions, and the HUD, being the larger surface, tends to win. Whether the client's engineers treat this as a priority inversion or as a frame-budget contention issue determines which fix is appropriate: raising the alert layer's composite priority addresses the former, while throttling HUD transition frequency addresses the latter. They are not the same patch.

A note on the sample

Forty sessions and 1,200 hands is enough to establish the conditional pattern with reasonable confidence and not enough to characterise rare states — multi-monitor setups, high-refresh displays, or the client's behaviour under GPU throttling were not tested. The 17.4% figure should be read as a point estimate for one configuration, not a universal constant. The conditional figures are more robust because the contrast between static and animated HUD states was large and consistent across sessions.

What players and operators can do with this

For players, the actionable finding is unglamorous: fewer docked panels and a static HUD reduce misses substantially, from roughly one in four down to roughly one in twenty-five. That is a configuration change, not a skill adjustment, and it costs nothing but a little screen real estate. Players who rely on the client's prompt rather than an external timer should treat the animated HUD as a mild liability during late-window decisions.

For operators and client teams, the finding is a reminder that overlay priority is a product decision with measurable consequences. A time-bank alert is not decorative; it is the interface's only signal that a decision is about to be made for the player. Losing it one time in six — and one time in four under common configurations — is a defect that a frame-level test would catch and a functional test would not, because the alert is present in the draw queue and absent only in the output.

Responsible-gambling tooling deserves a specific mention here. Time-bank alerts are, in part, a pacing mechanism. A client that intermittently fails to surface them is not creating harm on its own, but it is degrading the one interface element that gives a player a moment to think. That is a small thing until it is compounded across thousands of hands.

The open question

The capture establishes that the miss rate is conditional on HUD configuration and animation state, and that the effect concentrates in the final three seconds. What it cannot establish is whether the same inversion affects other time-sensitive overlays — the disconnect warning, the sit-out prompt, the tournament-break notice — which share the alert layer's compositing path. If the mechanism is frame-budget contention on a shared surface, those overlays are likely missing at similar rates, and no one has measured them. The next useful test is not another hand capture but a frame-level audit of every overlay that shares that path, run under the same animated-HUD condition that produced the 23.8% figure. Until then, the 1-in-6 number stands as a lower bound on a class of interface failures that players experience as intermittent unreliability and that the client, by design, never reports.