Automatically Resource Allocation && Dependency Graph

[windwhiterain]

After playing with the example "multipass", I found that I still need to explicit "Lease" images or buffer for transient usage. If a chain of operation on a color attachment finally write into "swapchain_image", I can only "copy" the image I leased to swapchain_image rather than telling the graph that all previous operations on that image can be performed directly on swapchain_image.

What's more, I expect "Render Graph" should be a "Dependency Graph". But I didn't found any creation of dependency during building a render graph. After shuffle the order of "begin_pass", I get different result. I think the graph use the order of passes to build a linear dependency, which is not
a "fully featured" render graph I'm afraid.

[attackgoat]

The concept of a lease exists to reduce the number of short-lifespan images, there is no requirement to use them. You may either create images directly or, if you prefer, pass the swapchain image.

If you're getting different results when shuffling the passes I would consider what the passes are actually doing; does it make sense given the shuffling? Doing a read before writes and expecting to read the written data, for example, does not make sense.

I'm open to criticism of the design and welcome constructive feedback, feel free to post code you think should work or things that don't seem correct. If this is more general feedback, perhaps you could use the Discussions tab.

[windwhiterain]

thanks for reply. i'll make a better post in disscusions tomorrow.