Releasing the scenery with JPGs saves about 40% of the bandwidth to download the package. Originally this seemed like a good idea, but packaging up the .DDS files, checking everything is there, and writing the script batch file isn’t too much fun. I also think people who download the package don’t love needing to run dozens of scripts to convert the JPGs to DDS files to get it going. I get emails from people who have a corrupted file or missing images. I also had to patch the first beta because a bunch of images went missing in transit.
The batch file is a windows thing, so Mac and Linux users aren’t well supported. (And I’m writing this on a Mac!)
So if I were to package up the scenery tiles with DDS they’d be rather large, but it would basically be a drop and go solution. Because it’s large, I might split the packages up into 5 or 10 sections. If each section is 30GB and there are 10 of them, people could just get what they need up front and add the rest over time.
What do you think? Keep the scripts, or make it easy?
Categories: Flight Simulation