dundun92

Alamo Squadron I Alamo 1-1 | dundun92 Alamo 1-2 | Dankguy Alamo Squadron II Alamo 1-3 | Griffin Alamo 1-4 | Prez Alamo 1-5 | Emperor

The default/alternate airspawn loadouts are as follows. Slots 1-2 use the default loadout, 3-4 use the alternate: F-14: 4*AIM-54A Mk.60,2*AIM-7MH,2*AIM-9M. Alternate: 4*AIM-54C,2*AIM-7MH,2*AIM-9M F-15C: 6*AIM-120C,2*AIM-9M. Alternate: 6*AIM-120C,2*AIM-7MH F-16C: 6*AIM-120C. Alternate: N/A F/A-18C: 6*AIM-120C, 2*AIM-7MH, 2*AIM-9M. Alternate: 6*AIM-120C, 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 JF-17: SD-10*4, PL-5*2 REGISTERED TEAMS (2/16): Alamo Squadron I Alamo Squadron II RESERVE TEAMS: None

​​ 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 2000s themed. DATE AND TIME This second edition of Mutual Support will start at 2030z on November 21st, 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 20th. 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. There will be two arena's, so that two matches can occur simultaneously Either of designated airbases for the chosen arena (Kutaisi-Tiblisi) is a valid RTB airbase. The competition will be on the Caucasus map. 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, and WILL 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. ECM is banned (unless ED fixes the ECM blinking bug) More Rules TBD WEAPONS RESTRICTIONS This edition features a roughly 2000s rule set with some exceptions. The BANNED weapons are: AIM-9X, Nukes. Restricted weapons are: AIM-120 (all variants) to 6 total, AIM-54 (pending RWR bug fix) 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.​

Your forgetting that IRL pilots arent playing games like yours with evading AIM-120s. They have a minimum abort range for a reason. They arent timing missile defense based on exactly how far away it is on the RWR. Not only may the RWR display not be capable of showing it, RWRs arent that accurate IRL, definitely not for this kind of thing. The F-16 RWR (along with most DCS RWRs) in vastly overmodeled and is wayyy to accurate. Not that I dont evade missiles the same way in DCS. But just saying I dont expect it for an RWR IRL.

1 is incorrect, at least in DCS. Both SAM (F-16) and STT give no launch warnings for AMRAAMs. As for IRL it's going to be RWR specific, not something there's gonna be any public info about. As for 2, for most FF aircraft jamming effects simply havent been implemented yet. Also in the ECM does completely disable Su-27 TWS at all ranges. In the F-15C it makes TWS unusable outside of 22nm.

FYI he is an IRL F-15E WSO.

Theres no reason ECM would force a missile warning at launch. Even if STT was forced, STT does not give launch warnings for AMRAAMs.

Congratulations to ETF for winning this edition of the Mutual Support! The link to the tacview is here: https://drive.google.com/file/d/1YOTUmg9PhxI3n3wELVfhp7PGp_AIXh3e/view?usp=sharing

Just a reminder that the competition starts in one hour! Please try and show up in the TS around 10 mins before if possible, it would help speed up things. Stream is yet TBD

I think the F-15 -34 mentions this, havent read that section in a while so I could be wrong. EDIT heres a quote: With an AIM-7 in flight and the spit-s tracker logic enabled due to target maneuvers, the radar enters a nutating conical scan that rotates the antenna in a 360° circle at a 1 second rate, centered about the 2.5° beam edge and providing a 5° beam width to find the target. The nutating scan starts 6 seconds after the standard split-s logic is enabled. The nutation shows up as a gyration in the TD box and an oscillation in the AZ/EL carets on the VSD. Unless the pilot rejects, the radar will continue in split-s logic until last missile TOF plus the 15-second pad expires, then return to search.

Nobody "equipped" the AIM-54 with anything. This is simply a case of the attempted upgrade to the new API causing issues (the AMRAAM already has its fair share of bugs and issues from it having the new API). As for why its an AIM-54 only issue we really dont know, and it really doesnt matter. All that matters is that it gets fixed ASAP.

Also I probably should add, this may also have something to do with specific RWRs because from some testing ( I can produce a track if needed) the F-15 RWR picks up AIM-54s just fine from TWS.

Personally im fine with Fox 1 stuff, but if that became the case Id probably want to switch to a blue F/A-18.

In singleplayers chaff is simply more effective for missiles on the old API. Dont ask me why.

Also I will add: ECM is banned. We will be watching for use of the ECM exploit, so please dont do it.

So here are the preliminary brackets:

Im pretty sure theres a waveform change for most SARH, even PD SARH. Also I think this is less about SATAL and whatnot, and more about the fact that is a unintended, unrealistic, game breaking bug. A TWS launched, AIM-54 RN gives no active warning at all, its essentially a Fox 2. Thats definitely not intended, and pretty much ruins any sort of BVR vs F-14s.

The Fi values and OmViz stuff are related to seeker gimbal limits, LOS rate limits, etc. So yea no clue. Guess its testing time lol.

In notepad++ it comes out as расчет времени полета, which translated to "flight time calculation", and it shows up for IR missiles as well.

Thanks! However, that field isnt on the old API missiles (like R-77). Do you know where it would be for them?

So considering the recent AIM-54 issues caused by the latest patch we have 2 options: Simply revert to DCS 2.5.6.55960 We could alternatively all agree not to use F-14s Im leaning towards 1 but if everyone would be OK with no AIM-54s we could go ahead with 2

Not only that, TWS AIM-54s arent giving pitbull warnings of any kind.

It gives no pitbull warning, its literally a BVR Fox 2 rn.

Yes thanks for the overhaul ED, MUCH easier to use

Slightly curious, where are the luas with this stuff? Unless its hidden in the missiles_data.lua somewhere? Or is it in the lua for AI radars?