Oh, really, you’re right! This is weird because I use the default .fp
from the built-in sprite. (Maybe it was the tint multiplication or the varying vec3 position… EDIT: Yeah, it was the tint multiplication to the Texture2D() function…)
I never thought this was the problem, but it seems it is.
Thanks for your help, I was pulling my hair out… 