Weird drawing behavior with G4onG5 with Vulkan backend about kinc HOT 1 OPEN

It happens here too (amd + windows).

It looks like you have to put these uniform constants in the for loop to make it work as intended:

kinc_g4_set_matrix4(mvp_loc, &mvp_mat);
kinc_g4_set_matrix4(v_loc, &v_mat);
kinc_g4_set_floats(lightPos_loc, (float*)&light_pos, 3);

The constants are written to a vertexConstantBuffer and fragmentConstantBuffer.

Each call to kinc_g4_draw_indexed_vertices on G4onG5 uses a offset (constantBufferIndex*constantBufferSize) from these buffers and they are then linked with a g5 command.

The command list is then executed every 100 draw calls, on a vertex_buffer change, kinc_g4_start() or on kinc_g4_end().

So at the moment your 1st instance uses all constants and the rest are only using off_loc and rot_loc.
1st cube:

2nd cube:

Edit:
The cubes eventually appear because each frame the mvp and v uniform constants are set on a different offset location
1st cube now has offset 344064:

from kinc.