Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with max_push_constant_size at 256 with my vulkan device #47

Open
CatCode79 opened this issue Nov 5, 2021 · 2 comments
Open

Comments

@CatCode79
Copy link

Hi, I'm trying to upgrade Richter to wgpu 0.11 version. (by the way, congratulations on the name of the project, it took me a while to understand it but then it made me smile).

You can find my efforts here: https://github.com/CatCode79/richter

the problem is that my device, using vulkan api, only supports up to 128 bytes of push constants, while Richter uses up to 256 bytes: a Matrix4x4 (so 128 bytes) + other values ​​sometime.

For me who do not know the code it is not trivial to solve this thing.
The limits per vulkan for that variable are a minimum of 128 in the official documentation.

Here the line:

max_push_constant_size: 256,

Is there a chance the code could support the 128 byte limit or will it stay that way?

Thanks for your project: I like it a lot!
bye!

@ethereumdegen
Copy link

ethereumdegen commented Oct 28, 2022

I am working on a fork that uses fewer push constants to support a wider range of graphics hardware. I got it to boot a demo file on my linux laptop with intel mesa integrated gfx recently. https://github.com/antiquake-rs

@CatCode79
Copy link
Author

cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants