https://bugs.winehq.org/show_bug.cgi?id=30328
--- Comment #11 from Béla Gyebrószki gyebro69@gmail.com --- (In reply to Matteo Bruni from comment #10)
(In reply to Béla Gyebrószki from comment #9)
(In reply to Matteo Bruni from comment #8)
This looks fixed for me on Nvidia drivers 349.16.
I wonder if Nvidia will apply the fix in their legacy drivers as well? Still present here with the 340.76 drivers.
Actually I talked to a Nvidia dev yesterday (not knowing yet that this was fixed after the 340.xx series) and I got a "no" back as an answer unfortunately.
I'm disappointed to say the least :(
Matteo, would you be so kind and test bug #30045 for me? I think it's another driver related issue which is still present in their 340.76 drivers. I couldn't reproduce that issue with nouveau. Maybe that bug is fixed as well in the latest Nvidia drivers.