7f7f9e987f
Its not standard how `Present Engines` return images for presentation, and currently is expected that they cycle between swap-chain images with each `vkAcquireNextImageKHR` call. However present engines could return any available image, that can mean to reuse the last presented one if available. (This seem to be the behavior using `Layered on DXGI Swapchain` the default `Present Method` used with latest NVIDIA drivers on Windows). Since resource pools expects to images to cycle in a sequential order, if any present engine always return the same image for presentation only a single resource pool would be used for each rendered frame, and since resources are only released by cycling between resource pools, this resource pool would overflow since it never releases any resource. This changes makes resource pools to cycle each time a image is presented. Pull Request: https://projects.blender.org/blender/blender/pulls/131129
Blender
Blender is the free and open source 3D creation suite. It supports the entirety of the 3D pipeline-modeling, rigging, animation, simulation, rendering, compositing, motion tracking and video editing.
Project Pages
Development
License
Blender as a whole is licensed under the GNU General Public License, Version 3. Individual files may have a different, but compatible license.
See blender.org/about/license for details.