Thank you for the report.
I have bisected this to start with commit https://github.com/doitsujin/dxvk/commit/175772944ca94a6cd001dad70a98cec4f1805907
More specifically commenting out the lines below makes the issue go away
if (unlikely(!dstHasRTUsage && (!dstIsSurface || !srcIsSurface || srcHasRTUsage)))
return D3DERR_INVALIDCALL;
Nothing extracted yet.
The issue is present in all places where weapons are rendered, so should be easy to reproduce. It doesn't occur with DXVK 2.3 (the version that ships with TF2).
Software information
Team Fortress 2, default settings used. *Antialiasing enabled
System information
Apitrace file(s)
Apitrace just doesn't work for me, so if anyone can reproduce this, please share the trace file in a comment.
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace