nice. at least loading such texture won't be a real concern in most hardware, then.
I have an integrated graphics board, Intel HD Graphics 620. the maximum texture size is exactly 16384.
interestingly, if I cut textures sizes by half, the problem still persists (big_tex: 8192, 8192; small_tex: 2048, 2048):
big_tex loading time: 3089ms
small_tex[0] loading time: 41ms
small_tex[1] loading time: 13ms
small_tex[2] loading time: 27ms
small_tex[3] loading time: 13ms
small_tex[4] loading time: 10ms
small_tex[5] loading time: 12ms
small_tex[6] loading time: 10ms
small_tex[7] loading time: 11ms
small_tex[8] loading time: 12ms
small_tex[9] loading time: 12ms
small_tex[10] loading time: 12ms
small_tex[11] loading time: 12ms
small_tex[12] loading time: 11ms
small_tex[13] loading time: 11ms
small_tex[14] loading time: 12ms
small_tex[15] loading time: 42ms
total small_tex loading time: 268ms
but if I cut it down by half again, the values get very close (big_tex: 4096, 4096; small_tex: 1024, 1024):
big_tex loading time: 58ms
small_tex[0] loading time: 15ms
small_tex[1] loading time: 3ms
small_tex[2] loading time: 3ms
small_tex[3] loading time: 3ms
small_tex[4] loading time: 3ms
small_tex[5] loading time: 3ms
small_tex[6] loading time: 3ms
small_tex[7] loading time: 2ms
small_tex[8] loading time: 3ms
small_tex[9] loading time: 3ms
small_tex[10] loading time: 3ms
small_tex[11] loading time: 3ms
small_tex[12] loading time: 3ms
small_tex[13] loading time: 2ms
small_tex[14] loading time: 2ms
small_tex[15] loading time: 2ms
total small_tex loading time: 63ms
would you guys mind testing with your respective Texture::getMaximumSize()?
although its not a bug, preliminarly findings suggest that using the max and 2nd max texture sizes (considering powers of two) may be too unpractical