Contradicting error message when creating a buffer for MAP_READ and COPY_DST after upgrading to 0.14.2

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/rust_gamedev
#Applications written in Rust #Graphics #Webgpu #Rust #native-libraries

Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • InfluxDB - Access the most powerful time series database as a service
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors

  • wgpu

    Safe and portable GPU abstraction in Rust, implementing WebGPU API.

    Hello everyone, wasn't sure if this is a bug or if I am missing something here but for some reason the following buffer (that worked in wgpu 0.13.1): let some_buffer = device.create_buffer(&wgpu::BufferDescriptor { label: Some("Some Label"), size: (std::mem::size_of::()) as u64, usage: wgpu::BufferUsages::STORAGE | wgpu::BufferUsages::MAP_READ | wgpu::BufferUsages::COPY_DST, mapped_at_creation: false, }); no longer works after upgrading to wgpu 0.14.2 and the error message I receive is: Caused by: In Device::create_buffer note: label = `Some Label` `MAP` usage can only be combined with the opposite `COPY`, requested MAP_READ | COPY_DST | STORAGE This doesn't make sense, since MAP_READ is the opposite of COPY_DST (right?). Also, I saw that this error message is not a new addition in 0.14.2 (in this issue, where it made sense). What am I missing?

  • SonarQube

    Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts