Skip to content

Renderer Rework: Initial Merge Tracking Issue #2535

Closed
@cart

Description

@cart

The Bevy Renderer Rework is starting to stabilize and it is time to start planning how to upstream it! The intent of this issue is to track the work required to merge the renderer rework as soon as possible. This isn't a "renderer feature wishlist". But feel free to discuss what you think should be on this list!

This is an issue to track work that still needs to be done. If there is a name in parentheses, that work has been claimed by someone.

For some history on this effort, check out:

Here is a list of open prs against the pipelined-rendering branch

Missing Required Features

The new renderer must have (approximate) feature parity with the old renderer.

Missing Nice-To-Have Features

These aren't required for a merge, but would be very nice to have.

Discussions To Have Before Merging

  • Consider RenderDevice + RenderQueue -> GpuDevice + GpuQueue
  • Consider using atomic counter instead of UUID for render resource ids
  • Should we keep the BevyDefault trait?
  • Agree on the final "shadow enable/disable" api

Steps to Merge

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-MetaAbout the project itselfA-RenderingDrawing game state to the screenC-FeatureA new feature, making something new possibleC-Tracking-IssueAn issue that collects information about a broad development initiative

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions