video_core: Never apply AF to None mipmap mode
Should fix some artifacts with the "apply anisotropic filtering for all mipmap modes" option
This commit is contained in:
parent
b9bba3ac89
commit
44f616edb9
1 changed files with 4 additions and 3 deletions
|
@ -62,9 +62,10 @@ std::array<float, 4> TSCEntry::BorderColor() const noexcept {
|
||||||
}
|
}
|
||||||
|
|
||||||
float TSCEntry::MaxAnisotropy() const noexcept {
|
float TSCEntry::MaxAnisotropy() const noexcept {
|
||||||
if (max_anisotropy == 0 && (depth_compare_enabled.Value() ||
|
const bool suitable_mipmap_filter = Settings::values.use_aggressive_anisotropic_filtering
|
||||||
(mipmap_filter != TextureMipmapFilter::Linear &&
|
? mipmap_filter != TextureMipmapFilter::None
|
||||||
!Settings::values.use_aggressive_anisotropic_filtering))) {
|
: mipmap_filter != TextureMipmapFilter::Linear;
|
||||||
|
if (max_anisotropy == 0 && (depth_compare_enabled.Value() || !suitable_mipmap_filter)) {
|
||||||
return 1.0f;
|
return 1.0f;
|
||||||
}
|
}
|
||||||
const auto anisotropic_settings = Settings::values.max_anisotropy.GetValue();
|
const auto anisotropic_settings = Settings::values.max_anisotropy.GetValue();
|
||||||
|
|
Loading…
Reference in a new issue