From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106053] Drawing at screen boundary is very slow.
Date: Sun, 15 Apr 2018 10:08:20 +0000 [thread overview]
Message-ID: <bug-106053-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1953 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106053
Bug ID: 106053
Summary: Drawing at screen boundary is very slow.
Product: Mesa
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
Assignee: dri-devel@lists.freedesktop.org
Reporter: cosiekvfj@o2.pl
QA Contact: dri-devel@lists.freedesktop.org
CC: alexdeucher@gmail.com, emil.l.velikov@gmail.com,
Hi-Angel@yandex.ru, lemody@gmail.com,
madbiologist2016@outlook.com, maraeo@gmail.com,
mark.a.janes@intel.com, michel@daenzer.net,
nhaehnle@gmail.com, notasas@gmail.com
Created attachment 138844
--> https://bugs.freedesktop.org/attachment.cgi?id=138844&action=edit
bitmap for testing
When a partially visible sprites are drawn to the screen, fps drops really
badly.
code tested:
https://gist.github.com/vfjpl/bd442e34036547e4ccb05200762fa274
fully visible = 73.8 fps
fully invisible = 394 fps
partially visible = 5.75 fps
The same situation is happening on Allegro library. I don't know enough OpenGL
to test it directly.
I can provide more test results. Just ask me to do it.
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org R300 Project (0x1002)
Device: ATI RC410 (0x5a62)
Version: 17.3.7
Accelerated: yes
Video memory: 128MB
Unified memory: no
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
And small question. Why Max core profile shows 0.0? Should I open another
bug-report?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3544 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 reply other threads:[~2018-04-15 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 10:08 bugzilla-daemon [this message]
2018-04-15 10:16 ` [Bug 106053] Drawing at screen boundary is very slow bugzilla-daemon
2018-04-15 15:40 ` bugzilla-daemon
2018-04-16 21:55 ` bugzilla-daemon
2018-04-16 22:05 ` bugzilla-daemon
2018-04-17 1:22 ` 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-106053-502@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