Rua
Rua
Image offsets are compared with the `min_texel_gather_offset` device property as u64 instead of i32.
A nice example of how evil `as` can be!
Why not just use a timeout of 1 second? That's more than is reasonably enough.
Yeah that fixed it.
The PR is what disabled the check. This issue is to remind us to fix the issues that led it to be disabled, so that it can be re-enabled.
Do you get any validation errors if you enable the validation layer?
I've reported the bug to KDE: https://bugs.kde.org/show_bug.cgi?id=498694
For example, the `SurfacePresentModeCompatibilityEXT` struct is set up like this before calling `get_physical_device_surface_capabilities2_khr`: ```rust capabilities_present_mode_compatibility_vk.insert( ash::vk::SurfacePresentModeCompatibilityEXT::default() .present_modes(&mut capabilities_present_modes_vk), ) ``` After the call is complete, I'm trying to pass both...
Note: setting `present_modes` to an empty slice doesn't work. Because that method returns the input type with the same lifetime; it does not create a new lifetime based on the...
I'm running into this limitation too. I have to choose between losing the pointed type, or losing the segment.
But do you think it's wise to force using an unstable feature? I think this project is a good idea overall, but I don't think it can be opinionated on...