gnosticoccultist / mercury-engine Goto Github PK

Capabilities and limitations of a current rendering context should be the same no matter what graphics API it is using (OpenGL, OpenGL ES, Vulkan, etc).
These data should be passed through each object (Texture, Shaders, VertexBuffers, etc), to create them appropriately based on capabilities and limitations.

When applying a non-identity model matrix to an AnimaMundi, every model of the hierarchy are distorted.

Specs :

• https://github.com/KhronosGroup/3D-Formats-Guidelines/blob/main/KTXDeveloperGuide.md
• https://registry.khronos.org/KTX/specs/2.0/ktxspec.v2.html

When resizing the screen framebuffer, if depth buffer is masked and depth testing is enabled, the rasterizer ignores every pixels. Maybe we need to automatically disable depth testing and enabling depth writing before clearing the depth buffer, to prevent said issue...

Use stride and offset parameters to interleave the vertex data into a single VBO, avoiding VBOs binding/unbinding. This way, a unique VBO will contain positions, texcoords, normals, indices and other type of data.

AssetManager should support async loading of assets and uploading it synchronously on the main thread.