NikolaiVChr / f16

General Dynamics F-16 for Flightgear flight simulator
GNU General Public License v2.0
120 stars 39 forks source link

Plan for development on the F-16 #290

Open NikolaiVChr opened 3 years ago

NikolaiVChr commented 3 years ago

Nuclear weapons

Due to the fallout in the Flightgear community when some put nukes on aircraft, F-16 will have no nukes. Also to keep it OPRF compatible. They can hang as dummies on the pylons, but thats it. No jettison them, no simulation of dropping them in live or dummy versions.

Variants and cockpit

The cockpit and systems will work as block 50. So except for MISC and the small EW panel next to RWR plus HSI, we just go with what is made already, which is sorta of a mix. Changes to that shall be to block 50 layout. We only have elec. diagrams of block 50 and 10, not going to invent some fantasy elec. system for other blocks. And yes, that differs alot between block in real life. Some things that is on DC bus in one block is on battery bus in another etc. etc. Plus it has taken us 2 years to even get the controls to 3D and animated on the current cockpit layout, not going to start from scratch on that. Same goes for MFD/DED and HUD. We keep them same across blocks, except for colors, or small things that very easy to make. And I am NOT going to maintain or make elec./systems for different blocks. Would require tons of changes across the whole aircraft, especially elec/hydr but many other things also, like caution light logic etc etc..

Quality Better to have something crappy that has no bugs, that something fancy with bugs. Squash bugs! Make a big effort to do that.

Other sims Do not headlessly copy features from BSM and DCS. They can be used for inspiration on what to make, but verify in official documents or other good sources that it worked like that.

JMaverick16 commented 3 years ago

The first point has been further addressed and limited.

Current cockpit layouts reflect MLU and Block 50 with some minor changes in between. Only panel remaining which would require rework is MISC as shown here: https://www.xflight.de/pe_org_par_cec_misc.htm with some exceptions to simplify compatibility (eg. Block 30 will have RF switch instead of IFF ident to avoid useless left console rework). Aim is to keep these changes by recycling already existing props/code and greatly limit the required work to implement them, mostly by subdividing work to slowly implement these features without affecting the flow of improvements.

True, but I still think delivering bug-free quality is doable.

Totally agree with regards to last point, especially since we have also people in the job to ask for doubts.