Difference between revisions of "Vulkan Renderer Development"
From CEGUI Wiki - Crazy Eddie's GUI System (Open Source)
Xxarthurxx (Talk | contribs) (→State of development) |
(→Improving CEGUI with the Vulkan Renderer) |
||
| 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. | * 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. | ||
| − | === | + | === 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 | + | * 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? | * 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? | ||
Revision as of 21:10, 20 June 2016
Contents
Purpose of this document
- Provide relevant links to Vulkan documentation, Vulkan tutorials, Vulkan code snippets that we will use during development
- Make a list of specific points we need to take into account when developing the Vulkan renderer for CEGUI:
- What are the problems/restrictions we need to consider? What should we keep in mind?
- How can we maximize Vulkan performance?
- What are the restrictions? How could we get around them?
- Keep track of the state of the development
References
Links
- Intel Vulkan Tutorial: https://software.intel.com/en-us/articles/api-without-secrets-introduction-to-vulkan-part-1
Books
- 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
General considerations
- As of now, CEGUI does not support any kind of internal threading.
- If we have separate command buffers for CEGUI and the rest of what the user's application uses, we can ensure that the states won't interfere with those of the regular rendering. (See enableExtraAttribs for more info..). This is a great advantage over OpenGL.
- 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.
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.
- 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?
ToDo
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
- Vulkan registry: https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml
Xxarthurxx (talk) 15:49, 20 June 2016 (UTC)
