vulkan

问题 For resource transitions, you need to know the 'before' and 'after' VkImageLayout of the resource (eg. in the VkImageMemoryBarrier passed to vkCmdPipelineBarrier ). Vulkan does not guarantee any ordering of execution of command buffers, unless explicitly stated in the API documentation (from this answer). However, vkCmdPipelineBarrier does explicitly say that it creates a dependency between commands in the command buffer, before and after the call. So it is possible to 'know' the layout of an

问题 I'm trying to port my OpenGL 3D game engine to Vulkan. There are large numbers of 3D objects in the game scene and each has it own attributes (model matrix, lights, etc.) and the objects are completely dynamic, which means some 3D objects may come in and others may be removed during the game play. with OpenGL, I grouped 3D object's attribute into a uniform buffer in shader (code simplified): layout(std140, set = 0, binding = 0) uniform object_attrib { vec3 light_pos; vec3 light_color; mat4

问题 From the man page for vkEnumerateDeviceExtensionProperties, vkEnumerateDeviceExtensionProperties retrieves properties for extensions on a physical device whose handle is given in physicalDevice. To determine the extensions implemented by a layer set pLayerName to point to the layer’s name and any returned extensions are implemented by that layer. Setting pLayerName to NULL will return the available non-layer extensions. pPropertyCount must be set to the size of the VkExtensionProperties array

问题 At Vulkan specs 1.0.9 (pg. 180), we have the following: typedef struct VkMemoryHeap { VkDeviceSize size; VkMemoryHeapFlags flags; } VkMemoryHeap; and this description: • size is the total memory size in bytes in the heap. • flags is a bitmask of attribute flags for the heap. The bits specified in flags are: typedef enum VkMemoryHeapFlagBits { VK_MEMORY_HEAP_DEVICE_LOCAL_BIT = 0x00000001, } VkMemoryHeapFlagBits; But when I query VkPhysicalDeviceMemoryProperties I've got flags with zero values.

问题 What is the correct way of using a Vulkan VkImage as a CUDA cuArray? I've been trying to follow some examples, however I get a CUDA_ERROR_INVALID_VALUE on a call to cuExternalMemoryGetMappedMipmappedArray() To provide the information in an ordered way. I'm using CUDA 10.1 Base code comes from https://github.com/SaschaWillems/Vulkan, in particular I'm using the 01 - Vulkan Gears demo, enriched with the saveScreenshot method 09 - Capturing screenshots Instead of saving the snapshot image to a

问题 As a lot of "beginner", I thought use TOP_OF_PIPELINE as a dst and BOTTOM_OF_PIPELINE as a src meant ALL_COMMANDS for both. Here Nicol Bolas wrote that "Since top/bottom of the pipe make no sense for memory barriers, maybe using them should just be flat-out invalid. And thus useful only for execution barriers." From what I understand, since TOP and BOTTOM does not perform any access into memory, putting barrier on top or bottom can't make memory visible^^. As I understand what Nicol Bolas

问题 In the simplified scenario where each object to be rendered is translated into a secondary command buffer and each of those command buffers bind a graphics pipeline initially: is a guaranteed no-op to bind the pipeline that was immediately bound before? Or the order of execution of the secondary command buffers is not guaranteed at all? 回答1: is a guaranteed no-op to bind the pipeline that was immediately bound before? No. In fact, in the case you're outlining, you should assume precisely the

问题 I want to play around with mobile Vulkan without having to buy a device. If it is not supported, please provide evidence (e.g. source code, official Google statements). Are there any plans to support it? If supported, please give detailed and tested instructions of how to get a minimal hello world triangle app running, including the app you have tested with. I have tried https://github.com/googlesamples/android-vulkan-tutorials/tree/7ba478ac2e0d9006c9e2e261446003a4449b8aa3/tutorial05_triangle

问题 Background: I want to write a CAD application. I want to implement all rendering with Vulkan. And I want to use GTK+. I don't want a (visible) different window for the rendered image of the object. So I researched and found the GtkGLArea widget, which seems to do what I want, but for OpenGL. Is there an equivalent to GTKGLArea ? If not, is there another way to implement what I'm thinking of? 回答1: There is a GdkWindow which I believe is behind many Gtk graphic types such as GtkWindow and