feat(graphics): extend the FOV slider to 300 percent #199

Open

brunobaccari wants to merge 3 commits from brunobaccari/Longshot:feat/longshot-fov-range-300 into main

pull from: brunobaccari/Longshot:feat/longshot-fov-range-300

merge into: MagicBeanDev:main

MagicBeanDev:main

Conversation 7 Commits 3 Files changed 7 +17 -9

brunobaccari commented 2026-11-13 13:25:37 +00:00

First-time contributor

• Copy link
• Copy Markdown

Why

Players who want a wider gameplay view currently reach the slider's limit at 150%. This extends the existing Field of view control to 300% and places it under Graphics.

What changed

• Move the existing row from Gameplay to Graphics → Detail; extend 50–150% to 50–300%, in steps of 5.
• Extend the accepted range in host/oot_fov.c. Preserve default 100%, the saved field_of_view key, option ID, the 5–140 degree angular clamp, gameplay camera ownership and event-camera exclusion.
• Update the existing FOV fixture, menu option comment, README and development reference. Record four historical runs at their original commit identities.

Flags and settings

Flag	What it does	Default now	Recommendation	Helps on	Doesn't help on	Untested on
Graphics → Field of view / field_of_view	Multiply the current native vertical gameplay angle by 50–300%; final angle remains within 5–140 degrees	100%	Keep 100% for the original camera; larger values widen and distort the view	Players wanting a wider view	Performance optimization; more geometry can increase GPU work	Current rebased runtime; aiming/zoom at 300%; Linux gameplay

No new environment variable, option ID, save format or renderer interface.

Measurements

main: 514591a3 (2026-11-13)
this PR: feat/longshot-fov-range-300 @ e2e7f320
Hardware: Windows 11 Pro, Ryzen 5 3600, 64 GB RAM, Radeon RX 5500 XT 8 GB / AMD 26.10.1.
Scene and settings for current runtime comparison: pending. The intended comparison is Kokiri Forest with identical save/camera, 1920×1080 native, upscaler/FG/V-Sync off, uncapped, audio 0, visible NoActivate window.
Method: read-only API/Git review identifies current head e2e7f320 on main 514591a3. Its three topic patches match the previously checked 3439a77a series (git range-diff); the intervening main change updates Discord links. The earlier focused checks below retain their original commit identities. No new suite, build or gameplay result is claimed. Full current-head suite, application build and interleaved gameplay measurements remain pending; shared build/GPU resources are reserved for the separate PR200 validation.

Check	main @ 514591a3	this PR @ e2e7f320
Source range / location	50–150%, Gameplay	50–300%, Graphics
Default / angular clamp	100% / 5–140°	Unchanged
Focused Windows checks	Not rerun on this main; prior d9648863 translation failure is recorded below	Not rerun on this head; 4 checks passed at 3439a77a and an earlier 76aad7d2 run had 7 passed / 1 baseline failure
Full current Windows suite	Not rerun on this main	Not run on this head
Current interleaved runtime comparison	Pending	Pending

Historical evidence only: main 0c74253d and FOV 446c856e had two interleaved 600-frame windows each at FOV 100%. Median run FPS was 21.3899 / 21.8349; the baseline runs varied 11.6%, so no gain, regression or zero-cost conclusion was established. The four runs are retained in docs/tested-configurations.md. Main has since changed GPU occlusion handling; these results do not validate the present commits.

Testing

Tested: Current read-only Git/API verification confirms e2e7f320 on 514591a3, with all three topic patches unchanged from 3439a77a. The current diff remains seven files, 17 insertions and 9 deletions; git diff --check and merge simulation pass. No source test, application build or game session was started for this metadata update.

Earlier rebase checkpoint at 3439a77a: all three remote topic commits from bd8912e7 were rebased onto d9648863. The README conflict retains upstream HDR/AMD FSR 4 documentation and the Graphics FOV row. The menu header retains upstream Damage taken and the FOV default/range comment. The later mouse and controller-layout fixes are included unchanged. The final diff is still seven files, 17 insertions and 9 deletions. git diff --check passes; local merge simulation against d9648863 has no conflicts. An independent source review found no issue in the conflict resolution.

At intermediate head 76aad7d2, eight serial Windows checks completed: seven passed (damage_debug_menu, framegen_preset, menu_keys, oot_damage, oot_fov, option_ids, readme_menu_rows), and menu_i18n failed because the PT-BR table still contains an old Debug help key. The same assertion was independently reproduced using the exact four required blobs from both main d906c8f4 and then-current main d9648863: four unit tests passed and one failed in each. The translation key ends in own speed., while the current menu help ends in own speed and damage.. No translation or assertion was changed by this FOV PR.

After incorporating the final upstream controller-layout fix, 3439a77a passed all four repeated/new checks: framegen_preset, oot_fov, pad_layout, and readme_menu_rows (4 passed, 0 failed, 0 skipped in 74 s, serial Windows run). The prior eight-check run took 271 s while the manual Launcher preparation was active. These elapsed times are test-run durations, not game performance measurements.

Reproduce focused checks using Builder Python and llvm-mingw with LONGSHOT_MINGW and RX_CPM configured: python -I -B tests/run_all.py --jobs 1 oot_fov readme_menu_rows menu_keys option_ids framegen_preset menu_i18n damage_debug_menu oot_damage pad_layout.

Earlier completed suite, explicitly at 4e0d71f9: 492 passed, 4 failed, 33 skipped in 883 s. All four failure names reproduced on clean main f647a072: nx2/test_nup_paths.py needs Windows symlink privilege 1314; test_bug_report.py rejects byte 0xe3 in an OS diagnostic as UTF-8; test_check_third_party.py fails its authored clean-tree fixture; test_release.py needs OpenSSL and encounters a non-Win32 git-cliff fixture plus a CRLF/LF assertion. These are historical baseline results, not a current-main reproduction or a clean pass.

Earlier Linux focal validation at 4e0d71f9 passed in disposable Alpine 3.22 containers (GCC/G++ 14.2.0, Python 3.12.16): the FOV Python/C fixture, menu-key fixture, and object compilation of actual host/oot_fov.c with official runtime headers generated by the existing helper. FOV source and those fixtures remain unchanged. No full Linux application or gameplay validation is claimed.

Not tested: Focused checks, full suite and complete Windows application/renderer build at current e2e7f320; current gameplay at 100/150/200/300%, reset, event cameras, aiming/zoom at 300%; new interleaved measurements/screenshots. Earlier full-suite/build attempts at 5844f707 were stopped to yield resources to the user's manual Launcher build; its processes were left untouched. Only lightweight serial checks were run at the earlier named checkpoints, without game assets or GPU; none were rerun for this metadata update. Earlier visible FOV/event-camera checks at 446c856e are historical.

Needs other testers: None. Author validation remains incomplete; no external testing is requested. The PR remains WIP until the pending author checks and measurements listed above are completed.

Screenshots

Historical captures only; new captures from the rebased build are pending.

Risk and rollback

High FOV values cause strong peripheral distortion and may increase rendering work. The percentage multiplies the native vertical angle subject to the retained 140-degree ceiling. Select 100% to restore the native gameplay angle on the next update. Revert the topic commits to restore the old range and location; no save migration or assets change.

Reviewer notes

Start at hos_oot_fov() and the Graphics row in gpu/vk/vk_menu.cpp. The diff contains only the existing FOV feature and its documentation/tests; upstream Damage taken, HDR/FSR 4, mouse and controller-layout behavior is preserved. The earlier push of 3439a77a used an explicit lease for remote bd8912e7; this metadata update does not push or alter the current e2e7f320 head.

Issues

Player-requested camera adjustment; no issue is closed.

Checklist

For everyone

• One topic.
• The title is a Conventional Commit (type(scope): description).
• Rebased on current main. — 514591a3, verified by API/Git on 2026-11-13.
• python -I -B tests/run_all.py run and passing (any failure that also fails on main is named above). — Not run on this head; earlier 492/4/33 and baseline reproductions are identified above.
• Tested in the game, or what wasn't is named under Testing. — Current-build game validation pending and named above.
• Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests).
• Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported. — Current-build runs pending; old runs are explicitly historical.
• 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.

If applicable

• AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
• Flags noted, and the switch reference updated (docs/development.md, the README).
• Screenshots for a change that shows on screen. — Historical captures attached; current-head captures pending.
• A row in docs/tested-configurations.md for each measured run. — Four historical runs, explicitly identified.
• A check under tests/ that reads changed source updated in this PR, not weakened.
• Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. — Linux actual host unit compiled and fixtures passed; current Windows application build pending.
• Docs updated.

## Why Players who want a wider gameplay view currently reach the slider's limit at 150%. This extends the existing Field of view control to 300% and places it under Graphics. ## What changed - Move the existing row from Gameplay to Graphics → Detail; extend 50–150% to 50–300%, in steps of 5. - Extend the accepted range in `host/oot_fov.c`. Preserve default 100%, the saved `field_of_view` key, option ID, the 5–140 degree angular clamp, gameplay camera ownership and event-camera exclusion. - Update the existing FOV fixture, menu option comment, README and development reference. Record four historical runs at their original commit identities. ## Flags and settings | Flag | What it does | Default now | Recommendation | Helps on | Doesn't help on | Untested on | |---|---|---|---|---|---|---| | Graphics → Field of view / `field_of_view` | Multiply the current native vertical gameplay angle by 50–300%; final angle remains within 5–140 degrees | 100% | Keep 100% for the original camera; larger values widen and distort the view | Players wanting a wider view | Performance optimization; more geometry can increase GPU work | Current rebased runtime; aiming/zoom at 300%; Linux gameplay | No new environment variable, option ID, save format or renderer interface. ## Measurements main: 514591a3 (2026-11-13) this PR: feat/longshot-fov-range-300 @ e2e7f320 Hardware: Windows 11 Pro, Ryzen 5 3600, 64 GB RAM, Radeon RX 5500 XT 8 GB / AMD 26.10.1. Scene and settings for current runtime comparison: pending. The intended comparison is Kokiri Forest with identical save/camera, 1920×1080 native, upscaler/FG/V-Sync off, uncapped, audio 0, visible NoActivate window. Method: read-only API/Git review identifies current head e2e7f320 on main 514591a3. Its three topic patches match the previously checked 3439a77a series (git range-diff); the intervening main change updates Discord links. The earlier focused checks below retain their original commit identities. No new suite, build or gameplay result is claimed. Full current-head suite, application build and interleaved gameplay measurements remain pending; shared build/GPU resources are reserved for the separate PR200 validation. | Check | main @ 514591a3 | this PR @ e2e7f320 | |---|---|---| | Source range / location | 50–150%, Gameplay | 50–300%, Graphics | | Default / angular clamp | 100% / 5–140° | Unchanged | | Focused Windows checks | Not rerun on this main; prior d9648863 translation failure is recorded below | Not rerun on this head; 4 checks passed at 3439a77a and an earlier 76aad7d2 run had 7 passed / 1 baseline failure | | Full current Windows suite | Not rerun on this main | Not run on this head | | Current interleaved runtime comparison | Pending | Pending | Historical evidence only: main `0c74253d` and FOV `446c856e` had two interleaved 600-frame windows each at FOV 100%. Median run FPS was 21.3899 / 21.8349; the baseline runs varied 11.6%, so no gain, regression or zero-cost conclusion was established. The four runs are retained in `docs/tested-configurations.md`. Main has since changed GPU occlusion handling; these results do not validate the present commits. ## Testing **Tested:** Current read-only Git/API verification confirms `e2e7f320` on `514591a3`, with all three topic patches unchanged from `3439a77a`. The current diff remains seven files, 17 insertions and 9 deletions; `git diff --check` and merge simulation pass. No source test, application build or game session was started for this metadata update. Earlier rebase checkpoint at `3439a77a`: all three remote topic commits from `bd8912e7` were rebased onto `d9648863`. The README conflict retains upstream HDR/AMD FSR 4 documentation and the Graphics FOV row. The menu header retains upstream Damage taken and the FOV default/range comment. The later mouse and controller-layout fixes are included unchanged. The final diff is still seven files, 17 insertions and 9 deletions. `git diff --check` passes; local merge simulation against `d9648863` has no conflicts. An independent source review found no issue in the conflict resolution. At intermediate head `76aad7d2`, eight serial Windows checks completed: seven passed (`damage_debug_menu`, `framegen_preset`, `menu_keys`, `oot_damage`, `oot_fov`, `option_ids`, `readme_menu_rows`), and `menu_i18n` failed because the PT-BR table still contains an old Debug help key. The same assertion was independently reproduced using the exact four required blobs from both main `d906c8f4` and then-current main `d9648863`: four unit tests passed and one failed in each. The translation key ends in `own speed.`, while the current menu help ends in `own speed and damage.`. No translation or assertion was changed by this FOV PR. After incorporating the final upstream controller-layout fix, `3439a77a` passed all four repeated/new checks: `framegen_preset`, `oot_fov`, `pad_layout`, and `readme_menu_rows` (4 passed, 0 failed, 0 skipped in 74 s, serial Windows run). The prior eight-check run took 271 s while the manual Launcher preparation was active. These elapsed times are test-run durations, not game performance measurements. Reproduce focused checks using Builder Python and llvm-mingw with `LONGSHOT_MINGW` and `RX_CPM` configured: `python -I -B tests/run_all.py --jobs 1 oot_fov readme_menu_rows menu_keys option_ids framegen_preset menu_i18n damage_debug_menu oot_damage pad_layout`. Earlier completed suite, explicitly at `4e0d71f9`: 492 passed, 4 failed, 33 skipped in 883 s. All four failure names reproduced on clean main `f647a072`: `nx2/test_nup_paths.py` needs Windows symlink privilege 1314; `test_bug_report.py` rejects byte `0xe3` in an OS diagnostic as UTF-8; `test_check_third_party.py` fails its authored clean-tree fixture; `test_release.py` needs OpenSSL and encounters a non-Win32 git-cliff fixture plus a CRLF/LF assertion. These are historical baseline results, not a current-main reproduction or a clean pass. Earlier Linux focal validation at `4e0d71f9` passed in disposable Alpine 3.22 containers (GCC/G++ 14.2.0, Python 3.12.16): the FOV Python/C fixture, menu-key fixture, and object compilation of actual `host/oot_fov.c` with official runtime headers generated by the existing helper. FOV source and those fixtures remain unchanged. No full Linux application or gameplay validation is claimed. **Not tested:** Focused checks, full suite and complete Windows application/renderer build at current `e2e7f320`; current gameplay at 100/150/200/300%, reset, event cameras, aiming/zoom at 300%; new interleaved measurements/screenshots. Earlier full-suite/build attempts at `5844f707` were stopped to yield resources to the user's manual Launcher build; its processes were left untouched. Only lightweight serial checks were run at the earlier named checkpoints, without game assets or GPU; none were rerun for this metadata update. Earlier visible FOV/event-camera checks at `446c856e` are historical. **Needs other testers:** None. Author validation remains incomplete; no external testing is requested. The PR remains WIP until the pending author checks and measurements listed above are completed. ## Screenshots Historical captures only; new captures from the rebased build are pending.      ## Risk and rollback High FOV values cause strong peripheral distortion and may increase rendering work. The percentage multiplies the native vertical angle subject to the retained 140-degree ceiling. Select 100% to restore the native gameplay angle on the next update. Revert the topic commits to restore the old range and location; no save migration or assets change. ## Reviewer notes Start at `hos_oot_fov()` and the Graphics row in `gpu/vk/vk_menu.cpp`. The diff contains only the existing FOV feature and its documentation/tests; upstream Damage taken, HDR/FSR 4, mouse and controller-layout behavior is preserved. The earlier push of `3439a77a` used an explicit lease for remote `bd8912e7`; this metadata update does not push or alter the current `e2e7f320` head. ## Issues Player-requested camera adjustment; no issue is closed. ## Checklist ### For everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`). - [x] Rebased on current `main`. — `514591a3`, verified by API/Git on 2026-11-13. - [ ] `python -I -B tests/run_all.py` run and passing (any failure that also fails on `main` is named above). — Not run on this head; earlier 492/4/33 and baseline reproductions are identified above. - [ ] Tested in the game, or what wasn't is named under Testing. — Current-build game validation pending and named above. - [x] Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests). - [ ] Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported. — Current-build runs pending; old runs are explicitly historical. - [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. ### If applicable - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Flags noted, and the switch reference updated (docs/development.md, the README). - [ ] Screenshots for a change that shows on screen. — Historical captures attached; current-head captures pending. - [x] A row in `docs/tested-configurations.md` for each measured run. — Four historical runs, explicitly identified. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [ ] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. — Linux actual host unit compiled and fixtures passed; current Windows application build pending. - [x] Docs updated.

kokiri.png

2.6 MiB

fov-00-100.png

2.6 MiB

fov-03-300.png

2.6 MiB

ui.png

484 KiB

event-warm-1-fov300.png

2.6 MiB

brunobaccari added 2 commits 2026-11-13 13:25:38 +00:00

feat(graphics): extend the FOV slider to 300 percent ... 5de413a9f6

Keep the native camera projection and angular bounds, move the existing slider to Graphics, and cover the extended range.

Assisted-by: Codex

Co-Authored-By: OpenAI Codex <[email protected]>

docs: align FOV option table with Graphics slider ... 446c856ef9

Document the Graphics location and 50–300% range of the FOV slider.

Assisted-by: Codex

Co-Authored-By: OpenAI Codex <[email protected]>

brunobaccari commented 2026-11-13 14:01:04 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Ran the full Windows suite: 482 passed, 7 failed, 33 skipped, with source and fixture hashes unchanged. Baseline reproductions and the passing serial cleanup recheck are documented in the description. The actual changed host C also compiled on Linux. Release builds and in-game measurements are still in progress; this remains WIP.

Ran the full Windows suite: 482 passed, 7 failed, 33 skipped, with source and fixture hashes unchanged. Baseline reproductions and the passing serial cleanup recheck are documented in the description. The actual changed host C also compiled on Linux. Release builds and in-game measurements are still in progress; this remains WIP.

brunobaccari commented 2026-11-13 15:12:34 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

The complete Windows standalone build linked the executable and Vulkan renderer with zero failures. The actual changed host translation unit also compiled on Linux; this is not a full Linux application or GPU run. Main has advanced only in README/CONTRIBUTING since the named build base; the final rebase is pending while the current runtime comparison is preserved. A warmed Kokiri baseline image is attached. Scripted, visible in-game comparisons are in progress; WIP remains until the repeated measurements and FOV captures are complete.

The complete Windows standalone build linked the executable and Vulkan renderer with zero failures. The actual changed host translation unit also compiled on Linux; this is not a full Linux application or GPU run. Main has advanced only in README/CONTRIBUTING since the named build base; the final rebase is pending while the current runtime comparison is preserved. A warmed Kokiri baseline image is attached. Scripted, visible in-game comparisons are in progress; WIP remains until the repeated measurements and FOV captures are complete.

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 15:34:17 +00:00

brunobaccari added 1 commit 2026-11-13 15:34:58 +00:00

Merge branch 'main' into feat/longshot-fov-range-300 6af043c322

brunobaccari force-pushed feat/longshot-fov-range-300 from 6af043c322 to 32227d8fb3 2026-11-13 16:10:39 +00:00 Compare

brunobaccari added 1 commit 2026-11-13 16:16:04 +00:00

Merge branch 'main' into feat/longshot-fov-range-300 73e84b49b1

brunobaccari changed title from feat(graphics): extend the FOV slider to 300 percent to WIP: feat(graphics): extend the FOV slider to 300 percent 2026-11-13 16:54:11 +00:00

brunobaccari force-pushed feat/longshot-fov-range-300 from 73e84b49b1 to f4213d2d4b 2026-11-13 16:56:05 +00:00 Compare

brunobaccari force-pushed feat/longshot-fov-range-300 from f4213d2d4b to 4e0d71f9f4 2026-11-13 16:57:03 +00:00 Compare

brunobaccari commented 2026-11-13 16:58:56 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Rebased all three topic commits onto main f647a072, preserving the upstream HDR text and every existing tested-configuration row while resolving the two documentation conflicts. Remote updates used explicit expected-head leases. Seven focused checks pass on 4e0d71f9. The description now separates historical evidence from current validation; WIP is restored until the current full suite, builds and visible game comparison are completed.

Rebased all three topic commits onto main f647a072, preserving the upstream HDR text and every existing tested-configuration row while resolving the two documentation conflicts. Remote updates used explicit expected-head leases. Seven focused checks pass on 4e0d71f9. The description now separates historical evidence from current validation; WIP is restored until the current full suite, builds and visible game comparison are completed.

brunobaccari force-pushed feat/longshot-fov-range-300 from 4e0d71f9f4 to 5844f7071d 2026-11-13 17:19:24 +00:00 Compare

brunobaccari commented 2026-11-13 17:21:40 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Rebased onto main fbd42024 as 5844f707 without conflicts; the topic diff remains seven files. The prior full Windows run at 4e0d71f9 completed with 492 passed, 4 failed and 33 skips; all four failure names reproduced on clean main with the same causes, now described in Testing. Linux FOV/menu fixtures and actual host-unit compilation passed, and those sources are unchanged in this rebase. A new full run and builds are in progress because the new upstream renderer change must be present on both sides of the runtime comparison. WIP remains.

Rebased onto main fbd42024 as 5844f707 without conflicts; the topic diff remains seven files. The prior full Windows run at 4e0d71f9 completed with 492 passed, 4 failed and 33 skips; all four failure names reproduced on clean main with the same causes, now described in Testing. Linux FOV/menu fixtures and actual host-unit compilation passed, and those sources are unchanged in this rebase. A new full run and builds are in progress because the new upstream renderer change must be present on both sides of the runtime comparison. WIP remains.

brunobaccari commented 2026-11-13 17:32:54 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

The new validation attempt and shared development build were deliberately interrupted to give the user manual Launcher build exclusive resources. Only the validation process trees were stopped; their logs and partial files are preserved, and the user build was left untouched. This interruption is not a test failure or a completed current-head suite. Rebase and prior completed evidence are unchanged; WIP remains until validation can resume.

The new validation attempt and shared development build were deliberately interrupted to give the user manual Launcher build exclusive resources. Only the validation process trees were stopped; their logs and partial files are preserved, and the user build was left untouched. This interruption is not a test failure or a completed current-head suite. Rebase and prior completed evidence are unchanged; WIP remains until validation can resume.

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 17:58:40 +00:00

brunobaccari force-pushed feat/longshot-fov-range-300 from 5844f7071d to bd8912e78a 2026-11-13 18:13:03 +00:00 Compare

brunobaccari requested review from HumanBean 2026-11-13 18:28:18 +00:00

brunobaccari force-pushed feat/longshot-fov-range-300 from bd8912e78a to 3439a77ae7 2026-11-13 18:39:56 +00:00 Compare

brunobaccari changed title from feat(graphics): extend the FOV slider to 300 percent to WIP: feat(graphics): extend the FOV slider to 300 percent 2026-11-13 18:41:01 +00:00

brunobaccari commented 2026-11-13 18:41:15 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Rebased the three existing topic commits from bd8912e7 onto main d9648863; published head 3439a77a with an explicit expected-head force-with-lease. Resolved README.md and gpu/vk/vk_menu.h by retaining upstream HDR/AMD FSR 4 and Damage taken content alongside the FOV change. The later mouse and controller-layout fixes are also preserved. The diff remains 7 files, 17 insertions and 9 deletions; diff --check and local merge simulation pass, and Forgejo confirmed no merge conflicts after the push.

Validation: the intermediate 76aad7d2 run completed with 7 checks passed and menu_i18n failed. That stale PT-BR Debug help key reproduces independently on current main d9648863 (4 unit tests passed, 1 failed). After the final rebase, all 4 selected checks passed: framegen_preset, oot_fov, pad_layout and readme_menu_rows.

Full current-head suite, application build and gameplay measurements remain pending. The user's manual Launcher preparation was preserved; no full build, game or GPU test was started for this rebase. The description distinguishes these checks from older suite/runtime evidence, and WIP remains appropriate until current author validation is completed.

Rebased the three existing topic commits from bd8912e7 onto main d9648863; published head 3439a77a with an explicit expected-head force-with-lease. Resolved README.md and gpu/vk/vk_menu.h by retaining upstream HDR/AMD FSR 4 and Damage taken content alongside the FOV change. The later mouse and controller-layout fixes are also preserved. The diff remains 7 files, 17 insertions and 9 deletions; diff --check and local merge simulation pass, and Forgejo confirmed no merge conflicts after the push. Validation: the intermediate 76aad7d2 run completed with 7 checks passed and menu_i18n failed. That stale PT-BR Debug help key reproduces independently on current main d9648863 (4 unit tests passed, 1 failed). After the final rebase, all 4 selected checks passed: framegen_preset, oot_fov, pad_layout and readme_menu_rows. Full current-head suite, application build and gameplay measurements remain pending. The user's manual Launcher preparation was preserved; no full build, game or GPU test was started for this rebase. The description distinguishes these checks from older suite/runtime evidence, and WIP remains appropriate until current author validation is completed.

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 18:41:25 +00:00

brunobaccari changed title from feat(graphics): extend the FOV slider to 300 percent to WIP: feat(graphics): extend the FOV slider to 300 percent 2026-11-13 18:42:04 +00:00

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 18:50:35 +00:00

brunobaccari changed title from feat(graphics): extend the FOV slider to 300 percent to WIP: feat(graphics): extend the FOV slider to 300 percent 2026-11-13 18:55:23 +00:00

brunobaccari commented 2026-11-13 18:55:24 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Description check follow-up: corrected the Needs other testers field to the required None form because validation is still the author's work, with no external test request. Restored WIP status and kept every pending checkbox unchanged: current-head full suite, gameplay, measurements, screenshots and complete platform build validation are still pending. No source, commit, test result or measurement changed. This metadata edit retriggers only the PR-description workflow; no build or GPU run was started.

Description check follow-up: corrected the Needs other testers field to the required None form because validation is still the author's work, with no external test request. Restored WIP status and kept every pending checkbox unchanged: current-head full suite, gameplay, measurements, screenshots and complete platform build validation are still pending. No source, commit, test result or measurement changed. This metadata edit retriggers only the PR-description workflow; no build or GPU run was started.

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 19:11:06 +00:00

brunobaccari force-pushed feat/longshot-fov-range-300 from 3439a77ae7 to e2e7f3205d 2026-11-13 19:11:08 +00:00 Compare

brunobaccari changed title from feat(graphics): extend the FOV slider to 300 percent to WIP: feat(graphics): extend the FOV slider to 300 percent 2026-11-13 20:11:36 +00:00

brunobaccari changed title from WIP: feat(graphics): extend the FOV slider to 300 percent to feat(graphics): extend the FOV slider to 300 percent 2026-11-13 20:19:43 +00:00

simonwjackson referenced this pull request 2026-11-13 21:03:52 +00:00

feat(video): a Window choice that fills the actual window, Hor+ and Vert+ #142

simonwjackson referenced this pull request 2026-11-13 21:03:53 +00:00

feat(video): a Window choice that fills the actual window, Hor+ and Vert+ #142

Some checks failed

Hide checks

CI / Conventional Commit title (pull_request) Blocked by required conditions

Details

CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions

Details

CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions

Details

CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions

Details

CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions

Details

Third-party parts / As their notes say (pull_request) Blocked by required conditions

Details

Third-party parts / The same as upstream (pull_request) Blocked by required conditions

Details

Website / Website on Cloudflare (pull_request) Blocked by required conditions

Details

PR description / Description follows the template (pull_request_target) Failing after 3s

Details

This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.

Some workflows are waiting to be reviewed.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u 'feat/longshot-fov-range-300:brunobaccari-feat/longshot-fov-range-300'

git switch 'brunobaccari-feat/longshot-fov-range-300'

Sign in to join this conversation.

Reviewers

No reviewers

HumanBean

Labels

Clear labels   

area/accessibility

Barriers for people with disabilities

  

area/audio

Sound and music

  

area/input

Controllers, keyboard, mouse

  

area/install

Installing, updating, building from your game

  

area/menu

In-game menu and settings

  

area/renderer

Vulkan renderer, shaders, effects

  

area/saves

Save files

  

area/upscaling

DLSS, FSR, frame generation

  

good first issue

A good start for a new contributor

  

gpu/amd

AMD GPUs

  

gpu/igpu

Integrated GPUs

  

gpu/intel

Intel GPUs

  

gpu/nvidia

NVIDIA GPUs

  

help wanted

Extra hands or knowledge wanted

  

kind

bug

Something doesn't work as it should

  

kind

chore

Build, CI, dependencies, tidying

  

kind

docs

Documentation

  

kind

feature

A new feature or an improvement

  

kind

performance

Frame rate, frame time, loading, memory

  

kind

question

A question rather than a change

  

needs measurements

Waiting for before/after measurements

  

platform/linux

Linux only

  

platform/steam-deck

Steam Deck

  

platform/windows

Windows only

  

preview

Maintainers: deploy a preview of this PR's website (read its changes first). Removed after the run.

  

priority

critical

Crashes, data loss, or blocks most players

  

priority

high

Important: next in line

  

priority

low

Nice to have

  

status

blocked

Waits on something else first

  

status

confirmed

Reproduced or agreed on

  

status

duplicate

Already reported or proposed

  

status

invalid

Not a problem in this project

  

status

needs-info

Waiting for more information from the reporter

  

status

wontfix

Will not be worked on

  

testing wanted

Wanted: a test on other hardware (posts a test request in #test-requests)

No labels

area/accessibility

area/audio

area/input

area/install

area/menu

area/renderer

area/saves

area/upscaling

good first issue

gpu/amd

gpu/igpu

gpu/intel

gpu/nvidia

help wanted

kind

bug

kind

chore

kind

docs

kind

feature

kind

performance

kind

question

needs measurements

platform/linux

platform/steam-deck

platform/windows

preview

priority

critical

priority

high

priority

low

status

blocked

status

confirmed

status

duplicate

status

invalid

status

needs-info

status

wontfix

testing wanted

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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!199

No description provided.