Use dispatchable handles instead of tracking object relationships about vulkan-performance-layers HOT 6 CLOSED

Yes, this is a related section. You can find full context in Paul's comment with the suggestion on how to implement it: #18 (comment). The implementation in https://github.com/google/gf-layers/blob/master/src/VkLayer_GF_frame_counter/src/frame_counter_layer.cc uses vulkan objects exactly like we want.

from vulkan-performance-layers.

@Hardik0307 cool, the next step would be to make sure that everything builds and you get some output with the layers enabled. You need a working Vulkan installation for that, either configured for your physical GPU, or a software-based one with something like swiftshader. See scripts/gen_sample_output.sh for instructions on generating sample output.
When your change is in a reasonable shape, just submit a pull request.

from vulkan-performance-layers.

Hey @kuhar want to work on this.

from vulkan-performance-layers.

Hi @Hardik0307, great! Feel free to ask any questions under this issue.

from vulkan-performance-layers.

Hi @Hardik0307, great! Feel free to ask any questions under this issue.
Creating dispatchable objects

is this helpful?

from vulkan-performance-layers.

@kuhar,
I've studied one layer frame_time_layer
and made changes in FrameTimeLayer_QueuePresentKHR like this

  auto device = layer_data->GetDevice.Get(DeviceKey(queue));
  
 auto next_proc = layer_data->GetNextDeviceProcAddr(
      device, &VkLayerDispatchTable::QueuePresentKHR);
  return (next_proc)(queue, present_info);

Review.

from vulkan-performance-layers.