Someone on the newsgroups was recently asking why loading his simple 800x600 texture was taking up so much memory (more than 5 megs). He was using code something like the following:
Texture myTexture = TextureLoader.FromFile(myDevice, somePath);
The quest seemed interesting enough for me to post my response here as well as in the newsgroup since this reinforces my belief that you should always know what the methods you're calling 'cost'. It wouldn't surprise me to find out that most people don't realize all the things that go in with that simple line above.
So here was my response:
PingBack from http://outdoorceilingfansite.info/story.php?id=5438
PingBack from http://outdoorceilingfansite.info/story.php?id=23074