Request for AMD to add anisotropic filtering override for dx11 and dx12 games?

[eager briar]

Huh, I was under the impression that the aniso override became gfx API agnostic with the transition to PAL UMDs.

I'll follow up with d3d sometime next week (company holiday today + long weekend in NA)

[eager briar]

This is Wuthering Waves? Thanks, I'll ask to have this investigated hopefully during the coming week

[olive yew]

Another game where AF can be pretty useful is Death Stranding (both the standard and Director's Cut edition IIRC). Although that game has another issue where forcing AF 16x breaks the lighting on textures.

[eager briar]

Will pass this on

[olive yew]

btw I'm not sure if AMD driver AF override worked for this game (don't think it did), this screenshot was made with OptiScaler/SpecialK AF override, but should serve as another game example where AF override comes in handy

[eager briar]

We've reproduced the behaviour in Wuthering waves

[olive yew]

Great

[sleek iron]

Yes, the game is Wuthering Waves running in Dx12 but switching to Dx11 still exhibit the same behaviour. In fact, none of the dx12 and dx11 games I have played worked with AF override 16x.

[eager briar]

appreciate the input, passing this on

many of my d3d contacts are still on vacation, hope to follow up with them soon

[sleek iron]

Hi, sry to bother again. Is there any progress on this issue?

[eager briar]

none so far

Will extend the ask to several more contacts

[eager briar]

Have filed this to engineering as an aside

[short hedge]

Is this real life? Could this finally be addressed? 😱

[eager briar]

I'm not making any promises yet, there may be some limitation here,

But I hate the idea of API specificity with our gfx overrides

Unintuitive and bad UX. I don't understand a case for this now that all UMDs are on PAL

Could be something kmd level but I'm well out of my depth here. Will see.

[olive yew]

yeah, I'd recommend doing a general pass throughout the entire UI, especially legacy feature tooltips

[eager briar]

I can't tell you how long I've been working towards that.

I believe it was more complex before the full 3D on PAL transition in 2022 though

Or maybe I'm misremembering. In any case, I hope this is more approachable today

[olive yew]

Good luck with pushing it through hopefully soon

btw, off-topic for this thread, but do you already have an open ticket for the weird looking Adrenaline app edges?

Where sometimes (maybe after exiting a fullscreen app?) edges go XP era?

this has been plaguing Adrenaline for the last few drivers

[eager briar]

The aero borders? Yeah

[olive yew]

Nice, it's not a high priority, but just annoying to see 😂

[eager briar]

agreed.

[eager briar]

for posterity:
SWDEV-554083 for aniso control
SWDEV-526381 for aero borders

[olive yew]

Any chance there's an update regarding these?

[eager briar]

the aero borders fix should be implementedl, i haven't heard back on the aniso control thing yet :/

[olive yew]

Good thing for the borders, RIP on the aniso

[eager briar]

yeah that's going to be a difficult one for me to get aligned

[short hedge]

Regarding overriding and API specificity:

For AF override:

Vulkan: doesn't work
OpenGL: works
DirectX 8-9: (works) (same for DX6-7 when they work)
DirectX 10-11: mostly work, it's not 100% reliable
DirectX 12: it sometimes works, most often doesn't

[sleek iron]

Also i noticed 8x tends to work on more games than 16x. Forgot which game but I remember 8x anistropy override working while 16x didn't.

The game uses dx11