Jump to content

TheEscapist___

Members
  • Posts

    30
  • Joined

  • Last visited

About TheEscapist___

  • Birthday 07/18/1993

Personal Information

  • Flight Simulators
    DCS
    Falcon 4.0
  • Location
    Cape Town
  • Interests
    Software development, Image processing, Model aircraft building

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We have started work on the Cheetah C over here in the link below. I dream of creating what Combat360 - SAAFOPS set out to do but for DCS. The Cheetah C was chosen because someone wanted to make a Cheetah and asked for information, but I was only able to get good information on the C variant, so C it is.
  2. The work in progress MFD model, it is subject to change or get updated.
  3. 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
  4. I already messaged you on Discord after your first comment, I recognized your name from DCS ZA Sent from my iPhone using Tapatalk
  5. I would also love a decent Cheetah, I would prefer for the mod to be a module but ja. The Cheetah C throttle has more buttons on it, like a full HOTAS, the Mirage one looked a bit naked when I last saw it. Yes we need to do something about it. Dino Cattaneo made an Impala for Prepar3D and is now about to release MB-339 module for DCS with the IFE team that they formed. Mirage F-1 is coming and there are manuals somewhere online for both the AZ and CZ even with the amendments included. MiG-21 is already there, MiG-23 has been started by Razbam if I remember. We need the map more than anything else. I know of someone on Reddit making SANDF things for a game, I can’t remember if it was Arma or something different, might be the same guy you mentioned but we can at least ask and see. Sent from my iPhone using Tapatalk
  6. That one. The aircraft itself is very illusive with its history, but things look promising at this stage in terms of research and specs and limitations and other things, although nothing guaranteed yet. Yeah that turbosquid model is not quite a Cheetah. I would like for him and Combat360 to get back in the game. And this topic shows there is at least a bit of interest from his side. Sent from my iPhone using Tapatalk
  7. Yes that’s also what I was referring to when I said we need to prove that we are capable. Well we can do that at least, static objects are easy simple. I have done one before but I still need to make one good quality one. I am no modeler so I buy my models on TurboSquid etc, but the missions I make them for are not SAAF related. Sent from my iPhone using Tapatalk
  8. Yes! I wholeheartedly agree with this. I sent OP a PM regarding a very related mod I am involved with and possibly getting him or his team involved, I also asked if I could get involved with the plans he has for DCS but he has not read my message yet (sent a week ago so still early). But I see he is very active with other things as well, filming etc. I am also willing to contribute my free time, but there's not a lot of it, I can make myself free most weekday evenings and then weekends as well. I am a software developer with mostly Java experience, moderate C++ experience and a bunch of other languages as well. Lua is still a bit new to me, but my bigger learning curve currently is the DCS ecosystem and how things talk to each other. I am currently giving all my free time to the aircraft mod I am involved with so at least I am conquering that learning curve I mentioned. And to answer your first question, they did, there was a comment made on a YouTube video where OP himself mentioned that he still has all the files and I quote "oh what to do"............. To propose to ED we would have to meet some requirements though, we would need to prove that we are capable, which is difficult because it is like a chicken and egg problem. And with aircraft you have to have declassified official documentation to provide them a way to test and prove that your aircraft performs like the real thing, which is not a problem for at least one of the SAAF aircraft.
  9. I also would like some info or sources about some of these marks, like what the target was, date and time etc. Great map thanks!
  10. When I swap out the Mirage 2000 with a Mirage III mod then it's no longer a problem.
  11. Any news on this? I've also just encountered this while trying to make a mission with Mirage 2000 role playing as Mirage III. They need to scramble from Ramat David, reach WP2 and do fighter sweep. But they take too long to get to WP2 because of the zig zagging. I have tried changing their role to CAP and Nothing but they keep on zig zagging, at first I thought they were maybe searching for enemies.
  12. I really want to have Israel campaigns of all operations, a lot of them are in the South. I'm trying to recreate the ones that fit on the current map from Jane's IAF now but the AI are dumbasses and demotivating. I am now sucked into rather playing Jane's IAF again
  13. I don't know if this is a separate issue but ships don't sink at Batumi port when I bomb them, I thought the water might be shallow there as well. I have no idea if this is realistic or not though, I am no expert.
  14. This seems to be fixed for me in the latest release. I also don't see the weird behavior of AI aircraft before they exploded anymore.
×
×
  • Create New...