fix(vk): remove duplicate motion deadzone formatter #1496
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!1496
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/motion-deadzone-redefinition"
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?
Current main does not compile because
vk_menu.cppdefinestx_deadzone(int)twice after the recent menu merges. Both definitions are identical; remove the second copy while keeping the original formatter and Motion row binding.The labels and clamping are unchanged. This is a build repair with no visible game change.
Validation: the official standalone Vulkan backend build (
RX_VK_ONLY=1, llvm-mingw, pinned Vulkan/SPIR-V headers) now compiles and links with zero failures atd36ae74on8240446; before the repair the compiler reports the duplicate definitions. Existingtest_motion.pyandtest_menu_hit.pypass. Exact-head fork workflows follow. No game data or build output included.Current-head validation
Current head
d36ae74, based on main8240446. Earlier local/runtime results describe their recorded source hashes.Fork runs are separate from upstream Actions approval; no maintainer approval gate is bypassed.