Hi guys, just a quick update to let you all know that in addition to making "AI cockpit mods
" user definable I have also implemented a feature that allows the user to define any additional flyable aircraft to add into the Mission Mate mix.
This feature will allow the user to add any flyable aircraft of their choosing and has been primarily designed to accommodate new flyable aircraft that are not available with an auto installer or are in the beta stage of development. Of course this will also allow users to add flyable aircraft that have been officially released with an auto installer that I have not formally included for what ever reason.
This whole process is managed by two simple text files that Mission Mate looks for while loading. The first I have developed an interface for that will generate and manage the "AI cockpit mod
" aircraft listings, it is also this file that any additional aircraft listings may be manually added to by the user, this list is additional to the Mission Mate hard-coded aircraft list.
The second is an accompanying aircraft load-out text file for each aircraft. This load out file will be the master load out file, that is to say that it will have priority over the hard coded listings present. This file however is totally the responsibility of the user to create and maintain. Mission Mate will of course use a hard coded default load out if you are not sure about how to construct one of your own and it is found to be absent when you select that particular aircraft, so that your mission wont $hit itself because of the load out spec.
This whole process sounds very simple and some of you may be wondering why MM was not setup this way from the beginning. The reason was simply to keep user functionality as trouble free as possible and of course there really wasn't the need to have this flexibility in the past.
Ok it's back to getting the installation & setup ready.