Render Doctor

There are a lot of different heuristics, guidelines, potential problems, hazards, performance tricks, etc etc that can be summed up by simple rules.

Either per-drawcall or per-frame there should be a way for RenderDoc to find and report these problems based on whatever metrics it has built in. This should basically amount to a checklist for people to look at when trying to diagnose a bug to see if there are any problem areas they should begin looking at if they're not sure where to start, and also to check up on to see if there are ways they can harden or improve their program.

The "Render Doctor" could be a separate window that would open up when a log opens, containing anything that RenderDoc notices or detects for free when parsing a log - for example binding resources for read and write when this will produce unexpected results (one of the bindings may become null) or cases where undefined behaviour is invoked.

In addition, for more heavyweight analysis the user can choose to invoke the tool across either a whole frame, a subset of drawcalls (e.g. one marker section) or just on one drawcall, and RenderDoc can choose the appropriate level of analysis to present back to the user.

This is obviously easily extensible and can be added to as necessary.