15.08.2009, 15:43
Now to the crux of your question. Can you use a button file published by another site?
The answer although long winded will not only explain why using different published button files not generated at the AAA will not be compatible as well as answer questions others might have.
Negative issues if anyone uses incompatible button files would be mission sounds (not good), missing engines (really not good) and missing aircraft flight models (really really not good).
Basically it won't be pretty. You might get lucky is say you fly one certain aircraft and ignore the others.
But lets say you do install a button files created offsite. Those buttons in about 30 days will be totally obsolete because, as of this writing, the button files for 1.2 contain new aircraft of which I have retained when I loaned out the new fileslist. Furthermore, new aircraft and their associated engine sub variants are being added for version 1.3 that are not in the button files for 1.2.
For instance in 1.2 we have managed to expand on avaiable sounds as depicted here:
viewtopic.php?p=226990#226990
So in short, the button files that contain the flight models and engine management and their specified engine sounds in 1.2 will NOT be compatible with anyone else.
Some publishers might emphatically say they are 100% compatible and you, the user could try it. You could get lucky with a button swap, but you would never know if you got the whole aircraft list and it's associated elements unless you either have a 60% crash or one day you spawn and explode.
Now, why the incongruency one might ask? Simple, we at AAA do not change the default flight models for any reason whatsoever and we test as we are testing now to ensure compatibility with the previous unified installer.
To expand, at the AAA do not change the default even for operable canopies. Why? The reason is simple.
If you allow open canopies on existing or modded models of which others do not have, those that have the operable canopies will emit smoke as if one is flying on full rich. While this may not affect the off line crowd it does affect the on line crowd. If padlock is not sufficient, a nice smoke trail will definitely arouse the opposition of your whereabouts if they do not have the sliding canopy for a model you are flying.
So our stance is and has been equal footing for everyone, offline and online.
So where does this leave all of us. Well there are steps being taken by many in the community to unify the button files of which we at the AAA have been invited to participate. The initial goal is the unification of the button files so we don't have any incongruity in our installations.
I answered your question.
Respectfully
The answer although long winded will not only explain why using different published button files not generated at the AAA will not be compatible as well as answer questions others might have.
Negative issues if anyone uses incompatible button files would be mission sounds (not good), missing engines (really not good) and missing aircraft flight models (really really not good).
Basically it won't be pretty. You might get lucky is say you fly one certain aircraft and ignore the others.
But lets say you do install a button files created offsite. Those buttons in about 30 days will be totally obsolete because, as of this writing, the button files for 1.2 contain new aircraft of which I have retained when I loaned out the new fileslist. Furthermore, new aircraft and their associated engine sub variants are being added for version 1.3 that are not in the button files for 1.2.
For instance in 1.2 we have managed to expand on avaiable sounds as depicted here:
viewtopic.php?p=226990#226990
So in short, the button files that contain the flight models and engine management and their specified engine sounds in 1.2 will NOT be compatible with anyone else.
Some publishers might emphatically say they are 100% compatible and you, the user could try it. You could get lucky with a button swap, but you would never know if you got the whole aircraft list and it's associated elements unless you either have a 60% crash or one day you spawn and explode.
Now, why the incongruency one might ask? Simple, we at AAA do not change the default flight models for any reason whatsoever and we test as we are testing now to ensure compatibility with the previous unified installer.
To expand, at the AAA do not change the default even for operable canopies. Why? The reason is simple.
If you allow open canopies on existing or modded models of which others do not have, those that have the operable canopies will emit smoke as if one is flying on full rich. While this may not affect the off line crowd it does affect the on line crowd. If padlock is not sufficient, a nice smoke trail will definitely arouse the opposition of your whereabouts if they do not have the sliding canopy for a model you are flying.
So our stance is and has been equal footing for everyone, offline and online.
So where does this leave all of us. Well there are steps being taken by many in the community to unify the button files of which we at the AAA have been invited to participate. The initial goal is the unification of the button files so we don't have any incongruity in our installations.
I answered your question.
Respectfully