Fix parts of the tutorial that weren't update to match the code (fixes #288)

Author: Overv

en/04_Vertex_buffers/03_Index_buffer.md

@@ -120,16 +120,16 @@ void cleanup() {
 ## Using an index buffer
 
 Using an index buffer for drawing involves two changes to
-`createCommandBuffers`. We first need to bind the index buffer, just like we did
+`recordCommandBuffer`. We first need to bind the index buffer, just like we did
 for the vertex buffer. The difference is that you can only have a single index
 buffer. It's unfortunately not possible to use different indices for each vertex
 attribute, so we do still have to completely duplicate vertex data even if just
 one attribute varies.
 
 ```c++
-vkCmdBindVertexBuffers(commandBuffers[i], 0, 1, vertexBuffers, offsets);
+vkCmdBindVertexBuffers(commandBuffer, 0, 1, vertexBuffers, offsets);
 
-vkCmdBindIndexBuffer(commandBuffers[i], indexBuffer, 0, VK_INDEX_TYPE_UINT16);
+vkCmdBindIndexBuffer(commandBuffer, indexBuffer, 0, VK_INDEX_TYPE_UINT16);
 ```
 
 An index buffer is bound with `vkCmdBindIndexBuffer` which has the index buffer,
@@ -142,7 +142,7 @@ the drawing command to tell Vulkan to use the index buffer. Remove the
 `vkCmdDraw` line and replace it with `vkCmdDrawIndexed`:
 
 ```c++
-vkCmdDrawIndexed(commandBuffers[i], static_cast<uint32_t>(indices.size()), 1, 0, 0, 0);
+vkCmdDrawIndexed(commandBuffer, static_cast<uint32_t>(indices.size()), 1, 0, 0, 0);
 ```
 
 A call to this function is very similar to `vkCmdDraw`. The first two parameters

en/05_Uniform_buffers/01_Descriptor_pool_and_sets.md

@@ -106,7 +106,7 @@ allocInfo.descriptorSetCount = static_cast<uint32_t>(MAX_FRAMES_IN_FLIGHT);
 allocInfo.pSetLayouts = layouts.data();
 ```
 
-In our case we will create one descriptor set for each frame in flight, all with the same layout. 
+In our case we will create one descriptor set for each frame in flight, all with the same layout.
 Unfortunately we do need all the copies of the layout because the next function expects an array matching the number of sets.
 
 Add a class member to hold the descriptor set handles and allocate them with
@@ -133,7 +133,7 @@ buffer descriptor.
 void cleanup() {
     ...
     vkDestroyDescriptorPool(device, descriptorPool, nullptr);
-    
+
     vkDestroyDescriptorSetLayout(device, descriptorSetLayout, nullptr);
     ...
 }
@@ -212,12 +212,12 @@ as its name implies.
 
 ## Using descriptor sets
 
-We now need to update the `createCommandBuffers` function to actually bind the
+We now need to update the `recordCommandBuffer` function to actually bind the
 right descriptor set for each frame to the descriptors in the shader with `vkCmdBindDescriptorSets`. This needs to be done before the `vkCmdDrawIndexed` call:
 
 ```c++
-vkCmdBindDescriptorSets(commandBuffers[i], VK_PIPELINE_BIND_POINT_GRAPHICS, pipelineLayout, 0, 1, &descriptorSets[i], 0, nullptr);
-vkCmdDrawIndexed(commandBuffers[i], static_cast<uint32_t>(indices.size()), 1, 0, 0, 0);
+vkCmdBindDescriptorSets(commandBuffer, VK_PIPELINE_BIND_POINT_GRAPHICS, pipelineLayout, 0, 1, &descriptorSets[currentFrame], 0, nullptr);
+vkCmdDrawIndexed(commandBuffer, static_cast<uint32_t>(indices.size()), 1, 0, 0, 0);
 ```
 
 Unlike vertex and index buffers, descriptor sets are not unique to graphics

en/07_Depth_buffering.md

@@ -577,10 +577,6 @@ void recreateSwapChain() {
     createGraphicsPipeline();
     createDepthResources();
     createFramebuffers();
-    createUniformBuffers();
-    createDescriptorPool();
-    createDescriptorSets();
-    createCommandBuffers();
 }
 ```
 

en/08_Loading_models.md

@@ -96,7 +96,7 @@ there are going to be a lot more vertices than 65535. Remember to also change
 the `vkCmdBindIndexBuffer` parameter:
 
 ```c++
-vkCmdBindIndexBuffer(commandBuffers[i], indexBuffer, 0, VK_INDEX_TYPE_UINT32);
+vkCmdBindIndexBuffer(commandBuffer, indexBuffer, 0, VK_INDEX_TYPE_UINT32);
 ```
 
 The tinyobjloader library is included in the same way as STB libraries. Include