Wait, what? Are you saying they are going to use different textures every frame or something? And anyway, my point was that if you have 512 MB of vram you aren't going to replace it 4 times over every second.
It's possible to use new textures every 1/4 of a second.
That's it.
What are you talking about? You don't need to completely eliminate grabs from the HDD, you just need to make it so they don't slow the program down...
But it doesn't matter how'd you do it if you change only 30-50mb of data per second.
As for the hill test, I am talking about a scenario where the player can't run up it and the dev knows this. They can simply put a flag up there so that it doesn't start loading the textures up there.
You just do not draw it, that's all.
Or have only one side of it modelled.