WIP: feat(menu): a HUD layout row, the HUD at the screen's edges or in the middle 16:9 #1152

Draft
enum wants to merge 2 commits from enum/Longshot:feat/hud-layout-row into main
First-time contributor

Type: feat · Risk: low · Tested on: Windows 11, RTX 4070 · Needs: Linux, any GPU (a build)

Why

On a screen that is not 16:9 (an ultrawide, 16:10, 4:3) the HUD's corners go to the screen's own edges since #95:
the hearts at the far left, the minimap and the item buttons at the far right. Players who want them near the middle,
as the first versions had them, have no row for it. The Ultrawide menus row moves only the pause, item and map menus,
and only the switch HOS_WIDE_UI=0 moves the HUD back. The README still says the default "keeps the HUD and movies in
the middle 16:9". #1133's reporter, on a 3440x1440 monitor, found exactly that: "none of the widescreen options
changes this view". See #1133.

What changed

A Graphics row, HUD layout, under Ultrawide menus: Screen's edges (the default, as now) or Middle 16:9
(the HUD where it is at 16:9, fitted to the width on a narrower screen, as HOS_WIDE_UI=0 does). It changes at once.
HOS_WIDE_UI, when set, still decides: the row is greyed then, and its hint says why.

  • host: hos_wide_ui_tick (host/hos_wide_ui.c) asks the row at each present (rx_option(71, 0)) when
    HOS_WIDE_UI is unset. The existing check that re-places every pane when the plan changes then moves the HUD at
    once. The switch reads as before.
  • vk: HOS_OPT_HUD_LAYOUT = 71 in gpu/vk/vk_api.h (60 is the item wheel's; 62 to 70, 80, 88 and 90 are taken by
    open pull requests, #227 among them); opts.hud_layout (0 by default, vk_menu.h), saved as hud_layout; the row, tx_hud_layout and
    hn_hud_layout in vk_menu.cpp; vk_replay.cpp's option callback answers 71; row_fixed greys the
    row while HOS_WIDE_UI holds it, as rows other switches hold are. The callback's signature is
    unchanged, so MKWVK_API_VERSION stays, as for option 61.
  • translations: the row's 7 texts in the 13 languages of gpu/vk/menu_i18n.h, each at its sorted place and with the
    counts raised. They are machine-made, as the file's others are, for speakers to correct.
  • docs: the README's feature line, its options table and its Aspect ratio text; docs/development.md's
    HOS_WIDE_UI line and options file (hud_layout).
  • tests: tests/test_hud_layout_row.py (new); tests/test_wide_ui.py's stand-ins answer rx_option for it.

Measurements

Verdict: works. On a 3440x1440 monitor, the row at Middle 16:9 moves the HUD 440 pixels in at once, to where
HOS_WIDE_UI=0 puts it, and back. At Screen's edges nothing changes from main. The new check fails on main and
passes here.

Hardware: Windows 11 Pro (26300), RTX 4070 (616.56), Ryzen 9 7900X, 64 GB; a 3440x1440 monitor
Scene: Kokiri Forest, the repository's kokiri-start save, in play; Aspect ratio 21:9, Output resolution 3440x1440,
DLSS, Frame generation 2x, Reflex, fullscreen
Method: captures of the monitor itself, the hearts' columns measured; the row changed from the Insert menu (keyboard)
and through the control bridge's option set; longshot_log.txt's wide ui: line
How to reproduce: the scene above, Insert menu > Graphics > HUD layout; python -I -B tests/run_all.py test_hud_layout_row

Before: main @ 71b1edd8 After, hud_layout=0: this PR @ 867c70b0 After, hud_layout=1: this PR @ 867c70b0
Hearts on a 3440x1440 screen (x) 116 to 261 116 to 261 556 to 701
wide ui: line, the HUD's sides moved 660 canvas units 660 0
The row changed in play (no row) (default) moves the HUD at once; back again at once
Saved (no key) hud_layout=0 hud_layout=1
HOS_WIDE_UI=1 set, the row set to Middle 16:9 (no row) refused: "the menu shows it greyed"; the HUD at the edges
tests/test_hud_layout_row.py 13 of its checks fail pass pass
run_all.py (Windows) (failures on main) 609 passed, 26 failed, 43 skipped: all 26 also fail on main

Before: main @ 71b1edd8 (Screen's edges, as this PR's default); After: this PR with HUD layout at Middle 16:9; the row in the Insert menu

== in play, the row set to Middle 16:9 and back (longshot_log.txt)
[hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 660 and its top and bottom 0 canvas units; the menus at 100%
[hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 0 and its top and bottom 0 canvas units; the menus at 100%
[hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 660 and its top and bottom 0 canvas units; the menus at 100%
== tests/test_hud_layout_row.py on main
FAIL 21:9: the row at Middle 16:9 places the HUD as HOS_WIDE_UI=0
FAIL 21:9: the row set to Middle 16:9 in play moves the HUD at once
FAIL 4:3: the row at Middle 16:9 places the HUD as HOS_WIDE_UI=0
FAIL 4:3: the row set to Middle 16:9 in play moves the HUD at once
(and the wiring: 9 checks)

Flags and settings

A new menu row and its ini key; no switch added or changed.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
hud_layout (Graphics > HUD layout) Where the HUD sits on a screen that is not 16:9 (none: the edges, or HOS_WIDE_UI=0) 0 Screen's edges (default) 1: the HUD in the middle 16:9, as HOS_WIDE_UI=0 Helps: tested at 21:9 in the game, 21:9 and 4:3 in the check Default as before (Screen's edges); Middle 16:9 for those who prefer it
HOS_WIDE_UI The existing switch 0: middle 16:9 unchanged; when set it stands over the row the same unchanged keep for testing

Testing

Tested:

  • tests/test_hud_layout_row.py compiles host/hos_wide_ui.c whole and places the HUD at 21:9 and 4:3. Middle 16:9
    matches HOS_WIDE_UI=0, Screen's edges matches the default, the switch stands over the row both ways, a change in
    play takes effect at once, and 16:9 is unmoved. It also checks the wiring (the row greyed while the switch holds it)
    and the docs. It fails on main (13 checks)
    and passes here on Windows (llvm-mingw clang) and Linux (WSL, gcc 15). test_hud_layout, test_wide_ui,
    test_menu_i18n, test_readme_menu_rows, test_menu_sections and test_preset_exempt pass on both.
  • In the game on a 3440x1440 monitor (above): the default, the row changed through the control bridge and from the
    Insert menu, back again, and hud_layout saved.
  • In the game with HOS_WIDE_UI=1: the row stays at its value and the bridge's set is refused, as the menu greys it.
  • A second agent reviewed the change cold. It found id 67 taken by open #227, so the row now uses 71, and the row not
    greyed under the switch, which it now is. It also noted that at 48:9 (three screens, the HUD on the middle one) and
    with HOS_HUD_MAX_RATIO at 16:9 or less the two choices look the same, as at 16:9; the help text names only 16:9.
    The default's behaviour, every value of HOS_WIDE_UI, the threading, the translations and the counts checked out.

Not tested: a 16:10 or 4:3 monitor in the game (covered by the check). A whole build on Linux: only
host/hos_wide_ui.c was compiled there (gcc 15, whole, by the check); the renderer's files and the game were built on
Windows.

Must be tested:

  • Linux, any GPU: a build of this branch, expecting it to compile with no new warning in host/hos_wide_ui.c,
    gpu/vk/vk_menu.cpp and gpu/vk/vk_replay.cpp; with a screen that is not 16:9, Insert menu > Graphics > HUD layout
    at Middle 16:9 moves the HUD in at once (Test Farm: @Beanstalk linux, a build of this branch and the HUD layout row)

Risks

What could break: the HUD's place on a screen that is not 16:9, only with the row at Middle 16:9. At its default
the HUD is placed as on main. The host reads one more option each present through the existing callback, as other
host files do.

Turning it off: the row's default is the behaviour before this PR; revert the commit to remove it.

Compatibility: an options file without hud_layout reads as Screen's edges, as before. An older renderer answers
unknown option ids with 0, which is also Screen's edges. Shader and pipeline caches, saves and MKWVK_API_VERSION are
unchanged.

Issues

See #1133

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Docs updated.

🤖 Generated with Claude Code

**Type:** feat · **Risk:** low · **Tested on:** Windows 11, RTX 4070 · **Needs:** Linux, any GPU (a build) ## Why On a screen that is not 16:9 (an ultrawide, 16:10, 4:3) the HUD's corners go to the screen's own edges since #95: the hearts at the far left, the minimap and the item buttons at the far right. Players who want them near the middle, as the first versions had them, have no row for it. The Ultrawide menus row moves only the pause, item and map menus, and only the switch `HOS_WIDE_UI=0` moves the HUD back. The README still says the default "keeps the HUD and movies in the middle 16:9". #1133's reporter, on a 3440x1440 monitor, found exactly that: "none of the widescreen options changes this view". See #1133. ## What changed A Graphics row, **HUD layout**, under Ultrawide menus: **Screen's edges** (the default, as now) or **Middle 16:9** (the HUD where it is at 16:9, fitted to the width on a narrower screen, as `HOS_WIDE_UI=0` does). It changes at once. `HOS_WIDE_UI`, when set, still decides: the row is greyed then, and its hint says why. - host: `hos_wide_ui_tick` (`host/hos_wide_ui.c`) asks the row at each present (`rx_option(71, 0)`) when `HOS_WIDE_UI` is unset. The existing check that re-places every pane when the plan changes then moves the HUD at once. The switch reads as before. - vk: `HOS_OPT_HUD_LAYOUT = 71` in `gpu/vk/vk_api.h` (60 is the item wheel's; 62 to 70, 80, 88 and 90 are taken by open pull requests, #227 among them); `opts.hud_layout` (0 by default, `vk_menu.h`), saved as `hud_layout`; the row, `tx_hud_layout` and `hn_hud_layout` in `vk_menu.cpp`; `vk_replay.cpp`'s option callback answers 71; `row_fixed` greys the row while `HOS_WIDE_UI` holds it, as rows other switches hold are. The callback's signature is unchanged, so `MKWVK_API_VERSION` stays, as for option 61. - translations: the row's 7 texts in the 13 languages of `gpu/vk/menu_i18n.h`, each at its sorted place and with the counts raised. They are machine-made, as the file's others are, for speakers to correct. - docs: the README's feature line, its options table and its Aspect ratio text; `docs/development.md`'s `HOS_WIDE_UI` line and options file (`hud_layout`). - tests: `tests/test_hud_layout_row.py` (new); `tests/test_wide_ui.py`'s stand-ins answer `rx_option` for it. ## Measurements **Verdict:** works. On a 3440x1440 monitor, the row at Middle 16:9 moves the HUD 440 pixels in at once, to where `HOS_WIDE_UI=0` puts it, and back. At Screen's edges nothing changes from `main`. The new check fails on `main` and passes here. Hardware: Windows 11 Pro (26300), RTX 4070 (616.56), Ryzen 9 7900X, 64 GB; a 3440x1440 monitor Scene: Kokiri Forest, the repository's `kokiri-start` save, in play; Aspect ratio 21:9, Output resolution 3440x1440, DLSS, Frame generation 2x, Reflex, fullscreen Method: captures of the monitor itself, the hearts' columns measured; the row changed from the Insert menu (keyboard) and through the control bridge's `option set`; `longshot_log.txt`'s `wide ui:` line How to reproduce: the scene above, Insert menu > Graphics > HUD layout; `python -I -B tests/run_all.py test_hud_layout_row` | | Before: main @ 71b1edd8 | After, hud_layout=0: this PR @ 867c70b0 | After, hud_layout=1: this PR @ 867c70b0 | |---|---|---|---| | Hearts on a 3440x1440 screen (x) | 116 to 261 | 116 to 261 | 556 to 701 | | `wide ui:` line, the HUD's sides moved | 660 canvas units | 660 | 0 | | The row changed in play | (no row) | (default) | moves the HUD at once; back again at once | | Saved | (no key) | `hud_layout=0` | `hud_layout=1` | | `HOS_WIDE_UI=1` set, the row set to Middle 16:9 | (no row) | refused: "the menu shows it greyed"; the HUD at the edges | | | `tests/test_hud_layout_row.py` | 13 of its checks fail | pass | pass | | `run_all.py` (Windows) | (failures on main) | 609 passed, 26 failed, 43 skipped: all 26 also fail on main | | ![Before: main @ 71b1edd8 (Screen's edges, as this PR's default); After: this PR with HUD layout at Middle 16:9; the row in the Insert menu](https://git.magicbean.dev/attachments/eb351c5a-8bf0-4109-991c-b407ce98076b) ``` == in play, the row set to Middle 16:9 and back (longshot_log.txt) [hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 660 and its top and bottom 0 canvas units; the menus at 100% [hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 0 and its top and bottom 0 canvas units; the menus at 100% [hos host] wide ui: picture 2.3889: the HUD at 100% of its 16:9 size, its sides moved 660 and its top and bottom 0 canvas units; the menus at 100% == tests/test_hud_layout_row.py on main FAIL 21:9: the row at Middle 16:9 places the HUD as HOS_WIDE_UI=0 FAIL 21:9: the row set to Middle 16:9 in play moves the HUD at once FAIL 4:3: the row at Middle 16:9 places the HUD as HOS_WIDE_UI=0 FAIL 4:3: the row set to Middle 16:9 in play moves the HUD at once (and the wiring: 9 checks) ``` ### Flags and settings A new menu row and its ini key; no switch added or changed. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `hud_layout` (Graphics > HUD layout) | Where the HUD sits on a screen that is not 16:9 | (none: the edges, or `HOS_WIDE_UI=0`) | 0 Screen's edges (default) | 1: the HUD in the middle 16:9, as `HOS_WIDE_UI=0` | Helps: tested at 21:9 in the game, 21:9 and 4:3 in the check | Default as before (Screen's edges); Middle 16:9 for those who prefer it | | `HOS_WIDE_UI` | The existing switch | 0: middle 16:9 | unchanged; when set it stands over the row | the same | unchanged | keep for testing | ## Testing **Tested:** - `tests/test_hud_layout_row.py` compiles `host/hos_wide_ui.c` whole and places the HUD at 21:9 and 4:3. Middle 16:9 matches `HOS_WIDE_UI=0`, Screen's edges matches the default, the switch stands over the row both ways, a change in play takes effect at once, and 16:9 is unmoved. It also checks the wiring (the row greyed while the switch holds it) and the docs. It fails on `main` (13 checks) and passes here on Windows (llvm-mingw clang) and Linux (WSL, gcc 15). `test_hud_layout`, `test_wide_ui`, `test_menu_i18n`, `test_readme_menu_rows`, `test_menu_sections` and `test_preset_exempt` pass on both. - In the game on a 3440x1440 monitor (above): the default, the row changed through the control bridge and from the Insert menu, back again, and `hud_layout` saved. - In the game with `HOS_WIDE_UI=1`: the row stays at its value and the bridge's set is refused, as the menu greys it. - A second agent reviewed the change cold. It found id 67 taken by open #227, so the row now uses 71, and the row not greyed under the switch, which it now is. It also noted that at 48:9 (three screens, the HUD on the middle one) and with `HOS_HUD_MAX_RATIO` at 16:9 or less the two choices look the same, as at 16:9; the help text names only 16:9. The default's behaviour, every value of `HOS_WIDE_UI`, the threading, the translations and the counts checked out. **Not tested:** a 16:10 or 4:3 monitor in the game (covered by the check). A whole build on Linux: only `host/hos_wide_ui.c` was compiled there (gcc 15, whole, by the check); the renderer's files and the game were built on Windows. **Must be tested:** - Linux, any GPU: a build of this branch, expecting it to compile with no new warning in `host/hos_wide_ui.c`, `gpu/vk/vk_menu.cpp` and `gpu/vk/vk_replay.cpp`; with a screen that is not 16:9, Insert menu > Graphics > HUD layout at Middle 16:9 moves the HUD in at once (Test Farm: @Beanstalk linux, a build of this branch and the HUD layout row) ## Risks **What could break:** the HUD's place on a screen that is not 16:9, only with the row at Middle 16:9. At its default the HUD is placed as on `main`. The host reads one more option each present through the existing callback, as other host files do. **Turning it off:** the row's default is the behaviour before this PR; revert the commit to remove it. **Compatibility:** an options file without `hud_layout` reads as Screen's edges, as before. An older renderer answers unknown option ids with 0, which is also Screen's edges. Shader and pipeline caches, saves and `MKWVK_API_VERSION` are unchanged. ## Issues See #1133 ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
On a screen that is not 16:9 the HUD's corners go to the screen's edges (#95);
only the switch HOS_WIDE_UI=0 keeps it in the middle 16:9, as the first
versions had it, and no menu row moves it: #1133's ultrawide player found the
Ultrawide menus row moving only the menus.

tests/test_hud_layout_row.py compiles host/hos_wide_ui.c whole and checks a
Graphics row, HUD layout: Middle 16:9 places the HUD at 21:9 and 4:3 as
HOS_WIDE_UI=0 does, Screen's edges as before, the switch over the row either
way, a change in play at once; and its wiring: option 71, hud_layout, the row
fixed while HOS_WIDE_UI holds it, the README and the options file's docs.
tests/test_wide_ui.py's stand-ins answer rx_option for it. On main 13 of its
checks fail.

Assisted-by: Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
feat(menu): a HUD layout row, the HUD at the screen's edges or in the middle 16:9 (#1133)
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 4s
867c70b08d
On a screen that is not 16:9 the HUD's corners go to the screen's edges since
#95, and only the switch HOS_WIDE_UI=0 kept it in the middle 16:9: no row of
the menu moved it, and the README still said the default kept it there. An
ultrawide player (#1133) found the Ultrawide menus row moving only the menus.

The Graphics tab's HUD layout row, after Ultrawide menus: Screen's edges (0,
the default, as before) or Middle 16:9 (1, as HOS_WIDE_UI=0: on a narrower
screen fitted to its width). Saved as hud_layout; option 71
(HOS_OPT_HUD_LAYOUT; 60 is the item wheel's, 62 to 70, 80, 88 and 90 open pull
requests') answers it, and host/hos_wide_ui.c reads it at each present, so a
change shows at once. HOS_WIDE_UI, when set, still decides: the row is fixed
then (row_fixed), and its hint says why. The row's texts in the 13 languages
of gpu/vk/menu_i18n.h (machine-made, as the others). The README's feature
line, its options table and its Aspect ratio text, and docs/development.md's
switch and options file, say what it does.

Assisted-by: Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
First-time contributor

Tested in game: Windows 11 Pro (26300), RTX 4070, NVIDIA 616.56, on a 3440x1440 monitor in fullscreen (21:9, 3440x1440, DLSS, DLSS FG 2x, Reflex), Kokiri Forest on the kokiri-start save: HUD layout at Screen's edges places the HUD as main (hearts x 116); set to Middle 16:9 from the Insert menu (keyboard) and through the control bridge, the HUD moves in at once (hearts x 556, the wide ui line's sides 660 -> 0) and back; saved as hud_layout=1. With HOS_WIDE_UI=1 set the row is greyed: the bridge's set is refused and the HUD stays at the edges.

Tested in game: Windows 11 Pro (26300), RTX 4070, NVIDIA 616.56, on a 3440x1440 monitor in fullscreen (21:9, 3440x1440, DLSS, DLSS FG 2x, Reflex), Kokiri Forest on the kokiri-start save: HUD layout at Screen's edges places the HUD as main (hearts x 116); set to Middle 16:9 from the Insert menu (keyboard) and through the control bridge, the HUD moves in at once (hearts x 556, the wide ui line's sides 660 -> 0) and back; saved as hud_layout=1. With HOS_WIDE_UI=1 set the row is greyed: the bridge's set is refused and the HUD stays at the edges.
Author
First-time contributor

@Beanstalk linux, any GPU: build this branch (make_game.py or a dev pack) and say whether host/hos_wide_ui.c, gpu/vk/vk_menu.cpp and gpu/vk/vk_replay.cpp compile with no new warning. If a game folder and a screen that isn't 16:9 are at hand: Insert menu > Graphics > HUD layout set to Middle 16:9 should move the hearts, buttons and minimap into the middle 16:9 at once, and Screen's edges back.

@Beanstalk linux, any GPU: build this branch (make_game.py or a dev pack) and say whether host/hos_wide_ui.c, gpu/vk/vk_menu.cpp and gpu/vk/vk_replay.cpp compile with no new warning. If a game folder and a screen that isn't 16:9 are at hand: Insert menu > Graphics > HUD layout set to Middle 16:9 should move the hearts, buttons and minimap into the middle 16:9 at once, and Screen's edges back.
Member

@enum only members of BigBeans can start the farm. One of them can approve this request by reacting 👍 to it.

@enum only members of `BigBeans` can start the farm. One of them can approve this request by reacting 👍 to it.
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 4s
This pull request is marked as a work in progress.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'feat/hud-layout-row:enum-feat/hud-layout-row'
git switch 'enum-feat/hud-layout-row'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1152
No description provided.