[Bug 106053] Drawing at screen boundary is very slow.

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- 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

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

--- Comment #1 from Hi-Angel <Hi-Angel@yandex.ru> ---
Can't comment on the rest, but

> And small question. Why Max core profile shows 0.0? Should I open another bug-report?

This is because the OpenGL version r300g supports didn't have the separation to
core/compat profile. See also this comment
https://bugs.freedesktop.org/show_bug.cgi?id=103506#c8

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1522 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

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

Marek Olšák <maraeo@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTABUG
             Status|NEW                         |RESOLVED

--- Comment #2 from Marek Olšák <maraeo@gmail.com> ---
r300-r500 hardware capabilities don't meet the requirements of OpenGL core
profile.

r300g on RC410 uses software emulation for vertex shaders and clipping (the
same code as llvmpipe), because the hardware doesn't have any vertex processor
and clipper.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2223 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

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 812 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

--- Comment #3 from Roland Scheidegger <sroland@vmware.com> ---
(In reply to Marek Olšák from comment #2)
> r300g on RC410 uses software emulation for vertex shaders and clipping (the
> same code as llvmpipe), because the hardware doesn't have any vertex
> processor and clipper.
Can't the chip do guardband clipping? I thought all radeon chips (starting from
r100) could do this, regardless if they support hw tnl.
I could be wrong though (and I wouldn't know how large the guardband would be,
and certainly draw's handling of guardband if you enable it is a bit lacking,
since hw has fixed limits whereas draw will use a guardband twice the size of
the viewport).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1715 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

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 439 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

--- Comment #4 from Marek Olšák <maraeo@gmail.com> ---
I think the hw doesn't have a clipper, though it shouldn't be hard to verify if
it's true. Yeah, draw could use some optimizations for the clipper, e.g. the
guardband, but simply doing culling (not clipping) should be enough for point
sprites.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1258 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

[Bug 106053] Drawing at screen boundary is very slow.

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

--- Comment #5 from Roland Scheidegger <sroland@vmware.com> ---
(In reply to Marek Olšák from comment #4)
> I think the hw doesn't have a clipper, though it shouldn't be hard to verify
> if it's true. Yeah, draw could use some optimizations for the clipper, e.g.
> the guardband, but simply doing culling (not clipping) should be enough for
> point sprites.

That's what I meant with guardband clipping: there's no actual clipping, but
the hw will still cull pixels outside the viewport. Hence it probably would be
better if draw wouldn't clip if a primitive doesn't fit into the viewport, but
fits into the (hw) guardband. (And you are right that point sprites are a bit
of a special case.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1745 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