Good Morning All,
What I would like to do is gather all known information and initiate a general discussion on the following topic:
Is it possible to manipulate the FSX multiplayer aircraft substitution system?
Having done no precursory research on the topic, I envision a tool/file-system that will replicate the basic elements of an aircraft not in your hanger when another player flies it. To this end, I ask the following sub-questions:
1) What file(s) is(are) absolutely necessary to properly display an aircraft not flown by yourself (AI or another player) in-game?
2) What must match in order to trigger a same-aircraft match and avoid a substitution altogether?
3) What might be the easiest way to document/warehouse all of the required files (see 1 above) and requirements (see 2 above) for all FSX add-on aircraft?
4) What potential is there for copyright infringement when undertaking such a task as warehousing all of this data and files into a package deliverable and install-able for the entire FSX multiplayer community?
Also, if this has been done or attempted already, I'd love to know what was learned in so doing.
Thanks in advance for your thoughts.
What I would like to do is gather all known information and initiate a general discussion on the following topic:
Is it possible to manipulate the FSX multiplayer aircraft substitution system?
Having done no precursory research on the topic, I envision a tool/file-system that will replicate the basic elements of an aircraft not in your hanger when another player flies it. To this end, I ask the following sub-questions:
1) What file(s) is(are) absolutely necessary to properly display an aircraft not flown by yourself (AI or another player) in-game?
* I imagine a model is required, but without textures or effects, will FSX consider it the same aircraft?
2) What must match in order to trigger a same-aircraft match and avoid a substitution altogether?
* As far as I know, even a modest change to an aircraft's configuration could mistakenly result in a substitution scenario, even if another player has the same base/original aircraft that you had prior to said modest change.
3) What might be the easiest way to document/warehouse all of the required files (see 1 above) and requirements (see 2 above) for all FSX add-on aircraft?
* I understand that this is a daunting endeavor... just asking for ideas here.
4) What potential is there for copyright infringement when undertaking such a task as warehousing all of this data and files into a package deliverable and install-able for the entire FSX multiplayer community?
Also, if this has been done or attempted already, I'd love to know what was learned in so doing.
Thanks in advance for your thoughts.
Comment