Well, after looking at dxvk.conf for a while I decided to try my luck by setting dxgi.hideIntelGpu = True, and that seems to have fixed it!
So... Would that be considered as fixed or just a workaround for now? I imagine I'm not the only one experiencing this.
This is a known game issue, they make assumptions on clear value rounding behaviour depending on GPU vendors which do not necessarily hold true on Vulkan drivers. We should already have an app profile for these games, can add the Intel option to that.
Oh, alright. Good to know that it's a quick fix.
sorry i have the same problem here, but a have no clue how can i fix with your files, can you be more specific about the steps that i should go through?
sorry i have the same problem here, but a have no clue how can i fix with your files, can you be more specific about the steps that i should go through?
I believe there was a fix merged for this already, but anyway, this is what I had done if I remember correctly.
# dxgi.hideIntelGpu = Auto
dxgi.hideIntelGpu = True
unfortunately it didnt work again, do you possibly know any othe changes in it?
or any other way?
3 years ago i changed some stuff in .xml file in the documents, but i dont remember it right now, it wasnt a good solution though
for more information i have dx12
ge-proton8-25x1 2023-12proton experimentalx1 2023-12
Software information
This is happening in Far Cry 3 and 4, both latest versions running from Steam. Tried a variety of graphics settings with no change. Does NOT affect the DX9 mode in Far Cry 3.
The games also seem to be a bit brighter than they should be due to this issue.
I tested on Windows 11 too and the same issue happens (with DXVK 2.3). It doesn't happen without DXVK, though this seems to have been an issue in the stock D3D11 renderer at some point according to this post on Intel community.
System information
Screenshots
Apitrace file(s)
Here
Log files
steam-2.tar.gz