From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98146] DRI_PRIME=1 and fullscreen issues
Date: Sat, 22 Oct 2016 16:24:49 +0000 [thread overview]
Message-ID: <bug-98146-502-p6J86DtHII@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98146-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1454 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98146
--- Comment #16 from Darek Deoniziak <darekdeoniziak@gmail.com> ---
Did some more testing with DRI3 and DRI_PRIME=1 to run programs using radeon.
1. is solved with DRI3 as I did mention in last comment
2. Found big new isse about that, screen is not only cutted to half in some
fullscreen games (issue happens while playing Serious Sam 3), but it feels like
gpu plays few frames for few milliseconds then it plays these frames again
(everything feels worse than small fps). It happens not only in fullscreen
applications, if I run genymotion (emulator for Android devices) then the same
thing happens. Changing vsync doesn't help. Dota 2 works fine.
3. flickering still happens and additionaly this flashes from time to time,
usually when window is not focused: http://i.imgur.com/D0XniPL.png The image
also shows cutted screen to half which happens quite often.
4. solved with DRI3, no freezing after closing fullscreen programs
5. solved with DRI3, no issues with external monitor.
What options I could try to solve above issues? 2nd is now the biggest one.
Tried for both radeon and intel:
Option "SwapBuffersWait" "0"
Option "TearFree" "true" (also tried "on", is there any difference?)
Noone did help radeon, intel is working fine for both DRI2 and DRI3 (all above
issues are related radeon).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2307 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-22 16:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:02 [Bug 98146] DRI_PRIME=1 and fullscreen issues bugzilla-daemon
2016-10-07 15:29 ` bugzilla-daemon
2016-10-07 16:33 ` bugzilla-daemon
2016-10-07 16:34 ` bugzilla-daemon
2016-10-07 16:55 ` bugzilla-daemon
2016-10-07 18:27 ` bugzilla-daemon
2016-10-07 18:46 ` bugzilla-daemon
2016-10-07 19:51 ` bugzilla-daemon
2016-10-07 19:53 ` bugzilla-daemon
2016-10-10 9:12 ` bugzilla-daemon
2016-10-11 7:21 ` bugzilla-daemon
2016-10-11 7:32 ` bugzilla-daemon
2016-10-11 7:41 ` bugzilla-daemon
2016-10-20 19:51 ` bugzilla-daemon
2016-10-20 20:27 ` bugzilla-daemon
2016-10-21 5:33 ` bugzilla-daemon
2016-10-22 16:24 ` bugzilla-daemon [this message]
2016-10-22 17:40 ` bugzilla-daemon
2016-10-22 20:52 ` bugzilla-daemon
2016-10-25 6:35 ` bugzilla-daemon
2017-06-25 6:42 ` bugzilla-daemon
2017-06-25 13:35 ` bugzilla-daemon
2017-07-25 12:33 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98146-502-p6J86DtHII@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).