Search the Community

Hello, We have been working on a Cheetah C for DCS the past 2-3 months and we have been making good progress on developing some systems in the EFM. We decided to make the Discord server public for anyone wanting to tag along. It is still very far from something enjoyable so it will take a while, like more than a year to my rough estimation. We are developing this for ourselves to enjoy so we want to have it as best as we can and therefore we are going to take it as far as we can, even try to make it a module if we can meet all the requirements for ED. Even though it looks promising so far, we are not there yet, we still have two or three holes to fill in our collection of information before we can consider that. Otherwise it will be a mod without the features the SDK has to offer. About the Cheetah C The Cheetah is a third generation multi-mission combat aircraft developed by Atlas Corporation (now Denel Aviation) for the SAAF (South African Air Force). It was to replace the Mirage F-1AZ and Mirage F-1CZ fighters during the Angolan war in the 80's to be able to take on the MiG-23 with its superior radar and longer range missiles. Sanctions were placed on South Africa at the time so acquisition of any weaponry was not a trivial task and South Africa was forced to be self sufficient. However, with no prior experience in developing aircraft other than modifications to Mirages and local assembly, South Africa looked for more feasible solutions. Israel had a close eye on South Africa and were already prepared when South Africa approached. Other variants were first developed, D - a trainer, and E - an interim variant while the more advanced C variant was being developed. Each variant has its own origins with the E, D and R variants more closely related. The C's were likely to have been made from old low hour Kfir C2 and possibly some C1 frames with technology borrowed from newer aircraft such as the Kfir C10 and Lavi. The engine, Snecma ATAR 09-K50-C11 from Mirages as South Africa already had many and could not get the more powerful American made General Electric engines from Israel. The Cheetah's were retired from the SAAF in 2008, today they are flying with the Ecuadorian Air Force and Draken International. Where we are (2022/07) 3D Model: Basic cockpit layout (very ugly) Basic external model (inaccurate) We have a nice clickable MFD and MFCD. Very nice accelerometer. A few other gauges and switches that aren't good enough to be mentioned. The cockpit is currently being remodeled by someone more capable. External model will also be remodeled by someone that is proficient. Systems: We have a 90% complete electrical system. The other 10% account for things I overlooked that I am not aware of. All buses are implemented, connected with relays and switches, and ready to be used by the avionics and other consumers, the alternators are connected to the engine with logic to simulate real behavior: Battery Two alternators Two transformer rectifiers Inverter There are a total of 5 AC buses and 4 DC buses. Needs proper testing once we have progressed with the cockpit 3D model. About 75% complete fuel system. All fuel tanks internal and external are implemented (including the negative-G accumulator). They have their capacities, fuel quantities and unusable fuel amounts. Refueling procedures for aerial and gravity refueling (the order in which the tanks are filled changes as well as the amount that is refuellable). The Cheetah C has a switch to change the order in which the tanks are depleted to maintain centre of gravity that is within safety parameters as fuel is consumed - this switch is implemented (no switch model though). The fuel system still requires its fuel pumps and we still need to attach the correct external tanks given a specific external fuel amount from DCS - not difficult, just still a todo. And of course **a lot of testing** is still outstanding. Engine is about 5-10% complete. It idles at the correct RPM for any given altitude. It consumes fuel in a seemingly accurate manner but changes to the engine performance will influence this so it is still too soon to say. The calculations may be correct, the values it is using in the calculations are not correct yet. Many systems of the engine still needs to be implemented. In terms of avionics we have: MFD: On/Off switch with "INDEX" display/menu and the entire "LIST" display family (display family -> collection of pages and subpages). The LIST display family consists of a series of "checklist" or "notes" displays that are made by the pilot during mission planning, these are typically mission specific. This information is loaded onto the aircraft via a data cartridge which we simulate with a JSON file that is editable. We include preset data cartridge files for each map as these include approach procedures for airfields relevant to the mission to give one example. A small desktop application is also in the works to create, edit and load preset data cartridges. MFCD: It is currently only showing a work in progress TSD that displays heading, heading circles, current position, radar targets, waypoints and airfields. We still need to add other symbology like railways, roads, rivers and the flight path. HUD: One of the many modes are currently work in progress, the most used mode - TACNAV. Accelerometer. Our immediate focus (2022/07) 3D Model: Good quality basic cockpit shape. Electrical panel - to test the electrical system. Circuit breaker panel - to further test the electrical system. Fuel panel - to test the fuel system. NMS (Navigation Mode Selector) switch - to interact with various modes and continue development on HUD, MFD and MFCD. Engine start panel. Systems: Test and finish the electrical system. "Finish" is short of adding failures to the electrical system when it is getting abused which will definitely be added. In parallel with the above connect MFD, HUD, gauges etc with the electrical system. Finish fuel system and integrate pumps with electrical system. Continue development on the engine's many subsystems. Discord link: https://discord.gg/fRXXvMuxjs