http://bugs.winehq.org/show_bug.cgi?id=26410
Summary: Wine sets gamma incorrectly - probably uses the obsolete xgamma interface instead of xrandr interface Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: hramrach@centrum.cz
When I start a d3d game the gamma on the other monitor changes.
- this is probably an action taken by the program that triggers the gamma change, it only happens on entering certain scenes
- there is a 'xgamma' utility that sets gamma on the other monitor as wine does and is unable to set gamma on any other monitor
- I tried to set the "Use XRandr" registry from N to Y but Wine would still only set gamma on the wrong monitor as xgamma does
http://bugs.winehq.org/show_bug.cgi?id=26410
Michal Suchanek hramrach@centrum.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64 Version|unspecified |1.3.15
http://bugs.winehq.org/show_bug.cgi?id=26410
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown Summary|Wine sets gamma incorrectly |d3d game sets gamma |- probably uses the |incorrectly |obsolete xgamma interface | |instead of xrandr interface |
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2011-03-14 01:06:44 CDT --- What "d3d game" is that?
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #2 from Henri Verbeet hverbeet@gmail.com 2011-03-14 05:37:13 CDT --- Yeah, this is not a D3D thing. Wined3d just uses SetDeviceGammaRamp(), which ends up calling X11DRV_XF86VM_SetGammaRamp() in winex11.drv. This indeed uses the XVidMode extension, not XRRSetCrtcGamma().
http://bugs.winehq.org/show_bug.cgi?id=26410
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |winex11.drv
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #3 from Michal Suchanek hramrach@centrum.cz 2011-03-16 16:48:12 CDT --- XVidMode probably should not be used at all on screens with XRandr support.
Either the XVidMode extension is broken or it is used incorrectly in Wine (and the X utilities).
http://bugs.winehq.org/show_bug.cgi?id=26410
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #4 from André H. nerv@dawncrow.de 2011-10-04 12:08:02 CDT --- i doubt it helps much, but as i did some recent gamma work, could you please try again?
@Henri: if we add a wrapped driver entry point for XRRSetCrtcGamma the functions in gdi32 would be able to choose that XRandr one. I'm not quite sure how it chooses it, is it alphabetical or something like the last used driver? The question is also if we then easily know on which display to change the gamma...
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #5 from Michal Suchanek hramrach@gmail.com 2011-10-04 14:18:10 CDT --- AFAICT the current behaviour is exactly the same as above.
Anyway, setting gamma on the crtc is generally wrong, it should be set on the window.
Failing that you *can* figure out which crtc to set because both window and crtc areas are available in screen coordinates.
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #6 from Henri Verbeet hverbeet@gmail.com 2011-10-05 07:58:06 CDT --- In principle there are functions like MonitorFromWindow() that would let you find the monitor the window is on. They probably don't work correctly in Wine at the moment because we just pretend there's one large monitor though. And yeah, I think the Windows behavior is to set the gamma based on which window currently has the focus, or something along those lines.
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #7 from Austin English austinenglish@gmail.com 2013-11-13 16:52:15 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
http://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #8 from Michal Suchanek hramrach@gmail.com 2013-11-14 03:14:23 CST --- Seen this bug recently with wine 1.6.
https://bugs.winehq.org/show_bug.cgi?id=26410
Reuben reuben_p@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |reuben_p@yahoo.com
https://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #9 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=26410
--- Comment #10 from Austin English austinenglish@gmail.com --- Over 2 years with no reply, marking abandoned.
https://bugs.winehq.org/show_bug.cgi?id=26410
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|UNCONFIRMED |RESOLVED
--- Comment #11 from Gijs Vermeulen gijsvrm@gmail.com --- Resolving.
https://bugs.winehq.org/show_bug.cgi?id=26410
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
--- Comment #12 from mrdeathjr28@yahoo.es --- Dont resolved still appears in hawx
https://bugs.winehq.org/show_bug.cgi?id=26410
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|ABANDONED |--- Ever confirmed|0 |1
--- Comment #13 from André H. nerv@dawncrow.de --- reopening then