Oh wow.
You mean to tell me that when I pass a pointer into setRamMipMapPointerFromInt() it sits there for a random amount of time before assigning that pointer to the texture, during which the old pointer (passed during the previous call to setRamMipMapPointerFromInt) is still assigned to the texture.
You’re right, that’s totally what’s happening.
If I push 0xff0000 into the original pointer after calling setRamMipMapPointerFromInt on a different value I totally get red flashes.
Daaamn…
That’s not very intuitive behaviour.
Still, thanks for your help. Looks like I’ll be using setRamImage after all~ [/i][/b]