Antialiased MirSurfaceItems impact spread rendering performance
Bug #1507813 reported by
Loïc Molinari
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtmir (Ubuntu) |
In Progress
|
High
|
Loïc Molinari |
Bug Description
MirSurfaceItem uses QSGDefaultImageNode for rendering its textured surface. When antialiasing is enabled on a QtQuick node, the whole node is forced to be rendered in the translucent pass of the renderer and the batching is prevented. This is problematic for the spread because all the surfaces are stacked and early-z culling can't be used by the GPUs.
Another antialiasing technique should be provided in order to optimize the spread.
Related branches
lp://staging/~loic.molinari/qtmir/qtmir-custom-mirsurfacenode
On hold
for merging
into
lp://staging/qtmir
- Mir development team: Pending requested
-
Diff: 1279 lines (+1095/-21)13 files modifiedCMakeLists.txt (+2/-1)
src/modules/Unity/Application/CMakeLists.txt (+2/-0)
src/modules/Unity/Application/mirsurfaceitem.cpp (+44/-20)
src/modules/Unity/Application/mirsurfaceitem.h (+11/-0)
src/modules/Unity/Application/mirsurfacenode.cpp (+736/-0)
src/modules/Unity/Application/mirsurfacenode.h (+55/-0)
src/modules/Unity/Application/resources.qrc (+10/-0)
src/modules/Unity/Application/shaders/edge.frag (+24/-0)
src/modules/Unity/Application/shaders/edge.vert (+74/-0)
src/modules/Unity/Application/shaders/fill.frag (+24/-0)
src/modules/Unity/Application/shaders/fill.vert (+26/-0)
src/modules/Unity/Application/shaders/offsetfill.vert (+64/-0)
src/modules/Unity/Application/shaders/opaquefill.frag (+23/-0)
affects: | qtmir → qtmir (Ubuntu) |
To post a comment you must log in.