Dzmitry Malyshau

Thank you for filing this! Unfortunately, we are not supporting the old pre-ll release any more. We would accept patches, at most.

> the lifetime of when exactly the name should be applied is a little unclear I don't know why Baldur finds this unclear. To me, it's as clear as Vulkan...

Thank you for the report! Reading the issue, I'm slightly confused. It was reported on dx12 originally (in https://github.com/parasyte/pixels/issues/49#issuecomment-554403950), was it? But then at the end the report says it...

If they have a problem on Vulkan, and it's within adapter enumeration, the good thing to ask would be to run any `ash` examples.

Thanks for the info @pluth ! @parasyte we already have [limited feature blacklisting](https://github.com/gfx-rs/gfx/blob/147b64c4432fe16ef2c866b20f538dc5686bc59d/src/backend/vulkan/src/lib.rs#L846) but we aren't checking for the driver version yet. Let this issue be a task to add...

@ceranco it may very well be that Intel isn't interested in updating the driver for this GPU, since it's quite old...

I played around it, and it appears to be more painful than it seems. Our CPU-visible memory has an associated buffer to it, but Metal's `synchronize_resource` doesn't take a range...

Whatever we expose will likely be based on Khronos efforts, and there isn't anything yet to target, see https://github.com/KhronosGroup/Vulkan-Docs/issues/686

Let me expand on the previous answer. Surely, there are many targets that support *some* way of raytracing. However, Vulkan itself doesn't have a vendor-independent API for this, and we...

@tangmi thank you for the interest! We definitely can get *something* today (compatible with Metal, DX12, and VK NVidia), but we'll potentially have to rewrite this later when https://github.com/KhronosGroup/Vulkan-Docs/issues/686 is...