Description
In the Preflop Lab (00 · PREFLOP LAB tab), BTN's decision node shows
the exact same action-mix split across every single hand in the 13x13
strategy grid, regardless of hand strength.
Observed with BTN's node in an unraised pot (all earlier seats folded):
every cell showed Fold 33% / Raise 3 33% / All-in 150 33% — including
clearly-wrong cases like 72o and 32s showing 33% "All-in 150" frequency,
and AA showing the same 33% fold frequency as 72o.
This is not limited to the unopened-pot node — the same uniform-grid
pattern also appears on BTN's node after an open, and after a 3-bet.
By contrast, all other seats (UTG, UTG1, MP, HJ, CO) render correctly
in the same solve, with properly varied, hand-differentiated frequencies
(premium hands mostly raise, weak hands mostly fold). This suggests the
bug is specific to BTN, not a general rendering issue affecting all seats.
Steps to reproduce
- Set up an 8-max 150bb scenario (limps + antes), build the game
- Solve to convergence (or even mid-solve)
- In BROWSE / the action ribbon, walk to BTN's decision node in each
of these situations:
a. Unraised pot (all earlier seats folded, BTN first to act), OR
b. Facing an open (someone before BTN raises), OR
c. Facing a 3-bet (someone re-raises before BTN acts)
- Observe the 13x13 grid for BTN — every cell shows the identical
action-mix split, regardless of hand, in each of these cases
- For comparison, check UTG/UTG1/MP/HJ/CO nodes in the same solve —
these render correctly with hand-differentiated frequencies
Expected behavior
BTN's grid should reflect each hand's actual computed strategy
frequencies, matching the pattern seen on all other seats in the same
solve.
Suspected cause
BTN's grid may be displaying an aggregate/header-level stat (the same
numbers shown in the ribbon above the grid, e.g. "Fold 33% / Raise 3 33%
/ All-in 150 33%") repeated across every cell, rather than pulling each
hand's individual combo-level data. Since other seats are unaffected,
this may point to something specific to how BTN's node data is indexed
or fetched (e.g. an off-by-one seat index, or BTN defaulting to a
placeholder/aggregate value) rather than a general grid-rendering bug.
Screenshots
Environment
- OS: [your OS]
- Build: [CPU-only or GPU build, if known]
- Scenario: 8-max 150bb, limps + antes, rake 4%/cap 5bb, 3bb opens,
3-4x re-raises, max 3 raises
Description
In the Preflop Lab (00 · PREFLOP LAB tab), BTN's decision node shows
the exact same action-mix split across every single hand in the 13x13
strategy grid, regardless of hand strength.
Observed with BTN's node in an unraised pot (all earlier seats folded):
every cell showed Fold 33% / Raise 3 33% / All-in 150 33% — including
clearly-wrong cases like 72o and 32s showing 33% "All-in 150" frequency,
and AA showing the same 33% fold frequency as 72o.
This is not limited to the unopened-pot node — the same uniform-grid
pattern also appears on BTN's node after an open, and after a 3-bet.
By contrast, all other seats (UTG, UTG1, MP, HJ, CO) render correctly
in the same solve, with properly varied, hand-differentiated frequencies
(premium hands mostly raise, weak hands mostly fold). This suggests the
bug is specific to BTN, not a general rendering issue affecting all seats.
Steps to reproduce
of these situations:
a. Unraised pot (all earlier seats folded, BTN first to act), OR
b. Facing an open (someone before BTN raises), OR
c. Facing a 3-bet (someone re-raises before BTN acts)
action-mix split, regardless of hand, in each of these cases
these render correctly with hand-differentiated frequencies
Expected behavior
BTN's grid should reflect each hand's actual computed strategy
frequencies, matching the pattern seen on all other seats in the same
solve.
Suspected cause
BTN's grid may be displaying an aggregate/header-level stat (the same
numbers shown in the ribbon above the grid, e.g. "Fold 33% / Raise 3 33%
/ All-in 150 33%") repeated across every cell, rather than pulling each
hand's individual combo-level data. Since other seats are unaffected,
this may point to something specific to how BTN's node data is indexed
or fetched (e.g. an off-by-one seat index, or BTN defaulting to a
placeholder/aggregate value) rather than a general grid-rendering bug.
Screenshots
Environment
3-4x re-raises, max 3 raises