You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BLASes referenced during a TLAS build (if provided) are recorded into the buildAccelerationStructures command in the pool.
Now just time for callbacks.
@Crisspl I also added that feature you wanted `bool IGPUCommandBuffer::recordReferences(const std::span<const IReferenceCounted*> refs);`
// [optional] Provide info about what BLAS references to hold onto after the build
478
+
// [optional] Provide info about what BLAS references to hold onto after the build. For performance make sure the list is compact (without repeated elements).
// We don't allow different indirect command addresses due to https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkCmdBuildAccelerationStructuresIndirectKHR-pIndirectDeviceAddresses-03646
@@ -305,9 +303,7 @@ class NBL_API2 IGPUCommandBuffer : public IBackendObject
// If the user wants the builds to be tracking, and make the TLAS remember the BLASes that have been built into it.
873
+
// NOTE: We know that a TLAS may be rebuilt multiple times per frame on purpose and not only the final BLASes need to be kept alive till submission finishes.
874
+
// However, the Command Pool already tracks resources referenced in the Build Infos, so we only need pointers into those records.
0 commit comments