Skip to content

Add gfx-rs news to newsletter 9 #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 2, 2020
Merged

Add gfx-rs news to newsletter 9 #116

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c0fc61e
Add gfx-rs news
kvark May 1, 2020
ee30ca4
Merge branch 'source' into patch-1
ozkriff May 2, 2020
1367a5e
Newsletter 9: wgpu/gfx: fmt & wording tweaks
ozkriff May 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion content/posts/newsletter-009/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,20 @@ If needed, a section can be split into subsections with a "------" delimiter.

## Library & Tooling Updates

### gfx-rs and wgpu news

Copy link
Member

Choose a reason for hiding this comment

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

Maybe there's some image from the updates that can be used here? Any ideas?

wgpu-0.5 release happened! See the [changelog](https://github.com/gfx-rs/wgpu/blob/master/CHANGELOG.md#v05-06-04-2020). It's based on `gfx-hal-0.5` (which we covered in the [March newsletter](https://rust-gamedev-preview.netlify.app/posts/newsletter-008/#gfx-rs-and-wgpu-news)), uses in-house gfx-extras crates adopted from Rendy, has many fixes and improvements, and totally changes the way passes are recorded.

`wgpu` project got restructured by only leaving `wgpu-core` and `wgpu-types` in the main ("core logic") repository. `wgpu-native` is moved out into a [separate one](https://github.com/gfx-rs/wgpu-native/). `wgpu-remote` got fully moved into mozilla-central as "gfx/wgpu_bindings" (this is "gfx" in a general sense, not gfx-rs in particular).

The Web target (aka "wasm32-unknown-unknown") is now officially supported by `wgpu-rs` :tada: @grovesNL wrote the announcement to [gfx-rs blog](https://gfx-rs.github.io/2020/04/21/wgpu-web.html).

At the same time, @kvark was implementing support for WebGPU in Firefox (Nightly only) with help of `wgpu`. They published results of this milestone on [Mozilla Hacks](https://hacks.mozilla.org/2020/04/experimental-webgpu-in-firefox/). The combined efforts allowed us to run all the `wgpu-rs` examples in Firefox Nightly on all platforms (yes, even on Android, terms and conditions apply...).

Given the wide spectrum of uses for `wgpu` ("core"), it became most important to be able to debug and reproduce visual issues, be it either the user's fault, or our implementations'. To aid these scenarios, a new [API tracing infrastructure](https://github.com/gfx-rs/wgpu/pull/619) was built into the core. We are now able to replay your `wgpu` workloads in a separate player on an entirely different platform.

In gfx-rs land, @mistodon created a nice [series of tutorials](https://www.falseidolfactory.com/projects/learning-gfx-hal/) for the gfx-hal API.

## Popular Workgroup Issues in Github

<!-- Up to 10 links to interesting issues -->
Expand Down Expand Up @@ -116,4 +130,4 @@ TODO: Add real links and un-comment once this post is published
-->

[/r/rust_gamedev]: https://reddit.com/r/rust_gamedev
[@rust_gamedev]: https://twitter.com/rust_gamedev
[@rust_gamedev]: https://twitter.com/rust_gamedev