When running the Call to Arms game with dxvk on Windows, sometimes abnormal rendering occurs.
Please describe your issue as accurately as possible.
If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows
Software information
Call to Arms https://store.steampowered.com/app/302670/Call_to_Arms/
System information
GPU: NVIDIA GeForce GTX 1660 SUPER Driver: 516.94.0 Wine version: N/A (windows 11) DXVK version: v1.10.3
Apitrace file(s)
- N/A
Log files
- d3d11.log:call_to_arms_d3d11.log
- dxgi.log:call_to_arms_dxgi.log
Additional info
- Game can work with dxvk
- Occasionally there will be abnormal rendering screen
-
Can you post a screenshot without DXVK so we know whats broken here? I assume it's the lighting on the containers.
Please make an apitrace.
Here is the screenshot without DXVK...
Sometimes instead of completely losing the rendering, the picture flickers between the rendering and the black model, but in the dx11 environment I don't have these problems.
Here is the an apitrace of game.(17/09/2022) https://send.vis.ee/download/03c13dcd108cd579/#myqYLpHcaInI8XBp88q4sQ The url is invalid after twenty downloads or seven days.
I tried checking the trace on both my AMD and Nvidia setup on Linux but everything looked fine. Will try to install the game here when i have time to check it out.
In the mean time can you try and see if latest master makes a difference? You can grab a build here https://github.com/doitsujin/dxvk/actions/runs/3071878973
Thank you for Blisto91 recommending the latest master makes version Dxvk, The rendering problem was improved.
But it is interesting that the Msi afterburner did not render the display card information.
By improved do you mean it is gone or?
Yes, the display card information is not displayed as usual.
I'm not sure what you mean by display card information in MSI afterburner. Do you mean a ingame overlay? If yes then yes there's a chance it won't work with dxvk on windows. It's recommended to disable such stuff usually as it can cause issues.
@semmyenator friendly ping
The rendering problem was improved.
As far as I understand it, that means the bug is fixed.