[Bug 46193] New: Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

Bug ID: 46193
           Summary: Incorrect display refresh rates in games & w/
                    dxgi-factory.exe test utility
           Product: Wine
           Version: 3.21
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 62854
  --> https://bugs.winehq.org/attachment.cgi?id=62854
Output of test utility with WINEDEBUG=xrandr

Tested most recently with Battlefield 5, the in-game resolution selector shows
odd refresh rates that are much too low - between 50-66Hz on a 144Hz display.
I've attached the output from a test utility included with DXVK that also
duplicates the issue with cleaner log output than the game.

List of 1440p examples:
  2560x1440 @ 50
  2560x1440 @ 51
  2560x1440 @ 52
  2560x1440 @ 53
  2560x1440 @ 54

xrandr correctly reports my display as 144Hz:
DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis)
598mm x 336mm
   2560x1440     59.95 + 144.00*  120.00    99.95    84.98

Test utility from: 
https://github.com/doitsujin/dxvk/tree/master/tests/dxgi

Also interesting is that it's detecting my GPU incorrectly as a GTX 470, not an
RTX 2080, which the utility looks to be pulling from 'desc.DeviceId'.

This was tested on a clean wine 3.21 install without dxvk or any other
alterations.

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

George Gibbs  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

Józef Kucia  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |directx-d3d
                 CC|                            |[e-mail]

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

--- Comment #1 from Henri Verbeet  ---
I think that's mostly just NVIDIA RandR returning bogus refresh rates. At some
point you could fix that by disabling the "DynamicTwinView" option, but it's
been several years now since I last used the proprietary NVIDIA driver.

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

--- Comment #2 from George Gibbs  ---
(In reply to Henri Verbeet from comment #1)
> I think that's mostly just NVIDIA RandR returning bogus refresh rates. At
> some point you could fix that by disabling the "DynamicTwinView" option, but
> it's been several years now since I last used the proprietary NVIDIA driver.

Running just 'xrandr' does correctly report 144Hz though, is there something
else I should run to confirm that it's an Nvidia bug?

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

--- Comment #3 from Henri Verbeet  ---
(In reply to George Gibbs from comment #2)
> Running just 'xrandr' does correctly report 144Hz though, is there something
> else I should run to confirm that it's an Nvidia bug?

Maybe "xrandr --q1"

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

--- Comment #4 from George Gibbs  ---
(In reply to Henri Verbeet from comment #3)
> (In reply to George Gibbs from comment #2)
> > Running just 'xrandr' does correctly report 144Hz though, is there something
> > else I should run to confirm that it's an Nvidia bug?
>
> Maybe "xrandr --q1"

Ok, that does confirm that this is an Nvidia issue I think.

$ xrandr --q1
 SZ:    Pixels          Physical       Refresh
*0   2560 x 1440   ( 602mm x 341mm )  *50   51   52   53   54

This still seems to impact wine more than other applications though - native
games see it correctly as does both Gnome and KDE. Is there some better way to
poll available resolutions and refresh rates that they are using?

[Bug 46193] Incorrect display refresh rates in games & w/ dxgi-factory.exe test utility

https://bugs.winehq.org/show_bug.cgi?id=46193

--- Comment #5 from George Gibbs  ---
I got a reply from aplattner @ nvidia regarding this which may be helpful. I'm
just going to paste it here:
> The RandR 1.1 interface predates having multiple monitor support in the
> X server, so the only way it has to identify display configurations is
> with a (resolution, refresh rate) pair. The NVIDIA driver supports
> configurations that would look identical to RandR 1.1, so the driver
> assigns sequentially increasing "refresh rate" numbers so that the RandR
> 1.1 modes are unique. This behavior is documented in the readme:
> https://download.nvidia.com/XFree86/Linux-x86_64/415.13/README/faq.html#WhyI...
> Nowadays, Wine could use RandR 1.2, which is aware of multiple monitors
> and capable of configuring the display timings (including refresh rate)
> and scaling parameters on a per-monitor basis. However, due to a
> disagreement over the intended behavior of RandR 1.2 interfaces, Wine
> does not use it and instead relies on the older RandR 1.1 interface. You
> can read more about the history of that decision here:
> https://bugs.winehq.org/show_bug.cgi?id=34348