Yes, this is a somewhat common issue on Windows and I don't know why it happens. We query available display modes from existing win32 APIs and expose them to the application in pretty much the same way that native DXGI would. Any help in resolving it without breaking wine would be appreciated.
On windows, just delete all resolutions from your EDID with CRU, so the only one left is 1920x1080@165hz (inside CTA-861)
To add some context here, it looks like the game confuses the numerator with the denominator and sets them the other way around. That is causing dxvk to pick the lowest supported refresh rate, but that's allegedly similar to native behavior?
WineD3D picks the highest supported refresh rate.
On setups where this is a problem or can't be addressed otherwise, the newly introduced d3d9/dxgi.forceRefreshRate option can be used to get the game on the preferred mode.
Nothing extracted yet.
Titan Quest Anniversary Edition (with all DLCs). Running under W10 19044.1645 x64. Using latest DXVK release. It works great for my RX480 card (60Hz) but for some weird reason instead of 1920x1080x165Hz, it sets 50Hz mode.
Reports with no log files will be ignored.
Software information
Titan Quest Anniversary Edition (with all DLCs).
System information
Apitrace file(s)
Log files
TQ_d3d11.log
TQ_dxgi.log