Skip to content

Commit 18765da

Browse files
kvarkozkriff
andauthored
Newsletter 9: Add gfx-rs news (#116)
* Add gfx-rs news * Newsletter 9: wgpu/gfx: fmt & wording tweaks Co-authored-by: Andrey Lesnikov <[email protected]>
1 parent f714e86 commit 18765da

File tree

2 files changed

+50
-0
lines changed

2 files changed

+50
-0
lines changed
166 KB
Loading

content/posts/newsletter-009/index.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ draft = true
66
+++
77

88
<!-- markdownlint-disable no-trailing-punctuation -->
9+
<!-- markdownlint-enable line-length -->
910

1011
Welcome to the ninth issue of the Rust GameDev Workgroup’s
1112
monthly newsletter.
@@ -146,6 +147,55 @@ _Discussions:
146147

147148
## Library & Tooling Updates
148149

150+
### `gfx-rs` and `wgpu` News
151+
152+
![hectic screenshot: graveyard and vampires](hectic.png)
153+
154+
^ _[hectic-rs] - Rust/wgpu/specs re-write of hectic by [@expenses]_
155+
156+
wgpu-0.5 release happened! See the [changelog][wgpu-0-5].
157+
It's based on `gfx-hal-0.5` (which was covered in the [March newsletter][gfx-march]),
158+
uses in-house gfx-extras crates adopted from Rendy,
159+
has many fixes and improvements, and totally changes the way passes are recorded.
160+
161+
`wgpu` project got restructured by only leaving `wgpu-core` and `wgpu-types`
162+
in the main ("core logic") repository.
163+
`wgpu-native` is moved out into a [separate one][wgpu-native].
164+
`wgpu-remote` got fully moved into mozilla-central as "gfx/wgpu_bindings"
165+
(this is "gfx" in a general sense, not gfx-rs in particular).
166+
167+
The Web target (aka "wasm32-unknown-unknown") is now officially supported
168+
by `wgpu-rs`! 🎉
169+
@grovesNL wrote the announcement to [gfx-rs blog][wgpu-wasm-blog].
170+
171+
At the same time, @kvark was implementing support for WebGPU in Firefox
172+
(Nightly only) with help of `wgpu`.
173+
They published results of this milestone on [Mozilla Hacks][wgpu-in-firefox].
174+
The combined efforts allowed all the `wgpu-rs` examples to be run
175+
in Firefox Nightly on all platforms
176+
(yes, even on Android, terms and conditions apply...).
177+
178+
Given the wide spectrum of uses for `wgpu` ("core"), it became most important
179+
to be able to debug and reproduce visual issues, be it either the user's fault,
180+
or wgpu implementations'.
181+
To aid these scenarios, a new [API tracing infrastructure][wgpu-pr-tracing]
182+
was built into the core.
183+
It's now possible to replay user's `wgpu` workloads in a separate player
184+
on an entirely different platform.
185+
186+
In gfx-rs land, @mistodon created a nice [series of tutorials][gfx-hal-tutorials]
187+
for the gfx-hal API.
188+
189+
[wgpu-0-5]: https://github.com/gfx-rs/wgpu/blob/master/CHANGELOG.md#v05-06-04-2020
190+
[gfx-march]: https://rust-gamedev.github.io/posts/newsletter-008/#gfx-rs-and-wgpu-news
191+
[wgpu-wasm-blog]: https://gfx-rs.github.io/2020/04/21/wgpu-web.html
192+
[wgpu-in-firefox]: https://hacks.mozilla.org/2020/04/experimental-webgpu-in-firefox
193+
[wgpu-native]: https://github.com/gfx-rs/wgpu-native
194+
[wgpu-pr-tracing]: https://github.com/gfx-rs/wgpu/pull/619
195+
[gfx-hal-tutorials]: https://www.falseidolfactory.com/projects/learning-gfx-hal
196+
[hectic-rs]: https://github.com/expenses/hectic-rs
197+
[@expenses]: https://github.com/expenses
198+
149199
### [erupt]
150200

151201
![erupt logo](erupt.png)

0 commit comments

Comments
 (0)