The new generation of low-level rendering APIs introduced the concept of “Resource Transitions“: The API user is responsible for keeping track how a memory resource is used and make explicit transitions in the command-list. Most common example: Use a texture as rendertarget and vice versa.
(This is definitely true for DirectX12 and Mantle, but I do not know for sure about the upcoming Vulkan-API… although it would surprise me if they handle it differently)
How to handle this concept in a render abstraction?
- No abstraction, pass burden of transition to user
- Highlevel renderer should know best, most resources don’t need any transition anyways
- Zero extra overhead
- If something goes wrong, the debug layer should be able to do the hard validation work
- Tedious to keep track
- May want to implement automatism anyway
- Error prone: Old APIs don’t care, debug layer of new API might miss something
- Go single-threaded and record resource usage (always only one)
- Trivial way to remove all resource transitions from userland
- Defeats an important point of the new APIs!
- Create extra command lists at submission to fill in unknown transitions
- Excellent explanation here
- Fully automatic and still multi-threaded, no locks
- Requires two levels of resource state tracking
- Need to create command lists on the fly (or pre-cached) – how costly is that?
- Record command lists multi-threaded in custom data structure without sending any commands to the API. When all lists are ready, missing resource transition infos can be propagated. Only then the API-side command lists are generated
- Has anybody tried that?
- Manual recording needs may be necessary to emulate multi-threading with old APIs anyway
- Requires multiple threading barriers
- Two step recording introduces a lot of overhead
In DirectX12 resource transitions are a special form of Resource Barriers.
Resource barriers in general were already in place in the old APIs, e.g. the infamous glMemoryBarrier. A common usage example are unordered access views, where the question weather caches need to be flushed or not depends entirely on the shader operating on it (usage example here). None of the discussed approaches is able to abstract such UAV Barriers entirely away, without generating too many of them. More or less the same goes for Aliasing Barriers (different resources on the same memory).
For the ClearSight project I am torn between the “no abstraction” and the “command list fill-in” which sounds reasonable to me (and hey, a guy on the official DX12 edu channel told us about it!). Automating the process or resource transitions sounds very attractive is probably a must-have for every serious render-abstraction. However, I don’t think it is trivial to implement in a robust and fast fashion. And as I mentioned it cannot abstract all resource barriers.
So for now I will just pass the burden to the user. I am curious how much extra work this actually means to the implementer of a high level rendering pipeline. I suspect that it should be fairly simple since most transitions are made deliberately. Assuming the API debug layer catches all missing transitions, it should also make it easier to see where unnecessary overhead was introduced:
An automatic system may fill in all transitions, but does not report where the graphics programmer did not intend to perform transitions.