https://bugs.winehq.org/show_bug.cgi?id=37966
--- Comment #3 from Adam Bolte abolte@systemsaviour.com --- I downloaded the simple application QRes to test (http://qres.sourceforge.net/). After installation, I selected "Add QRes" and "I want to create a new shortcut on the Desktop, applying QRes to a program I select." and clicked Next. Then I selected notepad.exe and clicked Next. Under Desktop area, there is a slider of all available screen resolutions.
With the patch I can see all resolutions I posted in the "xrandr --q1" output. Without it, I only see 1920x1080 and the slider does not move. Note that the QRes app doesn't actually seem to work though, beyond detecting what it perceives as available resolutions.
So the patch does appear to report the resolutions as intended. Without the patch, I can see Dead Space 3 and Call of Juaraz (the two I just tested again) do only see 1920x1080. I copied my Dead Space 3 install to Windows, and observed many resolutions selectable in the game using that environment. I'll note that the list of resolutions in Windows is not the same as those shown via the "xrandr --q1" command, but since it's all faked through GPU scaling, I guess that doesn't really matter and can be manually changed by the user. Whatever's there should be made available to Wine apps.
I'm guessing the problem is that your patch causes games to see new resolutions (demonstrated with QRes to be true), and some of them now attempt to load code for these new resolutions (possibly for a loading screen or intro video that the app would normally resize internally). Then elsewhere, the code in Wine that handles the actual resolution switching (which was previously not possible since the resolution could never be changed) isn't working with RandR 1.1 properly and causing these application failures.