Incorrect image buffer data

[hexuallyactive]

There's a difference between Image.GetImageContent() between gltf and glb. When loading a glb, the entire buffer is returned

[vpenades]

GetImageContent() returns an ArraySegment<Byte>

ArraySegment<Byte> usually represents a slice over a larger Byte[] array. If you inspect its properties you'll find:

• .Array: The source array (which might be larger than the segment.
• .Offset: the first byte of the segment within '.Array'
• .Count: the number of bytes of the segment.

When you load a glTF, images are loaded separately, so in general, ArraySegment is a segment that covers the entire underlaying image array, so the .Offset will be zero, and .Count will be the size of the array.

But when loading a GLB, the images are contained in the large binary array of the GLB, so you must take into account .Offset and .Count to get the segment of the array that is the image. This has the advantage that avoids making a very slow copy of the data.

An example of accessing the ArraySegment would be this:

ArraySegment<Byte> segment = new ...;
for( int i = segment.Offset; i < segment.Count; ++i )
{
    Byte value = segment.Array[ segment.Offset + i];
}

You could see Arrays as glTF buffers, and ArraySegments as glTF BufferViews, understanding how ArraySegments work is crucial because SharpGLTF uses them extensively to acccess buffer segments very fast.

But if you're in a hurry, you can use LinQ and just do: ArraySegment<Byte>.ToArray() or even GetImageContent().ToArray() which will create a defensive copy of the segment and return the exact array you need.

[hexuallyactive]

Ah, I see - makes sense now - thank you!