16 hourspic.twitter.com/zbDUVUyO6r
My first #Vulkan triangle! 
Under 512 lines and 16 hours of work, though I cheated a bit and I'm saving a PNG instead of messing with the swapchain. I also hand-crafted the SPIR-V bytecode instead of compiling GLSL. Full thing with lots being hardcoded: https://gist.github.com/mosra/268defb3ffbb0f2cd78815394f27f8a3 …pic.twitter.com/R7AaQ4vISd
-
-
-
It could have been 12, but by accident I copied my vertex data into the framebuffer instead of the vertex buffer and spent the last four hours being extremely angry about things
- 10 weitere Antworten
Neue Unterhaltung -
-
-
That moment Vladimir realized, he could just code a ray-tracing renderer based engine by the time he drew an infamous VkTriangle. :P
-
I expected it much worse to be honest ;) I could also just try with some ready-made example code, but I wanted to go the hard way by reading directly the spec to get the full picture.
Ende der Unterhaltung
Neue Unterhaltung -
-
-
Handy tip: remove all linefeed's to reduce lines of code.
-
... but I guess the preprocessor requires each statement on a new line, right? Well then.pic.twitter.com/6acRw6o0gE
- 1 weitere Antwort
Neue Unterhaltung -
-
-
Nice :) I guess that wins the prive for 'least-lines-of-code to triangle' in Vulkan so far?
-
I could have cheated a bit more and load a pipeline cache instead of the verbose manual setup, saving some ~200 lines, but that would be maybe too far :) Frankly I think the specs could be relaxed a bit and allow sane zero-filled defaults on a bit more places.
- 1 weitere Antwort
Neue Unterhaltung -
Das Laden scheint etwas zu dauern.
Twitter ist möglicherweise überlastet oder hat einen vorübergehenden Schluckauf. Probiere es erneut oder besuche Twitter Status für weitere Informationen.