bigwheels
bigwheels copied to clipboard
google
BigWheels is a cross-platform, API agnostic framework to build graphics applications.
The third of a series of CL that integrates the commits from: https://github.com/bjoeris/bigwheels/tree/experimental-foveation into BW main's branch. The series will have 4 CL, this is the third one that integrates...
I find code coverage metrics useful to identify missing tests. I only provided GCC instructions since that's the toolchain that I'm used to working with.
Adds multiview into Cube_XR. This is a followup to pr#419 where multiview was added to the repo.
Unlike `AppendIndex` and friends, `AppendIndicesU32` doesn't account for `INDEX_TYPE_UNDEFINED`. Consider: ```c++ Geometry geometry; Geometry::Create(GeometryCreateInfo{}.IndexType(grfx::INDEX_TYPE_UNDEFINED).AddPosition(), &geometry); std::array data = {0, 1, 2) geometry.AppendIndicesU32(data.size(), data.data()); EXPECT_EQ(geometry.GetIndexBuffer()->GetSize(), 0); ``` This test would fail...
`GltfLoader::LoadMeshData` currently complains when a mesh lacks `indices`. However, meshes are allowed to not have `indices`. [5.24.2](https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#_mesh_primitive_indices) says: > When this is undefined, the primitive defines non-indexed geometry This would...
`GltfLoader::LoadMeshData` will provide (0,0,0) for normals if not present. However [3.7.2.1](https://github.com/KhronosGroup/glTF-Sample-Assets/tree/main/Models/SimpleMaterial) says: > When normals are not specified, client implementations MUST calculate flat normals and the provided tangents (if present)...
Without extensions, Vulkan only supports UINT16 and UINT32 index buffers. However, glTF allows UINT8 index buffers. We can support scenes with UINT8 indices by repacking them into a UINT16 buffer...
I was running BigWheels on pixel 6 (which I haven't done in a while) and it failed with feature not present. I couldn't immediately see which feature was not present....
Also, create format definitions for YUV images.
All models loaded with `scene::GltfLoader` are assumed to be single-sided (back face culling is enabled). glTF supports double-sided materials. From [3.9.5](https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#double-sided): > When this value is true, back-face culling is...