My understanding was that the official DXVK does not support asynchronous shader compute, and you instead needed to use a fork which enables the feature. I have a separate request on the Plutonium Github issue tracker for this specific reason, as DXVK fixes AMD GPU driver crashes, but introduces large performance issues you outlined.

Hi there, I submitted a suggestion via the Github issue tracker a while ago and was told posting here would be a better way to get eyes on it.

I can understand being apprehensive on whitelisting .dlls due to wanting to keep a lid on cheating, but I don't think anyone has commented on it yet. If staff supports this change, it will improve the experience using Plutonium on AMD GPUs substantially, as dxvk does provide a workaround for a nasty driver crash bug, but has massive performance implications which these forks help resolve. I've explained this in more detail below.

[See issue 79 on the Plutonium Issue Tracker Github, as it seems I do not yet have permission to share links here]

This would also help properly address the issue below, which was previously understood as something that couldn't be fixed. Maybe using the alternative dxvk .dlls could be added to the troubleshooting page for AMD users.

[See issue 66]