I found that with 16 gig of memory more than 2 concurrent GeoConvert instances are thrashing away in the page file.
So I doubt more than 2 instances are actually gaining any performance benefit over dual instances run sequentially.
Eight concurrent instances eventually cause a pagefile crash.
Hopefully v1.0 of AeroScenery will have some configuration for MaxConcurrentGeoConvert instances.
/Stu
Yup. And if you do max out your memory, you will get MUCH better performance from geoconvert if your OS installation is on a fast SSD (preferably two two of them striped in raid) instead of an old spinning HDD because of that page file utilization.