feat(menu): the Game frame rate cap, Descriptor reuse and Sampler cache apply in play #7
No reviewers
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!7
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot:feat/live-settings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The three rows took a restart only because their values were read once at the start.
renderer's existing option callback; no MkwVkHost/MkwVkRenderer change), the vsync thread re-reads
its period each tick, and a cap brought down gives the game back its own limiter (+0xfc), its rate
(+0x2c8) and its step (hos_frame_seconds_bits). The FPS counter's line follows the row. HOS_FPS_MAX
still holds the cap for a run.
(menu_debug_rows). A draw keeps descriptors only from a build made with the same setting, so turning
reuse on never trusts a build that recorded no slot versions. RX_VK_DESC_REUSE and
RX_VK_SAMPLER_CACHE still hold them for a run.
Checks: tests/test_frame_rate_cap_step.py gains the cap changed in play (up, down, Uncapped, back to
60, and with HOS_FPS_STEP=0); tests/test_menu_env_on.py the Debug rows changed in play.
Moved from NotRexed/Hookshot#2900 (closed when the GitHub account was suspended).
e523c93156to992a242002