feat(menu): a Mesh shaders row (Automatic, Native, Compute) #1971
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!1971
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/mesh-shader-mode"
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?
From the #1001 request (three mesh shader modes, Automatic, Native and Compute, for GPUs without native mesh shaders).
What exists already. The compute fallback for GPUs without mesh shaders (issue 640) already runs automatically: an RX 5500 XT or a GTX 10xx gets it with no setting. The Navi 22 cards (issue 996) also use it for their task + mesh draws. Choosing between the paths was only possible through test switches:
RX_VK_FORCE_MESH_FALLBACK=1RX_VK_TASK_MESH_FALLBACKThis PR adds a Mesh shaders row to the Graphics tab, after Robust buffers. It's read when the device is made (
mesh_shaders=inhookshot_options.ini) and applies after a restart.RX_VK_FORCE_MESH_FALLBACK=1still forces Compute over the row, andRX_VK_TASK_MESH_FALLBACKstill decides the task + mesh draws. The log hasvk: mesh shaders row: <choice> (<what runs>).The menu now has 11 restart rows, within
menu_restart.h's limit of 16.Not yet checked:
🤖 Generated with Claude Code