Skip to content

[Flutter GPU] Allow specifying the mip levels/slices to use for overwriting a texture. #145015

Closed

Description

@bdero

Depends on #145014.

Activity

  1. moved this to 🤔 Needs Triage in Flutter GPUon Mar 12, 2024
  2. moved this from 🤔 Needs Triage to 💡 Features in Flutter GPUon Mar 12, 2024
  3. added
    engineflutter/engine related. See also e: labels.
    c: proposalA detailed proposal for a change to Flutter
    on Mar 13, 2024
  4. added
    P2Important issues not at the top of the work list
    on Mar 18, 2024
  5. self-assigned this
    on Jun 18, 2024
  6. bdero commented on Jun 18, 2024

    @bdero
    MemberAuthor

    Making the attachment piece of this a separate issue.

  7. changed the title [-][Flutter GPU] Allow specifying the mip level/slice for Texture attachments and Uploads.[/-] [+][Flutter GPU] Allow specifying the mip levels/slices to use for writing a texture.[/+] on Jun 18, 2024
  8. changed the title [-][Flutter GPU] Allow specifying the mip levels/slices to use for writing a texture.[/-] [+][Flutter GPU] Allow specifying the mip levels/slices to use for overwriting a texture.[/+] on Jun 18, 2024
  9. bdero commented on Jun 18, 2024

    @bdero
    MemberAuthor
    • When creating a Texture with GpuContext.createTexture, allow specifying the mip level count, default to 1.
    • Allow specifying the mipLevel and slice for Texture.overwrite. We can always add something like Texture.overwriteRange later on for uploading/overwriting ranges of mip levels/slices.
  10. removed their assignment
    on Jul 29, 2024
  11. bdero commented on May 1, 2026

    @bdero
    MemberAuthor

    For this to be usable end-to-end, #185883 (allow specifying mipLevelCount on createTexture) also needs to land. Without it, every flutter_gpu texture has exactly one mip level and there is no non-zero mipLevel for Texture.overwrite to address.

  12. self-assigned this
    on May 11, 2026
  13. moved this from 💡 Features to ✅ Done in Flutter GPUon May 12, 2026
  14. added a commit that references this issue on May 12, 2026
    7571305
  15. github-actions commented on May 26, 2026

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  16. locked as resolved and limited conversation to collaborators on May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listc: proposalA detailed proposal for a change to Flutterengineflutter/engine related. See also e: labels.flutter-gputeam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions