thanks for your reply, ye I notice this now haha, I feel silly. On my first version of the texture class I wrote I had bzeroed the memory assuming something like this might happen but being as it worked flawlessly with so many textures upon loading I did not think twice about doing this in this class rewrite as it was working just fine when tested upon launch. I suppose the problem doesn't present itself at launch since the memory is pretty much cleared at that moment.
|