Unity-Technologies / Unity-Technologies/NativeRenderingPlugin

How does Vulkan API interception work before VkInstance and VkDevice creating and after that?

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
943
Forks
186
PR merge metrics
No merged PRs in 30d

Description

In my test, I found that the intercept of vkCmdBeginRenderPass by Hook_vkCmdBeginRenderPass in function [ ProcessDeviceEvent ] didn't work in Editor mode.
image

I also intercepted vkCreatInstance in function [ ProcessDeviceEvent ] and it didn't work.

However, if I intercept above APIs in function [ Hook_vkGetInstanceProcAddr ], everything works well.
image

I think I could say that interception in function [ Hook_vkGetInstanceProcAddr ] works definitely .
But when does interception in function [ ProcessDeviceEvent ] work?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing ProcessDeviceEvent and Hook_vkGetInstanceProcAddr in the native rendering plugin, then compare when each callback is reached around VkInstance and VkDevice creation. Done means documenting when ProcessDeviceEvent interception is expected to work, or identifying the change needed to make the reported Editor case work.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, unity
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.