Firestar99

Results 50 issues of Firestar99

This is a collection of a bunch of smaller shader-related bugs and issues I came across, including ones which only trigger when using rust-gpu. See changelog below, and these non-user...

# Template * Version of vulkano: current master (9b6e3075699dfd85d2e4c6eb65b726c417f1f8ed) * OS: Ubuntu 23.10, KDE on Wayland * GPU: * [RADV](http://vulkan.gpuinfo.org/displayreport.php?id=25819#properties_core_10) * [AMDVLK](http://vulkan.gpuinfo.org/displayreport.php?id=26306#properties_core_10) # Issue I was messing about with VariableDescriptorCount,...

My Professor recommended your framework as a potential baseline for my master's thesis. So I attempted to get it working on my Ubuntu 23.10 machine with Clion and [according to...

https://github.com/cg-tuwien/Auto-Vk-Toolkit/issues/189

I wanted to explore your library in RenderDoc, specifically how you handle images, for some inspiration on my own rust-based rendering engine. But it seems like you don't have any...

This PR adds support for arrays of buffer descriptors, and represents them like this in rust-gpu: ```rust #[spirv(fragment)] pub fn main( #[spirv(descriptor_set = 0, binding = 4, storage_buffer)] sized_buffer: &mut...

## Description Using the payload of vulkan mesh shaders has been quite troublesome, both with RenderDoc and some drivers. There seems to be quite a disagreement on how the payload...

Bug
Need More Info

Adds support for subgroup intrinsics, see [GL_KHR_shader_subgroup](https://github.com/KhronosGroup/GLSL/blob/main/extensions/khr/GL_KHR_shader_subgroup.txt) and [SPIRV spec 3.49.24. Non-Uniform Instructions](https://registry.khronos.org/SPIR-V/specs/unified1/SPIRV.html#_group_and_subgroup_instructions). Note that the glsl extension only exposes spirv's `OpGroupNonUniform*` instructions, and NOT the `OpGroup*` instructions which can...

* added `DescriptorSet::invalidate()` to make vulkano forget about resources that bound to a descriptor_set, so they can be freed. As (normal) descriptors are validated when bound, this is entirely safe...

1. [ ] Update documentation to reflect any user-facing changes - in this repository. 2. [ ] Make sure that the changes are covered by unit-tests. 3. [x] Run `cargo...