Klowner , vor 13 Tagen

@fasterthanlime unexpected ursined integers?

fabs , vor 13 Tagen

@fasterthanlime I would take this kind of error in my stride.

lutzky , vor 13 Tagen

@fasterthanlime it makes for a thoroughly disappointing stereogram though

jaymcor , vor 13 Tagen

@fasterthanlime If your width calculation was 25% high or low, which is actually pretty similar to interpreting RGB as RGBA or vice verse, that could also produce a 4-plex of bear, with each horizontal row shifted successively by 25% of the expected image width. One way this could happen is swapping hsize and vsize on a 5:4 aspect ratio picture, though it would not account for the junk at the bottom. From a distance it would also feel like a consistent 25% alpha bear, but not variable alpha.

nicknicknicknick , vor 13 Tagen

@fasterthanlime
not enough bears

patriksvensson , vor 13 Tagen

@fasterthanlime Hmmm image stride mismatch?

typeswitch , vor 13 Tagen

@fasterthanlime activated magic eye mode by accident /j

bnjbvr , vor 13 Tagen

@fasterthanlime raised cool bear anger levels up to 5?

itamarst , vor 13 Tagen

@fasterthanlime Working with bear pointers in C++

groxx , vor 13 Tagen

@fasterthanlime delving into audio steganography? is this code for "bear with me"?

Wortex17 , vor 13 Tagen

@fasterthanlime Talking outta my late-night-but here, but wrap-x and clamp-y and then swapped your x&y read dimensions / aspect ratio?

thibault , vor 13 Tagen

@fasterthanlime Forgot the image was RGB and treated it as greyscale (or the other way around)?

18+ fasterthanlime OP , vor 13 Tagen

@thibault image was RGB8, told some code to interpret it as RGBA8!

18+ thibault , vor 13 Tagen

@fasterthanlime classic mistake. One I still always make of course, but classic nonetheless