If the performance is consistently different and there is not just more temporary stutter, then it has nothing to do with the shader cache. Probably just different vkd3d-proton versions between lutris and proton on steam. Bring this up to the lutris people or something, this bug tracker doesn't really have anything to do with that.
all versions are after 31 oct 22
That's still a 2 month time frame. Anyways, if you use the same version on steam and lutris it should behave the same and there is nothing vkd3d-proton can do about whatever lutris uses anyways. If I had to guess, it's probably the recent change that disables upload_hvv on cards with low vram, because 1-3 fps sounds like you're just running out of vram. Try VKD3D_CONFIG=no_upload_hvv on the lutris version I guess. And ask for lutris support on the lutris discord and not here.
VKD3D_CONFIG=no_upload_hvv didn't help.
trace log will help to discover bottleneck?
The only thing that trace logs will tell us is that you're likely using a different vkd3d-proton version between lutris and steam. I don't know why you think this is a vkd3d-proton bug, just play the game on steam?
its epic version.as far as i know proton is available viasteam or lutris.
shader trace log will if some of shaders that build is being repeatedly recomiling on runtime?
VKD3D_CONFIG=no_upload_hvvx1 2023-01VKD3D_CONFIG=no_upload_hvv`x1 2022-12
Shader cache size is 7gb.
AMD radeon 530
via steam no framedrops(Shader cache size is 1,6gb)
but via lutris drops to 1-3 fps on some chapters