mirror of
https://github.com/RPCS3/rpcs3.git
synced 2024-11-25 12:12:50 +01:00
vk: Enable shading rate hack for all GPUs
- This is a hack, ideally we should be using coverage-based masking when writing the exploded texture. - We do not have access to the fragment coverage mask and it is non-trivial to integrate it in a competent manner.
This commit is contained in:
parent
f526027778
commit
d6aa834b5f
@ -1737,15 +1737,11 @@ bool VKGSRender::load_program()
|
||||
rsx::method_registers.msaa_alpha_to_coverage_enabled(),
|
||||
alpha_to_one_enable);
|
||||
|
||||
if (const auto chip_family = vk::get_chip_family();
|
||||
chip_family == vk::chip_class::AMD_navi1x ||
|
||||
chip_family == vk::chip_class::AMD_navi2x)
|
||||
{
|
||||
// NAVI family has a GPU bug with MSAA where shading rate is not correctly initialized if left disabled
|
||||
// Manually initialize it and set it to spec default (full shading)
|
||||
// A problem observed on multiple GPUs is that interior geometry edges can resolve 0 samples unless we force shading rate of 1.
|
||||
// For whatever reason, the way MSAA images are 'resolved' on PS3 bypasses this issue.
|
||||
// NOTE: We do not do image resolve at all, the output is merely 'exploded' and the guest application is responsible for doing the resolve in software as it is on real hardware.
|
||||
properties.state.set_multisample_shading_rate(1.f);
|
||||
}
|
||||
}
|
||||
|
||||
properties.renderpass_key = m_current_renderpass_key;
|
||||
if (!m_interpreter_state && m_program) [[likely]]
|
||||
|
Loading…
Reference in New Issue
Block a user