A host visible VkImage is not intended for staging, I believe it's largely intended to be useful for situations where you want to display a stream of images that were generated on the CPU (e.g. When I took a course in grad school on statistical image processing, I saw a very interesting plot where data is shown as a surf plot and underneath, on the ground or x-y plane, an image is shown. You might find it works well enough for your first attempts to get something on screen, but you'll soon run into device-specific limitations that prevent VkImage staging buffers working for mipmaps, compressed textures, array textures or anything remotely exotic.īasically a VkBuffer is the correct tool for the job of being a staging buffer for texture data. T he surface / surf plot in MATLAB can visualize data in 3D. The problem with copying via a VkImage is that your temporary staging allocation is subject to the driver's limitations on host-visible images. To use the STABiX toolbox, some experimental data are required: average grain orientations (Euler angles ( 1,, 2) in degrees) or intragranular misorientation (misorientation axis u v w / angle ) grains boundaries positions (optional for the bicrystal analysis) grains positions (optional for the bicrystal. Copying via VkImage may work in limited cases, but you'll almost certainly find yourself removing that code at a later date. If we're talking about using a staging allocation during transfer of data from CPU to GPU then basically, copying via a VkBuffer is the correct way to do it. What is the difference between copying CPU data to the GPU via a VkImage and a VkBuffer?
0 kommentar(er)
