[Merged by Bors] - news: release 0.7.0#334
Conversation
|
How can we tell which commits you've already made a stub / writeup for? Do you remove them from Edit: commits that have been covered are indented, as it says in the PR description 🤦🏽♀️ |
I think I already answered this in the PR description. |
|
I definitely think the benefits of compressed texture support in terms of load times and RAM usage warrant a section in the article. |
|
Oh, is the list of highlights at the top the list of sections that will be in the article? I wonder if a before and after of performance since 0.6.1 would be good too. There should be a significant difference. I'll test in bistro and check. |
I would love to see both this and |
DJMcNab
left a comment
DJMcNab
left a comment
There was a problem hiding this comment.
I've done a first pass, and I'm broadly happy.
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Co-authored-by: Daniel McNab <36049421+DJMcNab@users.noreply.github.com>
| * **Cluster Assignment Optimizations**: The cluster assignment data access patterns and data structures received a variety of tweaks that improved performance. | ||
|
|
||
| // TODO: Show many lights video here | ||
| // TODO: Add iterative sphere refinement here if it is merged |
There was a problem hiding this comment.
It isn't yet, but the PR does fix a bug with orthographic projections, though we haven't yet been able to isolate what part of the PR fixes it as we had implemented the new algorithm and then fixed problems we saw along the way, thinking they were caused by the new algorithm, but I guess maybe it works better now? :)
Cover 0.7 docs improvements
Co-authored-by: Ida Iyes <40234599+inodentry@users.noreply.github.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
Co-authored-by: Robert Swain <robert.swain@gmail.com>
|
|
||
| <div class="release-feature-authors">authors: @mockersf</div> | ||
|
|
||
| [`Sprite`] components can now define an [`Anchor`] point, which determines the "origin" of the sprite. Sprites still default to a "center" origin, but this is now configurable: |
There was a problem hiding this comment.
I think it is also worth including the term/keyword "pivot point" somewhere in this description. A lot of people know it by that name and might be searching for that.
Co-authored-by: Ida Iyes <40234599+inodentry@users.noreply.github.com>
|
bors r+ |
This is a draft of the Bevy 0.7.0 blog post. Note that it is still _very_ incomplete. Sections are missing, as are some screenshots, videos, and "real numbers". I've included my "commit files" to help illustrate progress + organization. I've sorted roughly by category and then indented commits that have been covered. I dont intend to cover every commit, but its a rough indicator of progression. Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
|
Pull request successfully merged into master. Build succeeded: |
# Problem These were missed in #334. # Solution Yeet!
9 participants
This is a draft of the Bevy 0.7.0 blog post.
Note that it is still very incomplete. Sections are missing, as are some screenshots, videos, and "real numbers".
I've included my "commit files" to help illustrate progress + organization. I've sorted roughly by category and then indented commits that have been covered. I dont intend to cover every commit, but its a rough indicator of progression.