docs(website): refresh system requirements and AMD status #1054

Merged
llun merged 7 commits from bibiburl/Longshot:docs/requirements-audit into main 2026-11-16 06:24:59 +00:00
Member

Type: docs · Risk: low · Tested on: Linux, Chromium 153 (website only) · Needs: none

Why

The AMD project-status row is too technical for a quick compatibility check, omits the Linux fallback default, and links to old Hookshot reports that are no longer accessible.

The recommended hardware should allow more headroom while keeping the existing simple requirements table. These are estimates, not hardware qualification or a 60 fps guarantee.

The requirements page still says the Linux AppImage requires AVX2, despite #574 removing that restriction. It also promises steady 60 fps for specific CPUs without enough evidence, and suggests a 6 GB quality preset for a 4 GB card.

What changed

Keep the existing Minimum/Recommended table and surrounding wording, raise the recommended hardware, and make the README and Getting Started agree with the website.

  • Shorten the README’s AMD project-status row: mention automatic rendering workarounds on affected Windows cards and AMD GPUs on Linux; link current RX 6600 and Radeon 860M reports plus the existing developer details.
  • Recommended CPU: Ryzen 7 7800X3D or Core i5-13600K.
  • Recommended GPU: RTX 4070 or RX 7800 XT, with 12 GB or more VRAM.
  • Recommended RAM: 32 GB or more; the minimum remains 16 GB.
  • Remove Intel Arc examples from both minimum graphics and recommended mesh-shader rows. Keep the other minimum hardware, operating systems and storage unchanged.
  • Correct the AVX2 wording for current builds (v3.0.0-rc.4 or newer), remove the unsupported steady-60-fps sentence, and recommend Minimum (4GB) for a 4 GB card.

Only three documentation files differ from main: README (requirements and AMD project status), the requirements page, and the short memory recommendation in Getting Started. No layout, runtime, tests or new audit document.

Evidence and developer guidance

AMD status was checked against the Windows device rule in gpu/vk/mesh_mode.h, the Linux default in gpu/vk/vk_main.cpp, merged #219, and current reports #933 and #1040. #975 is merged but still lists RX 6600 gameplay verification as pending, so the row does not claim the slowdown is fixed. The detailed fallback rules already remain in docs/development.md; no new technical section is added.

The tested configurations catalogue records runs using the named CPUs and GPUs. This establishes that these configurations have been exercised, not that they are equivalent or guarantee a frame rate. The 7800X3D results are specific stationary scenes; RTX 4070 and RX 7800 XT records include correctness tests rather than a matched performance comparison. The 13600K test report is likewise build-, scene- and settings-specific.

The 32 GB recommendation leaves room for the recorded roughly 13–19 GiB game-memory use and the operating system. The 12 GB VRAM recommendation gives more headroom than the old 8 GB recommendation. These remain editorial estimates; no new benchmark qualification is claimed.

The developer hardware support tiers still include lower-end hardware. Those are support priorities, not recommended performance tiers. This PR does not remove that support. The runtime's “16GB RAM or more recommended” warning remains compatible with recommending 32 GB for headroom, and the direct Getting Started recommendation is updated to match. The project-status link remains available for known hardware issues; removing Arc from the examples does not change runtime compatibility.

Measurements

Verdict: documentation only; no gameplay measurements. Existing presentation retained and the two requirements copies checked for matching content.

Flags and settings

None.

Testing

Tested: main bbe421f5 against 73dd846d, with the final requirements wording rebuilt and visually checked at 1ee97b9a:

  • Website build: 19 pages; all 1,067 local links/assets and their anchors/edit links pass.
  • Website tests: 101 pass / 1 fail on both. Existing failure: graphics-settings.test.ts, HDR Native condition accepts current prose but remains required.
  • Game-free suite: 571 pass / 12 fail / 80 skipped on both; the same failing files are listed below.
  • Requirements text matches between README and website, allowing their existing link destinations. Git diff confirms only the three documentation files described above changed.
  • Final requirements wording: website build/check and requirements-copy parity rechecked. The game-free suite was not rerun for removing GPU examples; the results above apply to the preceding documentation commit.
  • Full-page requirements screenshots at 1440 px and 390 px in both themes remain current: the AMD-row follow-up does not change that page.
  • AMD status wording at 2c48449a: rebuilt the website and rechecked local links/tests; rendered README screenshots below. The same existing HDR test failure remains. No additional game-free suite or gameplay run for this prose-only follow-up.

Not tested: game performance, new hardware or Windows execution; this PR makes no new benchmark claim.

Must be tested: None for these documentation corrections.

Existing game-free failures on both sides
  • tests/test_bug_report_defaults.py
  • tests/test_crt_options.py
  • tests/test_guest_imported.py
  • tests/test_linux_preflight.py
  • tests/test_linux_update.py
  • tests/test_make_game_cache.py
  • tests/test_missing_nup.py
  • tests/test_mods_size_table.py
  • tests/test_pending_guest_import.py
  • tests/test_run_all_changed.py
  • tests/test_vk_occlusion_queries.py
  • tests/test_walk_key.py

Risks

What could break: wording could become outdated as builds change.

Turning it off: revert the change.

Compatibility: Nothing changes in the game, saves, settings or dependencies. The normal website workflow publishes the text after merge.

Issues

See #574 for the AVX2 change and #104 for the original requirements table. The revised hardware estimates remain estimates; this PR does not qualify a new performance tier.

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.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • Docs updated.

Screenshots

Current requirements page, with Intel Arc removed from every row.

Current: desktop, light

After: this PR @ 1ee97b9a — desktop, light

After: this PR @ 1ee97b9a, desktop, light

Current: desktop, dark

After: this PR @ 1ee97b9a — desktop, dark

After: this PR @ 1ee97b9a, desktop, dark

Current: phone, light

After: this PR @ 1ee97b9a — phone, light

After: this PR @ 1ee97b9a, phone, light

Current: phone, dark

After: this PR @ 1ee97b9a — phone, dark

After: this PR @ 1ee97b9a, phone, dark

Historical comparison only — old main before this PR (superseded specs)

Before: main @ bbe421f5 — desktop, light

Before: main @ bbe421f5, desktop, light

Before: main @ bbe421f5 — desktop, dark

Before: main @ bbe421f5, desktop, dark

Before: main @ bbe421f5 — phone, light

Before: main @ bbe421f5, phone, light

Before: main @ bbe421f5 — phone, dark

Before: main @ bbe421f5, phone, dark

AMD status comparison

Local Markdown renderings of the README row, using the same presentation for before and after. These show the source wording, not a screenshot of the Forgejo interface. Requirements-page screenshots above are unchanged.

AMD row: desktop, light — current and previous

Local README comparison: After 2c48449a; Before bbe421f5; desktop, light

AMD row: desktop, dark — current and previous

Local README comparison: After 2c48449a; Before bbe421f5; desktop, dark

AMD row: phone, light — current and previous

Local README comparison: After 2c48449a; Before bbe421f5; phone, light

AMD row: phone, dark — current and previous

Local README comparison: After 2c48449a; Before bbe421f5; phone, dark

**Type:** docs · **Risk:** low · **Tested on:** Linux, Chromium 153 (website only) · **Needs:** none ## Why The AMD project-status row is too technical for a quick compatibility check, omits the Linux fallback default, and links to old Hookshot reports that are no longer accessible. The recommended hardware should allow more headroom while keeping the existing simple requirements table. These are estimates, not hardware qualification or a 60 fps guarantee. The requirements page still says the Linux AppImage requires AVX2, despite #574 removing that restriction. It also promises steady 60 fps for specific CPUs without enough evidence, and suggests a 6 GB quality preset for a 4 GB card. ## What changed Keep the existing Minimum/Recommended table and surrounding wording, raise the recommended hardware, and make the README and Getting Started agree with the website. - Shorten the README’s AMD project-status row: mention automatic rendering workarounds on affected Windows cards and AMD GPUs on Linux; link current RX 6600 and Radeon 860M reports plus the existing developer details. - Recommended CPU: Ryzen 7 7800X3D or Core i5-13600K. - Recommended GPU: RTX 4070 or RX 7800 XT, with 12 GB or more VRAM. - Recommended RAM: 32 GB or more; the minimum remains 16 GB. - Remove Intel Arc examples from both minimum graphics and recommended mesh-shader rows. Keep the other minimum hardware, operating systems and storage unchanged. - Correct the AVX2 wording for current builds (v3.0.0-rc.4 or newer), remove the unsupported steady-60-fps sentence, and recommend Minimum (4GB) for a 4 GB card. Only three documentation files differ from main: README (requirements and AMD project status), the requirements page, and the short memory recommendation in Getting Started. No layout, runtime, tests or new audit document. ### Evidence and developer guidance AMD status was checked against the Windows device rule in `gpu/vk/mesh_mode.h`, the Linux default in `gpu/vk/vk_main.cpp`, merged #219, and current reports #933 and #1040. #975 is merged but still lists RX 6600 gameplay verification as pending, so the row does not claim the slowdown is fixed. The detailed fallback rules already remain in `docs/development.md`; no new technical section is added. The [tested configurations catalogue](https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/bbe421f508a3aa6c32014265067a5031ef333b32/docs/tested-configurations.md) records runs using the named CPUs and GPUs. This establishes that these configurations have been exercised, not that they are equivalent or guarantee a frame rate. The 7800X3D results are specific stationary scenes; RTX 4070 and RX 7800 XT records include correctness tests rather than a matched performance comparison. The [13600K test report](https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/bbe421f508a3aa6c32014265067a5031ef333b32/docs/tested/2026-11-15-rt-pin-nyannoying-ps1.md) is likewise build-, scene- and settings-specific. The 32 GB recommendation leaves room for the recorded roughly 13–19 GiB game-memory use and the operating system. The 12 GB VRAM recommendation gives more headroom than the old 8 GB recommendation. These remain editorial estimates; no new benchmark qualification is claimed. The developer [hardware support tiers](https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/bbe421f508a3aa6c32014265067a5031ef333b32/docs/workflow.md) still include lower-end hardware. Those are support priorities, not recommended performance tiers. This PR does not remove that support. The runtime's “16GB RAM or more recommended” warning remains compatible with recommending 32 GB for headroom, and the direct Getting Started recommendation is updated to match. The project-status link remains available for known hardware issues; removing Arc from the examples does not change runtime compatibility. ## Measurements **Verdict:** documentation only; no gameplay measurements. Existing presentation retained and the two requirements copies checked for matching content. ### Flags and settings None. ## Testing **Tested:** main `bbe421f5` against `73dd846d`, with the final requirements wording rebuilt and visually checked at `1ee97b9a`: - Website build: 19 pages; all 1,067 local links/assets and their anchors/edit links pass. - Website tests: 101 pass / 1 fail on both. Existing failure: `graphics-settings.test.ts`, `HDR Native condition accepts current prose but remains required`. - Game-free suite: 571 pass / 12 fail / 80 skipped on both; the same failing files are listed below. - Requirements text matches between README and website, allowing their existing link destinations. Git diff confirms only the three documentation files described above changed. - Final requirements wording: website build/check and requirements-copy parity rechecked. The game-free suite was not rerun for removing GPU examples; the results above apply to the preceding documentation commit. - Full-page requirements screenshots at 1440 px and 390 px in both themes remain current: the AMD-row follow-up does not change that page. - AMD status wording at `2c48449a`: rebuilt the website and rechecked local links/tests; rendered README screenshots below. The same existing HDR test failure remains. No additional game-free suite or gameplay run for this prose-only follow-up. **Not tested:** game performance, new hardware or Windows execution; this PR makes no new benchmark claim. **Must be tested:** None for these documentation corrections. <details> <summary>Existing game-free failures on both sides</summary> - `tests/test_bug_report_defaults.py` - `tests/test_crt_options.py` - `tests/test_guest_imported.py` - `tests/test_linux_preflight.py` - `tests/test_linux_update.py` - `tests/test_make_game_cache.py` - `tests/test_missing_nup.py` - `tests/test_mods_size_table.py` - `tests/test_pending_guest_import.py` - `tests/test_run_all_changed.py` - `tests/test_vk_occlusion_queries.py` - `tests/test_walk_key.py` </details> ## Risks **What could break:** wording could become outdated as builds change. **Turning it off:** revert the change. **Compatibility:** Nothing changes in the game, saves, settings or dependencies. The normal website workflow publishes the text after merge. ## Issues See #574 for the AVX2 change and #104 for the original requirements table. The revised hardware estimates remain estimates; this PR does not qualify a new performance tier. ## 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] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] Docs updated. ## Screenshots Current requirements page, with Intel Arc removed from every row. ### Current: desktop, light **After: this PR @ 1ee97b9a — desktop, light** ![After: this PR @ 1ee97b9a, desktop, light](https://git.magicbean.dev/attachments/17001695-7cba-4ee0-9c2e-9028c45c71ab) ### Current: desktop, dark **After: this PR @ 1ee97b9a — desktop, dark** ![After: this PR @ 1ee97b9a, desktop, dark](https://git.magicbean.dev/attachments/a32aeee5-8415-4ed1-b0bf-37b9862bee4b) ### Current: phone, light **After: this PR @ 1ee97b9a — phone, light** ![After: this PR @ 1ee97b9a, phone, light](https://git.magicbean.dev/attachments/24f55b0e-6902-4dcb-bce0-3bdd8f210fa5) ### Current: phone, dark **After: this PR @ 1ee97b9a — phone, dark** ![After: this PR @ 1ee97b9a, phone, dark](https://git.magicbean.dev/attachments/725c0503-c38b-4aca-aba4-0add830f0119) <details> <summary>Historical comparison only — old main before this PR (superseded specs)</summary> **Before: main @ bbe421f5 — desktop, light** ![Before: main @ bbe421f5, desktop, light](https://git.magicbean.dev/attachments/8851f1fc-8e88-4fc2-9a92-127f2a7d1eee) **Before: main @ bbe421f5 — desktop, dark** ![Before: main @ bbe421f5, desktop, dark](https://git.magicbean.dev/attachments/562fa8be-d472-4708-8fd2-1c98e675b7de) **Before: main @ bbe421f5 — phone, light** ![Before: main @ bbe421f5, phone, light](https://git.magicbean.dev/attachments/7a769f36-aa1f-4809-a37e-c7d2c75cb540) **Before: main @ bbe421f5 — phone, dark** ![Before: main @ bbe421f5, phone, dark](https://git.magicbean.dev/attachments/e849b984-45a0-49f6-bd92-adbe5b8d6eb7) </details> ## AMD status comparison Local Markdown renderings of the README row, using the same presentation for before and after. These show the source wording, not a screenshot of the Forgejo interface. Requirements-page screenshots above are unchanged. <details> <summary>AMD row: desktop, light — current and previous</summary> ![Local README comparison: After 2c48449a; Before bbe421f5; desktop, light](https://git.magicbean.dev/attachments/2b7a1fbd-20b2-49d3-805d-48c92ac266ce) </details> <details> <summary>AMD row: desktop, dark — current and previous</summary> ![Local README comparison: After 2c48449a; Before bbe421f5; desktop, dark](https://git.magicbean.dev/attachments/959ae472-87a7-41d9-8edc-a2c1b7712f50) </details> <details> <summary>AMD row: phone, light — current and previous</summary> ![Local README comparison: After 2c48449a; Before bbe421f5; phone, light](https://git.magicbean.dev/attachments/ca90b7e9-6a77-4fae-95ff-be04db587961) </details> <details> <summary>AMD row: phone, dark — current and previous</summary> ![Local README comparison: After 2c48449a; Before bbe421f5; phone, dark](https://git.magicbean.dev/attachments/84beac34-4a8f-4f19-b8fb-0f99bf17ac09) </details>
Assisted-by: Codex (OpenAI)
docs(website): ground system requirements in current evidence
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 6s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 13s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 16s
67694d7b4b
Assisted-by: Codex (OpenAI)
Author
Member

Requirements audit complete: source/history and RC ancestry checked, outdated claims corrected, and before/after light/dark desktop and phone screenshots added to the main post. The 19-page website build and link checks pass; the new parity test passes after reproducing the AVX2 mismatch on main. Website and game-free suites have only the same failures as main, listed in the description. No gameplay performance or hardware-qualification claim.

Requirements audit complete: source/history and RC ancestry checked, outdated claims corrected, and before/after light/dark desktop and phone screenshots added to the main post. The 19-page website build and link checks pass; the new parity test passes after reproducing the AVX2 mismatch on main. Website and game-free suites have only the same failures as main, listed in the description. No gameplay performance or hardware-qualification claim.
bibiburl changed title from WIP: docs(website): validate system requirements against current evidence to docs(website): validate system requirements against current evidence 2026-11-16 05:16:17 +00:00
docs(website): keep requirements changes limited to existing spec rows
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 16s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Third-party parts / As their notes say (pull_request) Successful in 20s
PR description / Description follows the template (pull_request_target) Successful in 6s
b0b82e9924
Assisted-by: Codex (OpenAI)
bibiburl changed title from docs(website): validate system requirements against current evidence to docs(website): correct CPU and VRAM guidance 2026-11-16 05:25:51 +00:00
Author
Member

Reduced to the requested spec-only update: original Minimum/Recommended layout and surrounding text restored. Only the CPU and VRAM rows change in the website and matching README: current builds no longer need AVX2, the unsupported steady-60-fps CPU sentence is removed, and a 4 GB card uses Minimum (4GB). The other documentation changes, added test and audit document are removed. Main-post screenshots now show this version. Build and link checks pass; website and game-free failures are unchanged from main.

Reduced to the requested spec-only update: original Minimum/Recommended layout and surrounding text restored. Only the CPU and VRAM rows change in the website and matching README: current builds no longer need AVX2, the unsupported steady-60-fps CPU sentence is removed, and a 4 GB card uses Minimum (4GB). The other documentation changes, added test and audit document are removed. Main-post screenshots now show this version. Build and link checks pass; website and game-free failures are unchanged from main.
docs(website): raise recommended hardware for more headroom
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 6s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 9s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 14s
PR description / Description follows the template (pull_request_target) Successful in 7s
73dd846d2f
Assisted-by: Codex (OpenAI)
bibiburl changed title from docs(website): correct CPU and VRAM guidance to docs(website): raise recommended hardware and correct requirements 2026-11-16 05:42:36 +00:00
Author
Member

Raised the recommended CPU/GPU and memory specifications in 73dd846d, keeping the original table and minimum hardware. README, website and Getting Started now agree. The description records the test evidence and its limits: these are headroom estimates, not a 60 fps guarantee. Fresh full-page desktop/phone screenshots in both themes replace the previous after captures. Website build and link checks pass; website and game-free test failures match main.

Raised the recommended CPU/GPU and memory specifications in 73dd846d, keeping the original table and minimum hardware. README, website and Getting Started now agree. The description records the test evidence and its limits: these are headroom estimates, not a 60 fps guarantee. Fresh full-page desktop/phone screenshots in both themes replace the previous after captures. Website build and link checks pass; website and game-free test failures match main.
docs(website): limit recommended GPUs to RTX 4070 and RX 7800 XT
Some checks failed
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 17s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Third-party parts / As their notes say (pull_request) Successful in 21s
PR description / Description follows the template (pull_request_target) Successful in 3s
831520522f
Assisted-by: Codex (OpenAI)
Author
Member

Updated 83152052 to the requested recommended specs: Ryzen 7 7800X3D or Core i5-13600K; RTX 4070 or RX 7800 XT; 12 GB+ VRAM and 32 GB+ RAM. Removed Arc B580 from the recommendation in both copies. Refreshed screenshots; website build and link checks pass, with the same existing HDR test failure. Layout and minimum hardware are unchanged.

Updated 83152052 to the requested recommended specs: Ryzen 7 7800X3D or Core i5-13600K; RTX 4070 or RX 7800 XT; 12 GB+ VRAM and 32 GB+ RAM. Removed Arc B580 from the recommendation in both copies. Refreshed screenshots; website build and link checks pass, with the same existing HDR test failure. Layout and minimum hardware are unchanged.
Author
Member

Put current screenshots first and collapsed the clearly labelled previous versions. The recommended GPU row shows RTX 4070 or RX 7800 XT. Intel Arc references remain in minimum hardware and mesh-shader support, which were unchanged.

Put current screenshots first and collapsed the clearly labelled previous versions. The recommended GPU row shows RTX 4070 or RX 7800 XT. Intel Arc references remain in minimum hardware and mesh-shader support, which were unchanged.
docs(website): remove Intel Arc from requirements examples
Some checks failed
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 17s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Third-party parts / As their notes say (pull_request) Successful in 19s
PR description / Description follows the template (pull_request_target) Successful in 9s
1ee97b9ac5
Assisted-by: Codex (OpenAI)
Author
Member

Removed Intel Arc from the requirements table entirely in 1ee97b9a: no Arc A380 minimum example and no Arc mention in the mesh-shader row. Updated the matching README section and all four current screenshots. Confirmed rendered requirements contain no Intel Arc text. Website build and link checks pass; the same existing HDR test failure remains.

Removed Intel Arc from the requirements table entirely in 1ee97b9a: no Arc A380 minimum example and no Arc mention in the mesh-shader row. Updated the matching README section and all four current screenshots. Confirmed rendered requirements contain no Intel Arc text. Website build and link checks pass; the same existing HDR test failure remains.
docs(website): refresh AMD project status guidance
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 13s
Third-party parts / As their notes say (pull_request) Successful in 18s
PR description / Description follows the template (pull_request_target) Successful in 5s
2c48449a36
Assisted-by: Codex (OpenAI)
bibiburl changed title from docs(website): raise recommended hardware and correct requirements to docs(website): refresh system requirements and AMD status 2026-11-16 06:20:04 +00:00
Author
Member

Added the AMD project-status refresh in 2c48449a. The row is shorter, mentions automatic Windows/Linux rendering workarounds, links current RX 6600 and Radeon 860M reports, and points to existing technical details. It does not claim the remaining issues are fixed. Website build and all 1,067 local link/asset checks pass; website tests retain the same existing HDR failure (101 pass / 1 fail). Added labelled local README before/after renders; the requirements screenshots remain unchanged.

Added the AMD project-status refresh in 2c48449a. The row is shorter, mentions automatic Windows/Linux rendering workarounds, links current RX 6600 and Radeon 860M reports, and points to existing technical details. It does not claim the remaining issues are fixed. Website build and all 1,067 local link/asset checks pass; website tests retain the same existing HDR failure (101 pass / 1 fail). Added labelled local README before/after renders; the requirements screenshots remain unchanged.
llun approved these changes 2026-11-16 06:24:46 +00:00
llun merged commit 2404555fdb into main 2026-11-16 06:24:59 +00:00
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!1054
No description provided.