VkFramebuffer is gone in future versions or vulkan? By what was it replaced? (I am being lazy here, asking instead of going to read the latest specs). I coded

VkFramebuffer is gone in future versions or vulkan? By what was it replaced? (I am being lazy here, asking instead of going to read the latest specs). I coded my everyday video player using vulkan (very conservative), I would move my code to this new thingy once it's in mesa. What I liked with vulkan, on the main thread of my video player, I just post vulkan non-blocking commands, I don't even need a video thread! I can even use the main thread to mix fast enough the audio data! NIR is a sweet spot for me (lean C89 code with benign bits of c99/c11), even though I would like a configure "switch" to remove all non-breaking algebraic optimizations from the vulkan drivers (I used to do that myself for a good while, near 0 performance impact) since it is redondant because those should be directly done in spir-v code. Since I am an AMD user (I play video games, now all the ones I play have a vulkan backend), even if I really dislike a bloody lot c++, I am grateful to valve for ACO (because llvm is beyond toxic, even from a c++ point of view). But I wish ACO would manage to add the possibility for hand-coded assembly shaders (AMDGPU ISA is public and really ez to code), just need a few relocation types (writing an assembler should not be a nightmare like with hw architectures using bazillions of relocation types).