Antarctic Coder

Results 28 comments of Antarctic Coder

Could anyone give me some feedback on the memory address system for acceleration structure. I'd just like a second pair of eyes on the implementation. Thanks

@billhollings I’m sorry, I’ve been busy with since I have began school and never got around to finishing this PR. I am interested in receiving compensation for finishing up `VK_KHR_acceleration_structure`....

@billhollings Just sent you an email.

Looking at [`VkAccelerationStructureGeometryDataKHR`](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkAccelerationStructureGeometryDataKHR.html) and `MTLAccelerationStructureTriangleGeometryDescriptor` seem to be almost identical with a few minor differences. One I noticed was the in the index type for the geometry descriptor, Vulkan allows...

@natevm I'm not sure if I'm looking in the wrong place however this link to the metal documentation seems to tell us the max count for some of these properties...

@rcaridade145 Thanks, I think `MTLAccelerationStructureSizes.accelerationStructureSize` could be used for the [`vkGetAccelerationStructureBuildSizesKHR`](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkGetAccelerationStructureBuildSizesKHR.html) function which provides the expected acceleration structure size.

Is it possible to get a scratch buffer from it's device address? Looking at the Metal API documentation, there's basically nothing on device addresses, except for a single property on...

I believe I saw this during my research, but I probably didn't read the docs properly. I'll try it out later. Thanks @rcaridade145

@K0bin This looks quite interesting, I'll see if i can get an efficient map working later.

@natevm The only real blocking issue is how accelerations are handled in gpu memory because we have copy commands and noncommand copies. The solution seems to MTLHeaps accoring to a...