I have been playing with AeroScenery and thinking about "production mode" use.
The issue arises in tiling out high resolution areas of interest.
I am building soaring scenery with level 9-12 scenery in the general area and level 13-14/15 for significant valley floors and walls. The geoconvert integration challenges make a single pass approach unworkable. Selecting a dozen tiles for an all Actions pass overnight always fails at the geoconvert stage as 12 concurrent geoconvert jobs crash the pagefile (and in reality with 16G more than two concurrent geoconvert are just thrashing away at each other anyway). Imposing a limit on concurrent geoconvert jobs stalls on the lack of a geoconvert completion event.
Based on this issue I have been doing download only "batch" jobs overnight and then geoconvert individual tiles the next day. It is not possible to tell from the map view which tiles have been converted and which are download only.
So it would be nice to have additional tile states such as "Converted" and "Installed" to make it easier to manage an incremental build process from the map view.
When the geoconvert integration can be tightened the batch production scenario will be less of an problem, but the same issue arises if you want to do an intermediate inspection and color correction before geoconvert.
It is possible to "schedule" AeroScenery for the wee hours (when bandwidth is free) using the pssuspend command from the MS pstools pack.
After selecting tiles and starting the download, the AeroScenery process can be suspended.
A batch job at the designated hour resumes the process without any apparent problems.