Vecvec
Vecvec
I think we are violating this rule (it's written as an allow in the other direction) > when using SPIR-V versions 1.4 and earlier: Block, BufferBlock, Offset, ArrayStride, and MatrixStride...
This would definitely be possible, glfw-sys builds glfw from source, so this would likely be possible. The main reason not to do that would be because to compile with support...
I think @Jaisiero had an implementation working (https://github.com/gfx-rs/wgpu/issues/1040#issuecomment-2460208883).
> procedural ray query is pretty involved (Niagara support? Naga support was added in #7047 (if that's what you're asking about).
I know they are on `trunk`, I *think* they were released in v25 as well. If you are adding features it's usual to target `trunk` though.
This also happens (for similar reasons) with TLASes.
I just remembered that structures have minimum versions, and it seems [`MTLIndirectAccelerationStructureInstanceDescriptor`](https://developer.apple.com/documentation/metal/mtlindirectaccelerationstructureinstancedescriptor) required MacOS 14.0+ (probably should have checked that earlier...).
> @Vecvec: What testing hardware do you have available? Can you maybe see why Vulkan is failing this too? I've got a couple of raytracing supported machines (plus llvmpipe which...
Hits a divide by zero on Microsoft Basic Render Driver (though it doesn't seem to be related to the memory used, and only on one of my comuters). Can't get...
Most other resources are created with an auto release pool around them, is it possible that that is fixing this issue somehow?