mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-27 00:36:00 +03:00
[PR #3471] [MERGED] vk_graphics_pipeline: Prioritize depth clip when separate clip/clamp control is not supported. #3492
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#3492
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
📋 Pull Request Information
Original PR: https://github.com/shadps4-emu/shadPS4/pull/3471
Author: @squidbus
Created: 8/29/2025
Status: ✅ Merged
Merged: 8/29/2025
Merged by: @squidbus
Base:
main← Head:depthclip📝 Commits (1)
e69f257vk_graphics_pipeline: Prioritize depth clip when separate clip/clamp control is not supported.📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
src/video_core/renderer_vulkan/vk_graphics_pipeline.cpp(+2 -2)📄 Description
When separate depth clip control is not supported, the current logic prioritizes depth clamp over clip. However in the common case that both clamping and clipping are being performed with the same depth range, it makes more sense to prioritize clipping as it will effectively no-op the clamp. Adjust the logic to only use depth clamp if enabled and either clip is disabled or separate control is supported.
Fixes rendering issues in CUSA16404 on MoltenVK, which does not support separate clip control.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.