Git Product home page Git Product logo

Comments (8)

marcdownie avatar marcdownie commented on June 13, 2024

Ah; looks like I'm at least missing #96. Anything else?

from wgpu-py.

marcdownie avatar marcdownie commented on June 13, 2024

Additionally it's (now) VK_INSTANCE_LAYERS="VK_LAYER_KHRONOS_validation"

from wgpu-py.

almarklein avatar almarklein commented on June 13, 2024

This is indeed a problem. Usually setting the RUST_BACKTRACE does not help much, because the additional info is not that useful. Getting #96 should help, especially since the eventual goal of wgpu-native is to validate everything and never panic. Because it's supposed to run from a browser too ;)

So yeah, the situation w.r.t. error messages is far from great now, but it will definitely get better over time!

from wgpu-py.

Korijn avatar Korijn commented on June 13, 2024

Now that #96 is closed and released, are we in a better shape here?

from wgpu-py.

almarklein avatar almarklein commented on June 13, 2024

We're indeed in much better shape. But it would help if we also are able to select the debug version instead of release. That should turn on the Vulkan validation layers. So let's leave this open to track that.

from wgpu-py.

Korijn avatar Korijn commented on June 13, 2024

We're indeed in much better shape. But it would help if we also are able to select the debug version instead of release. That should turn on the Vulkan validation layers. So let's leave this open to track that.

Well, at least in development we can already do that. At runtime you could do it with the environment variable.

But we could make it easier, by including it in the package.

from wgpu-py.

almarklein avatar almarklein commented on June 13, 2024

But we could make it easier, by including it in the package.

Yeah, since we do ship the debug library (we do, right?) I think it would be nice to provide a way to use these without having to know the file path. Perhaps setting the env variable to "debug".

from wgpu-py.

Korijn avatar Korijn commented on June 13, 2024

But we could make it easier, by including it in the package.

Yeah, since we do ship the debug library (we do, right?) I think it would be nice to provide a way to use these without having to know the file path. Perhaps setting the env variable to "debug".

We don't, but I'll make it happen :) It's not very hard

from wgpu-py.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.