BeRo's Blog
A blog about software development, digital music production and demoscene stuff
Menu
Projects
Projects
PasVulkan
My Android apps
KRAFT - a physics engine
PasMP - a parallel-processing library
BESEN - a ECMAScript engine
PUCU - a Unicode library
FLRE - a regular expression engine
PasDblStrUtils - for dbl<>str conversion
CrossPascal - A pascal->C transpiler
My demoscene productions
BeRoEXEPacker
Audio software
Audio software
Sobanth
BeRoTracker
CreamTracker
Picatune 2
BR808
BR404
Emulators
Emulators
micro64
hyper64
Games
Games
BMCP - a weak self-playing chess engine
BeRoFourConnect
BeRoChess
Slides
Slides
Supraleiter and its rendering technologies
How to use Voxel Cone Tracing with two bounces for everything instead of just Global Illumination
Links
Links
Main website
My german blog
GitHub
Play store developer site
SoundCloud
Youtube
Farbrausch
Privacy Policy
Privacy Policy
Datenschutzerklärung
Privacy Policy
The two different GUI rendering strategies at PasVulkan with the Vulkan API
Published on
Sat, 24 Mar 2018 04:22:56 UTC
in
PasVulkan
by
BeRo
-
Permalink
Admittedly, the Vulkan API calls could potentially be further optimized and merged.
Tags:
PasVulkan
Vulkan
→
By
BeRo
Share this post
Twitter
Facebook
Google+
Related posts
Vulkan memory management in PasVulkan
PasVulkan GLTF 2.0 support progress showcase with a sample with just one draw call per frame.
PasVulkan GLTF 2.0 support
▶ Comments
Please enable JavaScript to view the
comments powered by Disqus.
«
The Vulkan header generator and Vulkan header of PasVulkan is from this time point on also Vulkan 1.1 ready now
First working version of TpvGUIVulkanCanvas in the PasVulkan GUI subframework
»