Bug 99528 - Wine game doesn't redraw properly in fullscreen
Summary: Wine game doesn't redraw properly in fullscreen
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-25 02:28 UTC by Fabian Maurer
Modified: 2018-08-02 00:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Trace from the game (6.06 MB, application/x-7z-compressed)
2017-01-25 02:28 UTC, Fabian Maurer
Details

Description Fabian Maurer 2017-01-25 02:28:20 UTC
Created attachment 129133 [details]
Trace from the game

The windows game DXBall doesn't properly redraw in fullscreen mode.
I assume it's an radeonsi bug, since others reported it working fine. Also, LIBGL_ALWAYS_SOFTWARE makes it render properly, although fairly slow.

Apitrace attached, notice how the upper half is a static image while the lower half is how it should look like.
Also noteworthy is that it works sometimes. Seemingly random, the fullscreen game either renders fine or displays just a static image from the first menu.

System
-Arch 64bit
-Radeon R9 285 using amdgpu and opensource driver
-Mesa 17.1.0-devel (git-0054dded03)

Game in question: http://www.blitwise.com/Scorched_Reality/DXBall19.EXE
Just run it with wine2.0
Comment 1 fin4478 2017-02-04 12:51:09 UTC
DXBall runs fine with 32-bit wineprefix, wine-2.0 (Staging), custom ~agd5f/linux/?h=drm-next-4.11-wip kernel, Debian testing Xfce and RX460.
Comment 2 fin4478 2017-02-04 13:19:19 UTC
...and using latest Oibaf ppa.
Comment 3 Fabian Maurer 2017-02-04 13:53:33 UTC
Still present for me with mesa 88752.3f064e9a40 and linux 4.9.6.
Comment 4 fin4478 2017-02-05 18:40:26 UTC
(In reply to Fabian Maurer from comment #3)
> Still present for me with mesa 88752.3f064e9a40 and linux 4.9.6.

Those stock kernels have very little new  amdgpu and radeon drivers code (see diff in kernel.org), use latest drivers when you make bug reports. This kernel is latest and stable:
https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.11-wip
Comment 5 fin4478 2017-02-05 18:43:23 UTC
Also Debian testing Xfce is more stable, easier and compatible than Arch Linux.
Comment 6 Fabian Maurer 2017-02-05 23:00:06 UTC
(In reply to fin4478 from comment #4)
> Those stock kernels have very little new  amdgpu and radeon drivers code
> (see diff in kernel.org), use latest drivers when you make bug reports. This
> kernel is latest and stable:
> https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.11-wip
Thanks, didn't know that. There's also
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next

Which one of those should I chose, they both seem to be fairly recent. But why is it 4.11?
Comment 7 Michel Dänzer 2017-02-06 06:54:39 UTC
(In reply to fin4478 from comment #4)
> Those stock kernels have very little new  amdgpu and radeon drivers code
> (see diff in kernel.org), use latest drivers when you make bug reports.

There is no such requirement. Depending on the circumstances, we may ask bug reporters to try a newer kernel, but in this case it seems unlikely that the problem is kernel related.


> This kernel is latest and stable:
> https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.11-wip

This is the development tree for the amdgpu/radeon drivers, with changes going into the Linux 4.11 release, which will only get its first release candidate after the final 4.10 release. I.e. it's cutting edge, *not* stable.
Comment 8 Timothy Arceri 2018-07-04 23:01:04 UTC
Is this still an issue?
Comment 9 Fabian Maurer 2018-07-07 21:28:27 UTC
No, I can't reproduce the problem anymore. Also not when using mesa 17.1 - don't really know where it's fixed, but it works reliably now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.