Diligent::IDeviceContextVk struct
#include <Graphics/GraphicsEngineVulkan/interface/DeviceContextVk.h>

Exposes Vulkan-specific functionality of a device context.

Reference
- Base classes
- Public functions

Base classes

struct IDeviceContext: Device context interface.

Public functions

auto TransitionImageLayout(ITexture* pTexture, VkImageLayout NewLayout) -> void METHOD() virtual: Transitions internal vulkan image to a specified layout.
auto BufferMemoryBarrier(IBuffer* pBuffer, VkAccessFlags NewAccessFlags) -> void METHOD() virtual: Transitions internal vulkan buffer object to a specified state.
auto LockCommandQueue() -> ICommandQueueVk*METHOD() virtual: Locks the internal mutex and returns a pointer to the command queue that is associated with this device context.
auto UnlockCommandQueue() -> void METHOD() virtual: Unlocks the command queue that was previously locked by IDeviceContextVk::LockCommandQueue().

Function documentation

void METHOD() Diligent::IDeviceContextVk::TransitionImageLayout(ITexture* pTexture, VkImageLayout NewLayout) virtual

Transitions internal vulkan image to a specified layout.

Parameters
pTexture in	- texture to transition
NewLayout in	- Vulkan image layout this texture to transition to

void METHOD() Diligent::IDeviceContextVk::BufferMemoryBarrier(IBuffer* pBuffer, VkAccessFlags NewAccessFlags) virtual

Transitions internal vulkan buffer object to a specified state.

Parameters
pBuffer in	- Buffer to transition
NewAccessFlags in	- Access flags to set for the buffer

ICommandQueueVk*METHOD() Diligent::IDeviceContextVk::LockCommandQueue() virtual

Locks the internal mutex and returns a pointer to the command queue that is associated with this device context.

Returns	- a pointer to ICommandQueueVk interface of the command queue associated with the context.

Remark

Only immediate device contexts have associated command queues.

      The engine locks the internal mutex to prevent simultaneous access to the command queue.
      An application must release the lock by calling IDeviceContextVk::UnlockCommandQueue()
      when it is done working with the queue or the engine will not be able to submit any command
      list to the queue. Nested calls to LockCommandQueue() are not allowed.
      The queue pointer never changes while the context is alive, so an application may cache and
      use the pointer if it does not need to prevent potential simultaneous access to the queue from
      other threads.

      The engine manages the lifetimes of command queues and all other device objects,
      so an application must not call AddRef/Release methods on the returned interface.