• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

OpenGL vs Vulkan in DOOM

AMD users should compare their performance hit from TSSAA (async) vs FXAA (no async) in OGL and compare to Vulkan. That should give us an idea of how much async affects things.

Is that STILL true? it's been a few months now, you'd think they would have fixed that?

Or is this an indication of the future, where lazy-ass developers won't even implement all the features on the DX12 path?
 
Is that STILL true? it's been a few months now, you'd think they would have fixed that?

Or is this an indication of the future, where lazy-ass developers won't even implement all the features on the DX12 path?
Huh?

Afaik async only works when not using AA or using TSSAA, so we can't isolate it from there AA, we just need to look at % change and compare vulkan and ogl.
 
Huh?

Afaik async only works when not using AA or using TSSAA, so we can't isolate it from there AA, we just need to look at % change and compare vulkan and ogl.

When it was released, they noted that it was a first-cut, only AMD supports async. Because it wasn't finished yet, only the TSSAA and no AA paths were async.

id Software: Use TSSAA or No AA Or Else Async Compute Is Disabled

They also said the plan is to fix this discrepancy in a later update. But you know how that goes. So do you have any current information on whether they fixed async in other modes?
 
Back
Top