Skip to content

Conversation

@walley892
Copy link
Contributor

Replace rendering for solid color circles (both filled and stroked) to use SDFs. This change improves the visual quality of circle borders, especially on platforms without MSAA support.

  • Adds a vertex and fragment shader that support SDF rendering for both filled and stroked circles.

  • Adds a Contents subclass, CircleContents that uses these shaders for rendering

  • Modifies Canvas::DrawCircle to use this new contents for drawing circles

  • Only supports circles with a solid color paint. Everything else continues to use the existing behavior

  • Adds a playground test that interactively scales circles to ensure fidelity at all scales.

  • Partially fixes [Impeller] Aliasing artifacts when rendering some SVGs on some Android emulators. #167181

Before (Android emulator):

Screenshot 2025-10-23 at 4 26 18 PM Screenshot 2025-10-23 at 4 29 32 PM

After (Android emulator):

Screenshot 2025-10-23 at 8 48 17 PM Screenshot 2025-10-23 at 4 24 44 PM

Pre-launch Checklist

@walley892 walley892 requested a review from gaaclarke October 24, 2025 04:37
@google-cla
Copy link

google-cla bot commented Oct 24, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@github-actions github-actions bot added engine flutter/engine related. See also e: labels. e: impeller Impeller rendering backend issues and features requests labels Oct 24, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces SDF-based rendering for solid color circles to improve anti-aliasing quality, which is a great enhancement. The changes include new vertex and fragment shaders, a CircleContents class to use these shaders, and modifications in Canvas::DrawCircle to leverage this new path. A new interactive playground test is also added. The implementation looks solid, but I've found a couple of critical duplication issues that will cause build failures, along with several opportunities to improve code clarity and remove dead code.

@gaaclarke
Copy link
Member

@walley892 you're going to have to sign the CLA. if you click that presubmit failure it should link you to getting that resolved

@gaaclarke
Copy link
Member

the ci.yaml validation issue should be able to be resolved by updating your branch (either by merging main or rebasing against main)

Copy link
Member

@gaaclarke gaaclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking really good. Thanks Mr. Walley892. The concerns are:

  1. Usage of fwidth
  2. I want to see how it behaves when scaled
  3. Let's get the ci happy so golden tests run

@walley892 walley892 force-pushed the sdf-circles branch 8 times, most recently from 97fa29e to eb2560a Compare October 24, 2025 21:12
Copy link
Member

@gaaclarke gaaclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, looks good to me. Let's just get CI happy. I think you need to copyright and the others may have been flakes.

Copy link
Member

@chinmaygarde chinmaygarde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have serious misgivings about the direction here. So far, we have avoided having the fragment shaders be concerned about coverage in most cases. This is a notable departure from that approach. That it is being done for cases where there exists a broken MSAA implementation (emulators) makes me question if this is worthwhile.

I think what I am (hopefully incorrectly) concerned about is what happens when such shapes are used in operations where the coverage matters (like clipping). Won't that affect stenciling operations?

This also adds to the pipeline load which makes startup slower (again for the purpose of addressing emulators with broken MSAA).

@gaaclarke
Copy link
Member

I have serious misgivings about the direction here. So far, we have avoided having the fragment shaders be concerned about coverage in most cases. This is a notable departure from that approach. That it is being done for cases where there exists a broken MSAA implementation (emulators) makes me question if this is worthwhile.

I think what I am (hopefully incorrectly) concerned about is what happens when such shapes are used in operations where the coverage matters (like clipping). Won't that affect stenciling operations?

This also adds to the pipeline load which makes startup slower (again for the purpose of addressing emulators with broken MSAA).

I had those conversations with Evan already, I'll throw something on your calendar to discuss it.

@chinmaygarde
Copy link
Member

From the conversation, I was mistaken about the coverage geometry changing. The additional pipeline variant is unfortunate but Aaron says this is a one off. Looks good to me! Thanks for giving the additional context.

@walley892 walley892 force-pushed the sdf-circles branch 2 times, most recently from 2cea4fe to 08326c1 Compare October 28, 2025 18:58
@gaaclarke
Copy link
Member

FYI I'm happy with the code right now. I'm ready to approve when we are happy with the goldens. I think there were a few that mr wally892 wanted to look at. Particularly relating to think tiny rings evaporating from the anti-aliasing.

@walley892
Copy link
Contributor Author

FYI I'm happy with the code right now. I'm ready to approve when we are happy with the goldens. I think there were a few that mr wally892 wanted to look at. Particularly relating to think tiny rings evaporating from the anti-aliasing.

Changed the fragment shader to handle this case. Stroked circles that would be drawn just one pixel wide are just rendered as is with no fading.

frag_info.radius, frag_info.stroke_width, frag_info.center, v_position);
float sdfDistance = mix(dist_filled, dist_stroked, frag_info.stroked);

float pixelDerivativeSDF = fwidth(sdfDistance);
Copy link
Member

@gaaclarke gaaclarke Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you change this file to have consistent variable naming following the c++ style guide? ex pixel_deriviative_sdf

Copy link
Member

@gaaclarke gaaclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm as long as the goldens are happy

@walley892 walley892 enabled auto-merge October 31, 2025 19:56
@gaaclarke gaaclarke dismissed chinmaygarde’s stale review November 4, 2025 18:31

chinmay disregarded this review in a comment but forgot to update the status

@walley892 walley892 added this pull request to the merge queue Nov 4, 2025
Merged via the queue into flutter:master with commit a41146c Nov 4, 2025
185 checks passed
@walley892 walley892 deleted the sdf-circles branch November 4, 2025 20:18
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 5, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 5, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 6, 2025
auto-submit bot pushed a commit to flutter/packages that referenced this pull request Nov 6, 2025
flutter/flutter@e5d5c01...c5e809a

2025-11-06 [email protected] Remove WindowingOwner.hasTopLevelWindows (flutter/flutter#178033)
2025-11-06 [email protected] Fix DropdownMenu escape key does not close the menu (flutter/flutter#178002)
2025-11-06 [email protected] Update documentation tool reference in image.dart (flutter/flutter#177782)
2025-11-06 [email protected] Roll Skia from 4eb2383d38f2 to 5c4e1352128f (5 revisions) (flutter/flutter#178094)
2025-11-06 [email protected] Revert "Refactor OverlayPortal semantics (#173005)" (flutter/flutter#178007)
2025-11-06 98614782+auto-submit[bot]@users.noreply.github.com Reverts "Fix verified input test failure in CI (attempt 4) (#178018)" (flutter/flutter#178089)
2025-11-06 98614782+auto-submit[bot]@users.noreply.github.com Reverts "[web] Unify Surface code between Skwasm and CanvasKit (#177138)" (flutter/flutter#178085)
2025-11-05 [email protected] Fix verified input test failure in CI (attempt 4) (flutter/flutter#178018)
2025-11-05 [email protected] fix: inconsistent horizontal spacing between hours and mins in time picker for non-english language (flutter/flutter#173706)
2025-11-05 [email protected] Roll Fuchsia Linux SDK from mpsxF1gd-jbKNvmpm... to cm88aTLui5yorSGYQ... (flutter/flutter#178074)
2025-11-05 [email protected] Fix(ios): Remove arm64 exclusion to support Xcode 26 simulators (flutter/flutter#177065)
2025-11-05 [email protected] Roll Skia from 2ff897e9b440 to 4eb2383d38f2 (18 revisions) (flutter/flutter#178070)
2025-11-05 [email protected] [web] Unify Surface code between Skwasm and CanvasKit (flutter/flutter#177138)
2025-11-05 [email protected] Update more missing ninja deps (flutter/flutter#178079)
2025-11-05 [email protected] Add ninja / cmake deps to failing tests (flutter/flutter#178054)
2025-11-05 [email protected] [web] Don't add webparagraph suite to CI (flutter/flutter#177681)
2025-11-05 [email protected] Fixing broken link in engine readme (flutter/flutter#177987)
2025-11-05 [email protected] Print reason for adb command failure in verified input test (attempt 3) (flutter/flutter#178005)
2025-11-05 [email protected] Fix `ReorderableList` items jumping when drag direction reverses mid-animation (flutter/flutter#173241)
2025-11-05 [email protected] Replace deprecated `withOpacity` in `overflow_bar.0.dart‎` example (flutter/flutter#177813)
2025-11-05 [email protected] Replace deprecated `withOpacity` in `data_table.1.dart‎` example (flutter/flutter#177812)
2025-11-05 [email protected] Replace deprecated `withOpacity` in `switch.1.dart` example (flutter/flutter#177811)
2025-11-04 [email protected] Roll Skia from c89b6118266b to 2ff897e9b440 (6 revisions) (flutter/flutter#177999)
2025-11-04 [email protected] Fix verified input test in CI (attempt 2) (flutter/flutter#177961)
2025-11-04 [email protected] Replace rendering for solid color circles (both filled and stroked) to use SDFs (flutter/flutter#177482)
2025-11-04 [email protected] Roll Fuchsia Linux SDK from vxK5obzfr1X9P2kSh... to mpsxF1gd-jbKNvmpm... (flutter/flutter#177996)
2025-11-04 [email protected] Validate that platforms specified in .ci.yaml target names match the platforms defined in the platform_properties section (flutter/flutter#177523)
2025-11-04 [email protected] Roll Packages from 1a7075b to 3d926aa (6 revisions) (flutter/flutter#177998)
2025-11-04 [email protected] Remove dead code from snippet_generator (flutter/flutter#174440)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages
Please CC [email protected] on the revert to ensure that a human
is aware of the problem.

To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
IvoneDjaja pushed a commit to IvoneDjaja/flutter that referenced this pull request Nov 22, 2025
…o use SDFs (flutter#177482)

Replace rendering for solid color circles (both filled and stroked) to
use SDFs. This change improves the visual quality of circle borders,
especially on platforms without MSAA support.

- Adds a vertex and fragment shader that support SDF rendering for both
filled and stroked circles.
- Adds a `Contents` subclass, `CircleContents` that uses these shaders
for rendering
- Modifies `Canvas::DrawCircle` to use this new contents for drawing
circles
- Only supports circles with a solid color paint. Everything else
continues to use the existing behavior
- Adds a playground test that interactively scales circles to ensure
fidelity at all scales.


- Partially fixes flutter#167181


Before (Android emulator):

<img width="236" height="245" alt="Screenshot 2025-10-23 at 4 26 18 PM"
src="https://github.com/user-attachments/assets/566de15e-95d3-4b5d-963c-1cebba4aeb50"
/>
<img width="383" height="394" alt="Screenshot 2025-10-23 at 4 29 32 PM"
src="https://github.com/user-attachments/assets/7ca29be6-89f4-43e6-bd9a-c4ec4179ab1c"
/>


After (Android emulator):

<img width="383" height="394" alt="Screenshot 2025-10-23 at 8 48 17 PM"
src="https://github.com/user-attachments/assets/f138bedc-edc3-4cba-a982-bd3020d9e44c"
/>
<img width="236" height="245" alt="Screenshot 2025-10-23 at 4 24 44 PM"
src="https://github.com/user-attachments/assets/6b5bec91-e3aa-4daa-9233-3a407b1f1378"
/>

## Pre-launch Checklist

- [x ] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x ] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x ] I read and followed the [Flutter Style Guide], including
[Features we expect every widget to implement].
- [x ] I signed the [CLA].
- [x ] I listed at least one issue that this PR fixes in the description
above.
- [x ] I updated/added relevant documentation (doc comments with `///`).
- [x ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x ] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x ] All existing and new tests are passing.

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
reidbaker pushed a commit to AbdeMohlbi/flutter that referenced this pull request Dec 10, 2025
…o use SDFs (flutter#177482)

Replace rendering for solid color circles (both filled and stroked) to
use SDFs. This change improves the visual quality of circle borders,
especially on platforms without MSAA support.

- Adds a vertex and fragment shader that support SDF rendering for both
filled and stroked circles.
- Adds a `Contents` subclass, `CircleContents` that uses these shaders
for rendering
- Modifies `Canvas::DrawCircle` to use this new contents for drawing
circles
- Only supports circles with a solid color paint. Everything else
continues to use the existing behavior
- Adds a playground test that interactively scales circles to ensure
fidelity at all scales.


- Partially fixes flutter#167181


Before (Android emulator):

<img width="236" height="245" alt="Screenshot 2025-10-23 at 4 26 18 PM"
src="https://github.com/user-attachments/assets/566de15e-95d3-4b5d-963c-1cebba4aeb50"
/>
<img width="383" height="394" alt="Screenshot 2025-10-23 at 4 29 32 PM"
src="https://github.com/user-attachments/assets/7ca29be6-89f4-43e6-bd9a-c4ec4179ab1c"
/>


After (Android emulator):

<img width="383" height="394" alt="Screenshot 2025-10-23 at 8 48 17 PM"
src="https://github.com/user-attachments/assets/f138bedc-edc3-4cba-a982-bd3020d9e44c"
/>
<img width="236" height="245" alt="Screenshot 2025-10-23 at 4 24 44 PM"
src="https://github.com/user-attachments/assets/6b5bec91-e3aa-4daa-9233-3a407b1f1378"
/>

## Pre-launch Checklist

- [x ] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x ] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x ] I read and followed the [Flutter Style Guide], including
[Features we expect every widget to implement].
- [x ] I signed the [CLA].
- [x ] I listed at least one issue that this PR fixes in the description
above.
- [x ] I updated/added relevant documentation (doc comments with `///`).
- [x ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x ] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x ] All existing and new tests are passing.

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

e: impeller Impeller rendering backend issues and features requests engine flutter/engine related. See also e: labels. will affect goldens Changes to golden files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Impeller] Aliasing artifacts when rendering some SVGs on some Android emulators.

5 participants