Vulkan Renderer Development - Revision history

Xxarthurxx: /* Links */

2016-06-22T14:22:37Z

‎Links

2016-06-20T22:05:00Z

‎State of development

2016-06-20T22:04:42Z

‎References

2016-06-20T22:01:14Z

‎Links

2016-06-20T21:47:35Z

2016-06-20T21:10:08Z

‎Improving CEGUI with the Vulkan Renderer

2016-06-20T15:49:35Z

‎State of development

2016-06-20T15:43:36Z

‎Books

2016-06-20T15:42:59Z

‎Links

2016-06-20T15:42:48Z

‎Books

@@ Line 14: / Line 14: @@
 * Set of demos: https://github.com/SaschaWillems/Vulkan
 * Good old triangle demo: https://github.com/SaschaWillems/Vulkan/blob/master/triangle/triangle.cpp
 ===Books===

@@ Line 34: / Line 34: @@
 == State of development ==
 Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:
+* Repo link: https://github.com/nvpro-pipeline/vkcpp
-	- Repo link: https://github.com/nvpro-pipeline/vkcpp
+* Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml
-−
-	- Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml

@@ Line 10: / Line 10: @@
 ===Links===
-*Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1
+* Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1
-*QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf
+* QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf
 ===Books===
-*Vulkan Programming Guide by  John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540
+* Not yet released, not sure if worth it: Vulkan Programming Guide by John M. Kessenich and Graham Sellers: https://www.amazon.co.uk/Vulkan-Programming-Guide-Official-Learning/dp/0134464540
 == CEGUI Vulkan Renderer : Thoughts ==

← Older revision		Revision as of 22:01, 20 June 2016
Line 11:		Line 11:

	*Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1		*Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1
		+	*QuickRef: https://www.khronos.org/registry/vulkan/specs/1.0/refguide/Vulkan-1.0-web.pdf

	===Books===		===Books===

← Older revision		Revision as of 21:47, 20 June 2016
Line 35:		Line 35:

	- Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml		- Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml
−
−
−	~~----~~
−	~~[[User:Xxarthurxx\|Xxarthurxx]] ([[User talk:Xxarthurxx\|talk]]) 15:49, 20 June 2016 (UTC)~~

@@ Line 23: / Line 23: @@
 * Would any sort of threading for CEGUI's logic and rendering provide an advantage? In the end, the rendering would always have to wait for the logic to be processed but they could be started at separate times.
-=== Improving CEGUI with the Vulkan Renderer ===
+=== Points to achieve optimal performance with the CEGUI Vulkan Renderer ===
-* Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch or if this even would have any benefits.
+* Considering that Vulkan as one of its main benefits features threading support, we want to research whether this would be worth it for CEGUI default branch.
 * As always, we need to keep batching low. Is there anything provided in Vulkan that allows us to batch things better? We used to make the VBOs as large as possible, which was a notable advantage even though we rendered the quads in separate draw calls. Can this be done better?

@@ Line 30: / Line 30: @@
 == State of development ==
-* We will use the Nvidia C++ Wrapper for Vulkan by creating the header file based on the Vulkan registry. This header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer.
+Nvidia C++ Wrapper for Vulkan will be used. This Wrapper contains of a single header file. For CEGUI this means, that the single header needs to be namespaced in CEGUI and will be bundled with the Vulkan Renderer. For further building informations, please look into the repository:
-** Repo: https://github.com/nvpro-pipeline/vkcpp
-** Vulkan registriy: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml
+	- Repo link: https://github.com/nvpro-pipeline/vkcpp