It was happening in my own code, but it also 100% reproduces for me in the examples. Simply build the examples, run and hit the window close button.

Seems to be something relating to it still being inside renderFrame() during bgfx::shutdown().

<img width="1582" alt="Screenshot 2019-12-25 at 14 38 40" src="https://user-images.githubusercontent.com/621629/71447311-a7752680-2724-11ea-8a29-c2eae

	dependencies[0].srcSubpass = VK_SUBPASS_EXTERNAL;
	dependencies[0].dstSubpass = 0;
	dependencies[0].srcStageMask = VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT;
	dependencies[0].dstStageMask = VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT;
	dependencies[0].srcAccessMask = VK_ACCESS_MEMORY_READ_BIT;
	dependencies[0].dstAccessMask = VK_ACCESS_COLOR_ATTACHMENT_READ_BIT | VK_ACCESS_COLOR_ATTACHME

We use PIX labels to organize the events in a single frame (e.g. Z PrePass, GBuffer, Alpha, etc). These can get quite deep/nested.

It would be useful if we could see a 'path' for the event currently selected, e.g.

Camera 1\3D Stage\GBuffer\TreeBark Material

It would be extra nice if clicking on any of these would take you to the beginning of that section.
(think folders in Windows Explor

It is unclear from the provided documentation what the difference is between a chunk and a subbuffer. Without examples it can be very difficult to identify when using one instead of the other may be necessary. We spent multiple days tracking down why an attempt to pass a subbuffer of vertices to a call to draw() was failing to compile. The error message was extremely verbose, but ultimately see

The Forge sounds pretty great but there does not seem to be much in the way of documentation.

I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.

The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects pi

Also optionally, if we make backwards incompatible changes to the config file we should notify users somehow. (E.g. changing defaults).

example

// Flags type as declared in https://www.khronos.org/registry/vulkan/specs/1.0/man/html/VkFlags.html
type Flags uint32

seems to me a couple of issues with providing documentation as links to documentation.

1. in the case above the link target has changed, or rather is redirected, in the case above its to https://www.khronos.org/registry/vulkan/specs/1.1-extensions/man/html/