Please capture an apitrace of the game following these instructions: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Software information

Name of the game, settings used etc.

Also, can you be more specific about what game this is happening in? The issue template is there for a reason.

P.S.: Note than when you are in windowed mode, the game will use a hardware (OS) cursor, so it's unlikely this is a dxvk bug. Regardless, we can't look into this without an apitrace.

Please capture an apitrace of the game following these instructions: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Software information

Name of the game, settings used etc.

Also, can you be more specific about what game this is happening in? The issue template is there for a reason.

P.S.: Note than when you are in windowed mode, the game will use a hardware (OS) cursor, so it's unlikely this is a dxvk bug. Regardless, we can't look into this without an apitrace.

ok i make apitrace but is large file '-' about 177mb
how to send?

ok i make apitrace but is large file '-' about 177mb how to send?

Compress it first, because it generally compresses well, then and use a public hosting service (e.g. GDrive) to upload it. Once that is done, post the access link here.

ok i make apitrace but is large file '-' about 177mb how to send?

Compress it first, because it generally compresses well, then and use a public hosting service (e.g. GDrive) to upload it. Once that is done, post the access link here.

Ok!
link -> https://drive.google.com/file/d/1Sz-9Zuj57WFKKy6xu8CbIFsyQ9jo6IZ0/view?usp=sharing

Thank you for the trace. I don't see a cursor captured in it though, so that means that what you are seeing is indeed an OS cursor. Unfortunately that will make it very difficult to reproduce (and also highly unlikely to be an issue with dxvk).

I have not been able to reproduce this issue on my Windows 11 install with either AMD or Nvidia.

This bug is not caused by the dxvk as the same problem exists for me in interior designing software KD Max, which uses OpenGL. This problem appeared after one of AMD's driver updates late last year. It also looks to affect only RDNA4 on desktop and RDNA 3.5+ on mobile.