Add a FAQ page for common problems and their solutions

Overv · Overv · commit c1fe4a63417e · 2017-09-20T18:40:40.000+02:00
diff --git a/00_Introduction.md b/00_Introduction.md
@@ -112,4 +112,9 @@ in mind that once you have that boring looking triangle, drawing fully textured
 3D models does not take that much extra work, and each step beyond that point is
 much more rewarding.
 
+If you encounter any problems while following the tutorial, then first check the
+FAQ to see if your problem and its solution is already listed there. If you are
+still stuck after that, then feel free to ask for help in the comment section of
+the closest related chapter.
+
 Ready to dive into the future of high performance graphics APIs? [Let's go!](!Overview)
diff --git a/03_Drawing_a_triangle/00_Setup/02_Validation_layers.md b/03_Drawing_a_triangle/00_Setup/02_Validation_layers.md
@@ -335,11 +335,6 @@ window. You'll see that the following message is printed to the command prompt:
 
 ![](/images/validation_layer_test.png)
 
-*If this message is not printed when the program exits, then there may be a
-problem with your Vulkan SDK installation. See [this page](https://vulkan.lunarg.com/doc/sdk/1.0.61.0/windows/getting_started.html) for more information. You can prevent the command prompt from
-immediately closing in Visual Studio by running your program with Ctrl-F5 instead
-of just F5.*
-
 Oops, it has already spotted a bug in our program! The
 `VkDebugReportCallbackEXT` object needs to be cleaned up with a call to
 `vkDestroyDebugReportCallbackEXT`. Similarly to `vkCreateDebugReportCallbackEXT`
diff --git a/99_FAQ.md b/99_FAQ.md
@@ -0,0 +1,14 @@
+This page lists solutions to common problems that you may encounter while
+developing Vulkan applications.
+
+* **I get an access violation error in the core validation layer**: Make sure
+that the RivaTuner Statistics Server is not running, because it has some
+compatibility problems with Vulkan.
+
+* **I don't see any messages from the validation layers**: First make sure that
+the validation layers get a chance to print errors by keeping the terminal open
+after your program exits. You can do this from Visual Studio by running your
+program with Ctrl-F5 instead of F5, and on Linux by executing your program from
+a terminal window. If there are still no messages and you are sure that
+validation layers are turned on, then you should ensure that your Vulkan SDK is
+correctly installed by following [these instructions](https://vulkan.lunarg.com/doc/sdk/1.0.61.0/windows/getting_started.html).
