fix(vk): preserve brightness in flash sampling across capture sizes #1537
No reviewers
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot!1537
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/flash-sampling-normalization"
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?
PNG flash diagnostics divide by floored cell/stride counts rather than the number of samples visited. A constant white3440x1440 capture becomes18 in the first detector cell after byte wrapping (1920x1080 becomes77), so brightness changes can produce false flashes or reversed polarity. Remainder rows/columns are omitted, and small captures can divide by zero.
Partition the full capture into normalized64x36 cells, retain the four-pixel sampling stride, and divide by the actual sample count. Cells smaller than the grid repeat a valid pixel. The production cell/region detector, thresholds and filenames remain unchanged; game rendering, HUD and FOV are unaffected.
Validation at
04aa05don main509579b:docs/flash-sampling.mddescribes the diagnostic behavior. Resource readiness (#1472), host-cache visibility (#1502), normal PNG slot ownership (#1519), binary reader integrity (#1467) and sink errors (#1531) are separate contracts. The shared upstream Linux updater test failure is tracked in #1536; exact-head fork source/build/AppImage workflows follow. No game data, captures, generated game code or binaries are included.Current-head validation
Current head
25bf24a, based on main7d1562d. Earlier local/runtime results describe their recorded source hashes.The standalone contribution patch is unchanged after the audited main refresh; exact-head build/source checks are refreshed below. Earlier runtime evidence remains tied to its recorded hash.
Fork runs are separate from upstream Actions approval; no maintainer approval gate is bypassed.