Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Sa 01.06.2024 00:04:08 73.481 +1 2.286.694 31,1 Mastodon 4.2.8 500 Fr 31.05.2024 00:03:14 73.480 0 2.283.188 31,1 Mastodon 4.2.8 500 Do 30.05.2024 00:04:25 73.480 0 2.280.533 31,0 Mastodon 4.2.8 500 Mi 29.05.2024 00:05:19 73.480 0 2.277.905 31,0 Mastodon 4.2.8 500 Di 28.05.2024 00:04:58 73.480 0 2.275.687 31,0 Mastodon 4.2.8 500 Mo 27.05.2024 00:03:13 73.480 0 2.273.895 30,9 Mastodon 4.2.8 500 So 26.05.2024 00:02:07 73.480 0 2.272.417 30,9 Mastodon 4.2.8 500 Sa 25.05.2024 00:01:58 73.480 0 2.270.260 30,9 Mastodon 4.2.8 500 Fr 24.05.2024 00:02:09 73.480 -1 2.267.583 30,9 Mastodon 4.2.8 500 Do 23.05.2024 00:02:13 73.481 0 2.264.857 30,8 Mastodon 4.2.8 500
Litherum (@litherum) · 11/2022 · Tröts: 2.156 · Folger: 392
Sa 01.06.2024 22:14
Here's a Vulkan question: Why is VkImageTiling not just part of VkImageLayout?
https://registry.khronos.org/vulkan/specs/1.3-khr-extensions/html/chap12.html#resources-image-layouts says "Images are stored in implementation-dependent opaque layouts in memory."
https://registry.khronos.org/vulkan/specs/1.3-khr-extensions/html/chap12.html#VkImageTiling says "tiling ... specifies the tiling arrangement of texel blocks in an image"
Those sound like the same thing.
The only difference I can find is that vkCmdPipelineBarrier() can be used to transition an image between layouts, but tiling seems to be immutable. But, like, why?
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web