https://bugs.winehq.org/show_bug.cgi?id=26712
--- Comment #9 from Henri Verbeet hverbeet@gmail.com --- (In reply to Bruno Jesus from comment #8)
Is any log useful to check this? Would it be possible to make only the game window or virtual desktop to receive the gamma changes?
You'd see (probably a lot of) SetDeviceGammaRamp() calls in +dc, and wined3d_swapchain_set_gamma_ramp() calls in +d3d if it's going through D3D. The gamma ramps are a property of the CRTC/screen, so you can't set it per-window. It's usually not really an issue because applications typically only do this kind of thing in full-screen mode, although sometimes it's visible on Windows as well on e.g. multi-head setups or when switching away from full-screen windows. For things that set the gamma ramp through D3D it would in theory be possible to do the gamma correction in a post-processing shader instead, although I'm not convinced that would be desirable. For things that go directly through gdi32 it would be harder, although perhaps it could be done when flushing window surfaces.
Of course if you just don't want the application to mess with the display gamma, you can disable UseXVidMode, but then you probably won't get fading at all.