Post by Dutch Owen on Dec 13, 2012 10:13:08 GMT -5
FSCaptain depends on the aircraft configurations having accurate data to give good dispatch planning estimates. While a set of good configurations are included, many other airplanes exist out there and the thousands of pilots that have flown and are flying with FSCaptain have developed some good configurations that are staying on their PC. So new pilots have to re-invent some wheels.
Version 1.5 will contain a feature we call 'netconfig' but which would better be called Automatic Configuration Sharing. The idea being there's a central repository of verified good configurations on the FSCaptain server. Every time FSCaptain does a version check (about every three days if you use it every day) it could check to see if any new configurations are available for airplanes you have in your FS9/X that don't have configurations in FSCaptain\Aircraft. If any are found, install them into your system.
The first time this happens we'd put up a dialog explaining it and allowing you to opt out of the process, or defer the update till a later time. Also an option to opt out at any time.
It would work the other way too. If you have configurations for types that are not on the server we'd upload yours to a holding area, review them, and place them in the standard set for others to pick up automatically when they need them. You would have the option of disabling this part too, of course.
We'd never replace a configuration on your system with one from the standard set -- only add new ones you don't have.
Seeking ideas and thoughts about this before we start the coding (which will be very soon!)
Dutch
Version 1.5 will contain a feature we call 'netconfig' but which would better be called Automatic Configuration Sharing. The idea being there's a central repository of verified good configurations on the FSCaptain server. Every time FSCaptain does a version check (about every three days if you use it every day) it could check to see if any new configurations are available for airplanes you have in your FS9/X that don't have configurations in FSCaptain\Aircraft. If any are found, install them into your system.
The first time this happens we'd put up a dialog explaining it and allowing you to opt out of the process, or defer the update till a later time. Also an option to opt out at any time.
It would work the other way too. If you have configurations for types that are not on the server we'd upload yours to a holding area, review them, and place them in the standard set for others to pick up automatically when they need them. You would have the option of disabling this part too, of course.
We'd never replace a configuration on your system with one from the standard set -- only add new ones you don't have.
Seeking ideas and thoughts about this before we start the coding (which will be very soon!)
Dutch