fix(deps): update rust crate wgpu to 0.17.0 #38
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.16.1
->0.17.0
Release Notes
gfx-rs/wgpu (wgpu)
v0.17.0
Compare Source
This is the first release that featured
wgpu-info
as a binary crate for getting information about what devices wgpu sees in your system. It can dump the information in both human readable format and json.Major Changes
This release was fairly minor as breaking changes go.
wgpu
types now!Send
!Sync
on wasmUp until this point, wgpu has made the assumption that threads do not exist on wasm. With the rise of libraries like
wasm_thread
making it easier and easier to do wasm multithreading this assumption is no longer sound. As all wgpu objects contain references into the JS heap, they cannot leave the thread they started on.As we understand that this change might be very inconvenient for users who don't care about wasm threading, there is a crate feature which re-enables the old behavior:
fragile-send-sync-non-atomic-wasm
. So long as you don't compile your code with-Ctarget-feature=+atomics
,Send
andSync
will be implemented again on wgpu types on wasm. As the name implies, especially for libraries, this is very fragile, as you don't know if a user will want to compile with atomics (and therefore threads) or not.By @daxpedda in #3691
Power Preference is now optional
The
power_preference
field ofRequestAdapterOptions
is now optional. If it isPowerPreference::None
, we will choose the first available adapter, preferring GPU adapters over CPU adapters.By @Aaron1011 in #3903
initialize_adapter_from_env
argument changesRemoved the backend_bits parameter from
initialize_adapter_from_env
andinitialize_adapter_from_env_or_default
. If you want to limit the backends used by this function, only enable the watned backends in the instance.Added a compatible surface parameter, to ensure the given device is able to be presented onto the given surface.
By @fornwall in #3904 and #3905
Misc Breaking Changes
AdapterInfo::{device,vendor}
to beu32
instead ofusize
. By @ameknite in #3760Changes
buffer_from_raw
(Dx12, Metal, Vulkan) andcreate_buffer_from_hal
. By @AdrianEddy in #3355Vulkan
Added/New Features
TextureFormat
s. By @teoxoy in #3843.Documentation
GPUVertexBufferLayout
. By @fornwall in #3906DEPTH32FLOAT_STENCIL8
by @ErichDonGubler in #3734.AdapterInfo::{device,vendor}
by @ErichDonGubler in #3763.descriptor.usage
is not empty increate_buffer
by @nical in #3928max_bindings_per_bind_group
limit to reflect spec changes by @ErichDonGubler and @nical in #3943 #3942Bug Fixes
General
SurfaceConfiguration
. by @liquidev in #3817Vulkan
Metal
DX12
WebGPU
get_preferred_canvas_format()
to fillformats
ofSurfaceCapabilities
. By @jinleili in #3744Examples
v0.16.3
Compare Source
Changes
General
Id
type that is exposed when using theexpose-ids
feature implementSend
andSync
again. This was unintentionally changed by the v0.16.0 release and is now fixed.v0.16.2
Compare Source
Changes
DX12
max_storage_buffers_per_shader_stage
andmax_storage_textures_per_shader_stage
limits based on what the hardware supports. by @Elabajaba in [#3798]https://github.com/gfx-rs/wgpu/pull/3798Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.