Jump to content

dundun92

Members
  • Posts

    1314
  • Joined

  • Last visited

Everything posted by dundun92

  1. Id say the F-15 under modeling is a fair bit more than a little (at least a solid 40% reduction, and thats vs the very original APG-63) but yes DCS radars are overall poor, and the thing is, the documentation is out there. And even when it isnt, the radar range equation is a thing. You can make VERY good guesses off that (such as the fact that your little APG-68/73 shouldnt be performing better than the APG-63 :music_whistling:). Even if you cant get exact absolutes, at least make it as close as possible comparatively. Yet it seem that for their flagship modules (F-16/18 ) they are just gonna keep them overperforming, and leave the FC3 ones to w/e they are at RN.
  2. Its real, theres a RoKAF version out there as well.
  3. T-33 IIRC is 6m2 frontal, so detection range vs a JF would be in the ballpark of 60-70nm
  4. JF-17 does have a relatively low RCS (3m2), but Im pretty sure you can detect it past 37nm. And no thats not even close to the MAR for the SD-10/AMRAAM at that alt, thats like AIM-54 Mk.47 MAR. It hasnt been made worse, its just always been bad.
  5. The date was moved to deconflict with the Top Gun Super Hornet comp, I did not realize it was on the same day, and was probably one of the reasons for the overall lack of entries
  6. ***COMPETETION DATE IS BEING MOVED TO THE 7TH OF NOVEMBER***
  7. Umm the new API hasnt been out for "years", the AMRAAM just got it a few months ago and there are definitely issues with it. Patience is key. Also, at least for the magic INS, this appears to be caused by the F-14s TWS memory mode and may not be completely due to the lack of new API API (as STT AIM-54s do NOT have magic INS, and neither to any of the other ARH missiles on the old API (Just R-77 as of rn)).
  8. Yep, the AIM-7s will guide on your jammer if you dont turn them off, and you will not get any RWR alert, as its passive
  9. ...the data has been provided in this thread. The fact that some radars overperform (F-16/18) and some underperform (F-15, MiG-29) isnt a reason not to fix them.
  10. That's not the safety time Flappie. The safety time is the time from when the missile comes off the rail till it fuzes and starts manuevering
  11. How accurately modeled are the systems tho? Likely not very
  12. That bug has been fixed (tho it has reappeared once since them and again has been fixed), I dont think thats the point he was making. The bugs he is referring to are the overall poor modeling of the Russian missiles, specifically the R-27 series (this is multi-faceted, and includes the need of the new FM, fully CFDd aerodynamics, fixing of the chaff bug, etc).
  13. Its been reported already
  14. Alamo Squadron Alamo 1-1 | dundun92 Alamo 1-2 | Dankguy Alamo 1-4 | Prez
  15. The default/alternate airspawn loadouts are as follows. Slots 1-2 use the default loadout, 3-4 use the alternate: F-14: 4*AIM-54C,2*AIM-7MH,2*AIM-9M. Alternate: N/A F-15C: 6*AIM-120B,2*AIM-9M. Alternate: 6*AIM-120B,2*AIM-7MH F-16C: 6*AIM-120B. Alternate: N/A F/A-18C: 6*AIM-120B, 2*AIM-7MH, 2*AIM-9M. Alternate: 6*AIM-120B, 6*AIM-9M Su-27S: 4*R-27ER,2*R-27ET,4*R-73. Alternate: 5*R-27ER,1*R-27ET,4*R-73 J-11A: 2*R-27ER,2*R-77,2*R-27ET,4*R-73. Alternate: 4*R-27ER,1*R-77,1*R-27ET,4*R-73 REGISTERED TEAMS (8/16): Alamo Squadron 104th Phoenix Iranian Sky Guardians Raviar/-= IRIAF =- Hunter 64th Aggressors Eclipse Task Force Eclipse Task Force Plastic Edition Task Force Trident RESERVE TEAMS: None
  16. INTRO Mutual Support is a 2v2 BVR Tournament. Naturally, the smaller team sizes often lead to more aggressive and interesting fights that are focused on solid mutual support. Various editions of it will have various rulesets based on the approximate time era chosen; this edition is 1990s themed. DATE AND TIME This second edition of Mutual Support will start at 2000z on November 7th, 2020. The running time will be no greater than 3 hrs. If this is exceeded, the competition will be resumed one of the the following Saturdays at a similar time, based on the teams preference. Registration ends on November 6th. OBJECTIVES AND TOURNAMENT STYLE Each match is conducted as best of three rounds. The objective is to destroy all enemy aircraft (by doing so preventing them from RTBing), and still be able to RTB to the designated base. Note that enforcing the RTB is up to the loosing team; if they want they can tell the winning team to simply respawn. The competition is a knockout-style competition, with teams being eliminated after loosing a 3 round match. Time permitting, looser of the first round of fights will participate in a separate championship. RULES A single team may be comprised of as many pilots as desired; however, only two may be used at a time. Only one pilot is allowed to change between rounds (note that for the F-14, changing RIOs is allowed as much as desired). Aircraft types may not be changed between the individual rounds of a particular match. They can, however, be changed between matches. Mixed fleets of aircraft are allowed (e.g, one F-18C and one J-11A). All spawns are air spawns separated by 100-120nm. Either of designated airbases for the chosen arena (Kutaisi-Tiblisi) is a valid RTB airbase. The competition will be on Caucasus map. [] Weapons employment from outside the engagement zone is not permitted. [DELETED]. Ping limit of 300 is server-enforced. Lonewolfs are allowed; the pairings are to be decided automatically the day before the matchup, and will stay that way for the tournament. Alternatively, you may decide on the pairings yourselves; in that case, simply state the agreed pairings no later than November 6th at 2300z. AWACS will be present, but will NOT have datalink enabled. To keep the event running smoothly, I would ask that suggestions/questions be kept until the end of the event, unless they are relevant to/will affect the remaining rounds (e.g, concerns about excessive lag/rubber banding). One squadron may enter up to 2 primary teams. Any further teams will be put on a reserve roster to allow space to accommodate more teams. If a team cannot show up, or registration is not full by registration end, reserve teams will be moved to the primary roster. More Rules TBD WEAPONS RESTRICTIONS This edition features a roughly 1990s rule set with some exceptions. The BANNED weapons are: AIM-9X, AIM-54A Mk.60, AIM-120C, Nukes. Restricted weapons are: AIM-120B to 6 total, AIM-54 Mk.47 to 4 total. COMMUNICATION All team captains must be present on the Alamo Squadron Teamspeak (server info below) during play. IP: 73.32.85.67 PW: 5775 Questions are to be asked either in PMs, or on this thread. STREAMING AND PRIZES There is no anticipated stream as of RN. If you would want to volunteer DM me. There are no prizes, its simply for the fun of it! REGISTRATION Registration format is as follows: [Team Name] Player #1 Player #2 Player #3 ... As an example Alamo Squadron Alamo 1-1 | dundun92 Alamo 1-2 | Dankguy There will be a limit of 16 teams. OTHER RESOURCES For those that may be interested, but may not be familiar with 2v2 BVR, the 2v1, 2v2, and Tactical Intercepts of "Fighter Combat: Tactics and Maneuvering" are very informative. It is widely available as a PDF online.
  17. did you have ECM on?
  18. BTW Stream is here for anyone interested:
  19. No worries we managed to sub
  20. Just a reminder that the tournament is in just under 30mins. Stream is yet TBD
  21. Yep the DCS DLZs are almost useless. Flanker's is the only one remotely useful
  22. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\F14\Entry\Weapons.lua This contains all the stuff for the F-14s missiles etc Also from checking it its actually 0.05 for the C.
  23. dundun92

    Members age?

    Im just gonna say under 18 and been playing DCS since 2018. Been (space)flight simming as a whole from like 2011 ish.
×
×
  • Create New...