Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d49b1eb

Browse files
SaschaWillemsSaschaWillems
committed
Updating 1.2 to 1.3 spec links
1 parent 0b7627b commit d49b1eb

9 files changed

Lines changed: 10 additions & 10 deletions

File tree

‎config.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919
"links": {
2020
"GitHub Repository": "https://github.com/Overv/VulkanTutorial",
2121
"Support the website": "https://www.paypal.me/AOvervoorde",
22-
"Vulkan Specification": "https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/",
22+
"Vulkan Specification": "https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/",
2323
"LunarG Vulkan SDK": "https://lunarg.com/vulkan-sdk/",
2424
"Vulkan Guide": "https://github.com/KhronosGroup/Vulkan-Guide",
2525
"Vulkan Hardware Database": "https://vulkan.gpuinfo.org/",

‎en/03_Drawing_a_triangle/00_Setup/02_Validation_layers.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ Similarly the `messageType` field lets you filter which types of messages your c
298298

299299
Finally, the `pfnUserCallback` field specifies the pointer to the callback function. You can optionally pass a pointer to the `pUserData` field which will be passed along to the callback function via the `pUserData` parameter. You could use this to pass a pointer to the `HelloTriangleApplication` class, for example.
300300

301-
Note that there are many more ways to configure validation layer messages and debug callbacks, but this is a good setup to get started with for this tutorial. See the [extension specification](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap50.html#VK_EXT_debug_utils) for more info about the possibilities.
301+
Note that there are many more ways to configure validation layer messages and debug callbacks, but this is a good setup to get started with for this tutorial. See the [extension specification](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap50.html#VK_EXT_debug_utils) for more info about the possibilities.
302302

303303
This struct should be passed to the `vkCreateDebugUtilsMessengerEXT` function to
304304
create the `VkDebugUtilsMessengerEXT` object. Unfortunately, because this

‎en/03_Drawing_a_triangle/00_Setup/04_Logical_device_and_queues.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ there are Vulkan devices in the system that lack this ability, for example
100100
because they only support compute operations. We will come back to this
101101
extension in the swap chain chapter.
102102

103-
Previous implementations of Vulkan made a distinction between instance and device specific validation layers, but this is [no longer the case](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap40.html#extendingvulkan-layers-devicelayerdeprecation). That means that the `enabledLayerCount` and `ppEnabledLayerNames` fields of `VkDeviceCreateInfo` are ignored by up-to-date implementations. However, it is still a good idea to set them anyway to be compatible with older implementations:
103+
Previous implementations of Vulkan made a distinction between instance and device specific validation layers, but this is [no longer the case](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap40.html#extendingvulkan-layers-devicelayerdeprecation). That means that the `enabledLayerCount` and `ppEnabledLayerNames` fields of `VkDeviceCreateInfo` are ignored by up-to-date implementations. However, it is still a good idea to set them anyway to be compatible with older implementations:
104104

105105
```c++
106106
createInfo.enabledExtensionCount = 0;

‎en/03_Drawing_a_triangle/02_Graphics_pipeline_basics/04_Conclusion.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ And finally we have the reference to the render pass and the index of the sub
5454
pass where this graphics pipeline will be used. It is also possible to use other
5555
render passes with this pipeline instead of this specific instance, but they
5656
have to be *compatible* with `renderPass`. The requirements for compatibility
57-
are described [here](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap8.html#renderpass-compatibility),
57+
are described [here](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap8.html#renderpass-compatibility),
5858
but we won't be using that feature in this tutorial.
5959

6060
```c++

‎en/04_Vertex_buffers/01_Vertex_buffer_creation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -290,7 +290,7 @@ matches the contents of the allocated memory. Do keep in mind that this may lead
290290
to slightly worse performance than explicit flushing, but we'll see why that
291291
doesn't matter in the next chapter.
292292

293-
Flushing memory ranges or using a coherent memory heap means that the driver will be aware of our writes to the buffer, but it doesn't mean that they are actually visible on the GPU yet. The transfer of data to the GPU is an operation that happens in the background and the specification simply [tells us](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap7.html#synchronization-submission-host-writes) that it is guaranteed to be complete as of the next call to `vkQueueSubmit`.
293+
Flushing memory ranges or using a coherent memory heap means that the driver will be aware of our writes to the buffer, but it doesn't mean that they are actually visible on the GPU yet. The transfer of data to the GPU is an operation that happens in the background and the specification simply [tells us](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap7.html#synchronization-submission-host-writes) that it is guaranteed to be complete as of the next call to `vkQueueSubmit`.
294294

295295
## Binding the vertex buffer
296296

‎fr/03_Dessiner_un_triangle/00_Mise_en_place/02_Validation_layers.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -294,7 +294,7 @@ fait partie des paramètres de la fonction de rappel.
294294

295295
Notez qu'il existe de nombreuses autres manières de configurer des messagers auprès des validation layers, mais nous
296296
avons ici une bonne base pour ce tutoriel. Référez-vous à la
297-
[spécification de l'extension](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap50.html#VK_EXT_debug_utils)
297+
[spécification de l'extension](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap50.html#VK_EXT_debug_utils)
298298
pour plus d'informations sur ces possibilités.
299299

300300
Cette structure doit maintenant être passée à la fonction `vkCreateDebugUtilsMessengerEXT` afin de créer l'objet

‎fr/03_Dessiner_un_triangle/02_Pipeline_graphique_basique/04_Conclusion.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ pipelineInfo.layout = pipelineLayout;
4343
Finalement nous devons fournir les références à la render pass et aux indices des subpasses. Il est aussi possible
4444
d'utiliser d'autres render passes avec cette pipeline mais elles doivent être compatibles avec `renderPass`. La
4545
signification de compatible est donnée
46-
[ici](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap8.html#renderpass-compatibility), mais nous
46+
[ici](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap8.html#renderpass-compatibility), mais nous
4747
n'utiliserons pas cette possibilité dans ce tutoriel.
4848

4949
```c++

‎fr/05_Uniform_buffers/01_Descriptor_pool_et_sets.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@ Vulkan s'attend à un certain alignement des données en mémoire pour chaque ty
295295
* Une `mat4` doit avoir le même alignement qu'un `vec4`
296296

297297
Les alignemenents imposés peuvent être trouvés dans
298-
[la spécification](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap15.html#interfaces-resources-layout)
298+
[la spécification](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap15.html#interfaces-resources-layout)
299299

300300
Notre shader original et ses trois `mat4` était bien aligné. `model` a un décalage de 0, `view` de 64 et `proj` de 128,
301301
ce qui sont des multiples de 16.

‎fr/06_Texture_mapping/00_Images.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -480,7 +480,7 @@ indique une étape de la pipeline. Durant celle-ci seront réalisées les opéra
480480
paramètre d'après indique également une étape de la pipeline. Cette fois les opérations exécutées durant cette étape
481481
attendront la barrière. Les étapes que vous pouvez fournir comme avant- et après-barrière dépendent de l'utilisation
482482
des ressources qui y sont utilisées. Les valeurs autorisées sont listées
483-
[dans ce tableau](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap7.html#synchronization-access-types).
483+
[dans ce tableau](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap7.html#synchronization-access-types-supported).
484484
Par exemple, si vous voulez lire des données présentes dans un UBO après une barrière qui s'applique au buffer, vous
485485
devrez indiquer `VK_ACCESS_UNIFORM_READ_BIT` comme usage, et si le premier shader à utiliser l'uniform est le fragment
486486
shader il vous faudra indiquer `VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT` comme étape. Dans ce cas de figure, spécifier
@@ -625,7 +625,7 @@ pipeline de transfert. Mais cette opération d'écriture ne dépend d'aucune aut
625625
une condition d'accès nulle et `VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT` comme opération pré-barrière. Cette valeur correspond
626626
au début de la pipeline, mais ne représente pas vraiment une étape. Elle désigne plutôt le moment où la pipeline se
627627
prépare, et donc sert communément aux transferts. Voyez
628-
[la documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap7.html#synchronization-pipeline-stages)
628+
[la documentation](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap7.html#VkPipelineStageFlagBits)
629629
pour de plus amples informations sur les pseudo-étapes.
630630

631631
L'image sera écrite puis lue dans la même passe, c'est pourquoi nous devons indiquer que le fragment shader aura accès à

0 commit comments

Comments
 (0)