Скачать или смотреть C++ programming: live development of vulkan engine. READ THE DESCRIPTION. Switch to HD if needed.

Todo: Although textures now work, including descriptor arrays, internally, the API of the engine still behaves as if each descriptor refers to a single image. I need to change the API to be able to specify an array element that the texture is supposed to use (if the descriptor is an array) and I need to be able to work with whole arrays of textures at once when updating a descriptor, as opposed to just a single texture.

Todo: Textures (images) are "uploaded" to the GPU now - but what does that mean? What represents the CPU-side thing(s) that allows me to use a texture? And how can I free the resources on the GPU again when I don't need the texture anymore?

Todo: Properly fix uploading vertex buffers so that that is only done once.

FAQ
Q: What is a vulkan engine?
A: a graphics program that use the Vulkan API (a library+driver that talks directly to the GPU). An engine is a bunch of functions that do complex tasks so that you can use vulkan with a simpler syntax.
Q: How long have you been coding?
A: I started at 12 on a TRS-80 in a shop where they sold those. Later my dad bought a D.A.I. (2 Mhz clk, 48 kB ram) on which I taught myself to code in GFA-basic and assembly and little C (although that usually crashed the whole OS). I started to code seriously in C once CPUs had 'proctected mode' that allows safe multi-tasking at the age of 25. I only started with C++ when I left university at the age of 30. I am now 58 - so that means I've been coding C++ for 28 years (full time).

Music (if any) was downloaded from https://tunetank.com

Note: Each Todo is followed by the Todo that I was working on. The higher Todo's need to be finished before I can continue with a lower Todo.

The source code of this project is Free Open Source (GPL3). The git repository can be found here: https://github.com/CarloWood/linuxviewer