iced-rs/iced

Damage tracking / partial present

Open

#367 opened on May 29, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (1,572 forks)batch import
featurehelp wantedrenderingshell

Repository metrics

Stars
 (30,491 stars)
PR merge metrics
 (Avg merge 24d 11h) (11 merged PRs in 30d)

Description

Damage tracking allows for power savings by not rerendering regions unchanged between frames. There's actually two optimizations made possible by tracking damage: in the desktop compositor (you just tell it the region) and in the application (a bit more tricky, but e.g. I've implemented support in WebRender+EGL recently).

Doesn't look like wgpu supports passing the VkPresentRegionKHR yet, so I've raised an issue for this: https://github.com/gfx-rs/wgpu/issues/682

On the new GL backend though, it should be possible to use EGL_KHR_swap_buffers_with_damage (e.g.).

But first, iced should do the actual tracking :)

Contributor guide

Research direction
Study the current rendering pipeline in iced, identify where damage tracking can be added, and review the Vulkan VkPresentRegionKHR and EGL KHR swap buffers with damage extensions. Look at the references in the issue and similar implementations in other projects to understand the approach.
Tech stack
rust
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60