Where "big" in this context refers purely to download and installation size, rather than awsomeness, which doesn't require a poll.
As you will have realised by now, the next version will provide a significant jump in supported texture resolution, plus elevation support, which in turn comes at the cost of larger downloads and disk space requirements. The latest Earth textures alone at full resolution currently stand at about 64GB disk space, delivered in 24GB compressed download packages, but I am not even pushing the Landsat textures to the limit. I could probably go two resolution levels higher, i.e. make everything 16 times bigger. And this is before considering local high-resolution aerial imagery.
So maybe it's a good time to ask the question: how big an Orbiter installation size would you tolerate to inhabit your harddrive?
As you will have realised by now, the next version will provide a significant jump in supported texture resolution, plus elevation support, which in turn comes at the cost of larger downloads and disk space requirements. The latest Earth textures alone at full resolution currently stand at about 64GB disk space, delivered in 24GB compressed download packages, but I am not even pushing the Landsat textures to the limit. I could probably go two resolution levels higher, i.e. make everything 16 times bigger. And this is before considering local high-resolution aerial imagery.
So maybe it's a good time to ask the question: how big an Orbiter installation size would you tolerate to inhabit your harddrive?