“Downlevel flags VIEW_FORMATS are required but not supported on the device.”

[Raj2032]

I am using (Arch)Linux and I am currently using the Blue Engine

And I have a very simple project:

use blue_engine::{header::{Engine, Renderer, ObjectStorage, /*ObjectSettings,*/ WindowDescriptor, PowerPreference}, Window};

fn main()
{
    println!("Hello, world!");

    let mut engine = Engine::new(); // This is where it screws up
}

As soon as I add this line let mut engine = Engine::new(); it "panics" with this error message:

Hello, world!
[2023-05-07T10:19:28Z ERROR wgpu::backend::direct] Handling wgpu errors as fatal by default
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_texture
      note: label = `Default Texture`
    Downlevel flags VIEW_FORMATS are required but not supported on the device.
This is not an invalid use of WebGPU: the underlying API or device does not support enough features to be a fully compliant implementation. A subset of the features can still be used. If you are running this program on native and not in a browser and wish to work around this issue, call Adapter::downlevel_properties or Device::downlevel_properties to get a listing of the features the current platform supports.

"Downlevel flags VIEW_FORMATS are required but not supported on the device." It looks like I might need to disable the VIEW_FORMATS flag or something? In the previous version of blue engine it would work fine on the exact same computer and OS but the current version has this issue.

I got another person with a different computer to run the project and it works fine for him so not too sure why all of a sudden its not working for me?

I am using amdgpu drivers, not raedeon drivers.

[Wumpf]

WebGPU added requirement for being able to specify the view format and wgpu checks against that now. Blue engine probably had an older version of wgpu before that didn't have this requirement yet.

That said, the only place where this feature isn't supported is on wgpu's GLES & WebGL backend. On linux you should always use Vulkan whenever possible.
In any case, this would be a bug with blue engine for not picking the correct backend and/or requiring this feature when they also want to suport GLES/WebGL (?, don't know blue engine at all)

[Raj2032]

On linux you should always use Vulkan whenever possible.

So if I understood correctly, if blue engine configured WGPU to use Vulkan backend, then I shouldn't get this issue? ------- Original Message -------

…

On Sunday, May 7th, 2023 at 11:55 PM, Andreas Reich ***@***.***> wrote: WebGPU added requirement for being able to specify the view format and wgpu checks against that now. Blue engine probably had an older version of wgpu before that didn't have this requirement yet. That said, the only place where this feature isn't supported is on wgpu's GLES & WebGL backend. On linux you should always use Vulkan whenever possible. In any case, this would be a bug with blue engine for not picking the correct backend and/or requiring this feature when they also want to suport GLES/WebGL (?, don't know blue engine at all) — Reply to this email directly, [view it on GitHub](#3755 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AG7P2BXA23FDYQ4RENRQPOLXE6SUTANCNFSM6AAAAAAXY2LNIE). You are receiving this because you authored the thread.Message ID: ***@***.***>

[Wumpf]

Yep. Depending on the engine chooses the backend, the WGPU_BACKEND environment variable might work, but that's really the engine's choice how to expose these things or if at all. Instead, blue engine should set the required downlevel flags correctly when it requests a wgpu device.

[teoxoy]

@Wumpf thanks for helping with this!

It looks like there is nothing for us to do here; closing.