You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
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
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:
richter/src/bin/quake-client/main.rs
Line 125 in 506504d
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!
The text was updated successfully, but these errors were encountered: