Adrian Blumer

I recently did a similar evaluation, but rather approaching this from the memory consumption side instead of the performance perspective. My findings also point in the direction of using normal...

Small update to the above, a class with x, y & z fields uses ~56 bytes, which also matches with other sources: - 24 bytes object overhead, see https://www.mattzeunert.com/2017/03/29/v8-object-size.html -...

@krisnye Yes of course, that's how we mainly use them in our code base. Unfortunately they tend to lead to less idiomatic and maintainable code, so I started to investigate...

Yes, I saw your other PR on that topic and at some point was also experimenting with changes to the encoding there, but then figured to keep the two separate....

No need to rush from my side :) And don't get me wrong, even though that might not be obvious from my last couple comments here, coming from 3D rendering,...

PS: I'm also wondering if we should treat "image textures" and "font/shape atlas textures" separately. Image textures contain colors, with all the headache that entails. The atlas textures (which could...

@DGriffin91 Thanks for taking the time to look into this. I'm far from an expert on Vulkan tbh, but I'm happy to provide some context based on my understanding: The...

As for testing instructions: - Get the VulkanSDK for MacOS from the download page linked in [this article](https://vulkan.lunarg.com/doc/sdk/1.4.313.0/mac/getting_started.html), and while at it give at least the first part of the...

Glad to hear! For reference, I've been testing a similar setup as your second one: MacBook Pro 2023 M3 Max (Sequoia 15.5), Vulkan SDK 1.4.309.0 Btw, I'm curious about your...