):J'espere d'etre capable de poster quelque ingame screenshots en futur, ici sont quelque screenies du 3d models:1. Introduction to Project Phoenix
Project Phoenix emerged out of a concern in the Falcon 4.0 community that their favorite pastime, simulating combat aircraft operations, was threatened by a lack of suitable computer application programs. This concern reached its peak when Infogrames and G2I, which acquired the intellectual property rights to the Falcon4 program of Microprose, limited the community in their freedom to enhance the program. This had been common practice in the previous years, resulting in patches for the original Falcon 4.0 program, like the Reality Patch, eFalcon and Superpak. Without complete freedom to shape Falcon 4.0 in the desired form, the community became dependant on the initiatives of commercial companies. As it was felt that the features the community wished for had no commercial viability, they took it upon themselves to develop a completely new combat simulator. The main objective of Phoenix therefore is to develop a state-of-the-art combat simulator, based on open source and involving the flight simulation community.
2. Project objectives
To determine what the project’s objectives are, it is important to establish for whom it will deliver products and services. Obviously, combat simulator enthusiasts belong to our ‘customers’. Less obviously, the members of the project team are customers in a sense as well. They are contributing not only because they are interested in the end product, but also because they are interested in the work itself. In this project the way really is as important as the destination.
Thus, the project objectives are:
1. To provide combat simulator enthusiasts with an open source, multiplayer, state-of-the-art, highly realistic combat simulator program that surpasses Falcon 4.0, Superpak 4, FreeFalcon 3 and any current and future commercially available programs.
2. To provide people interested in the development of this program an opportunity to use or develop their skills in a fun environment.
3. Project constraints
1. There is no budget, so we cannot acquire any paid goods or services.
2. There is no deadline (a non-constraint)
3. There is no maximum to the effort spent on the project (a non-constraint)
4. The project will be staffed by volunteers.
5. Project staff will work on the project in their spare time.
6. Project staff cannot meet in person as they are scattered around the globe.
7. The end products must be free from license fees.
4. Assignment to tasks
Tasks will be assigned on a voluntary basis. Each task will be posted so volunteer can apply to do the job. The management team will decide which volunteers will actually do the job, based on skills, available time, and resources needs for other tasks. When insufficient volunteers apply, or the volunteers lack the skills to guarantee the quality of the job, the task will be marked “unpopular”. Unpopular tasks will be traded for popular tasks. “You may do this, but then you’ll have to do this as well”. This way the fulfillment of all tasks is guaranteed, even in a volunteer project.
Si il y ont des personnes qui veulent aider avec se project, fait une poste dans ce thread: http://www.phoenixosfs.org/forum/showth ... threadid=9
