dundun92

AFAIK no, id guess this is some sort of LOS rate limit but I really dont know, its pretty close to Rmin though, so its probably related to some pre-launch constraint.

@BIGNEWY said its planned to be fixed, theres no reason if you break lock at say 40nm on a lofted shot the missile should fly into space, it should use the INS to fly to last known target position, its just one of those WIP things. But CSGO, it should NOT get new datalink if you regain lock, that is not realistic

If you have a track I can simply replay it when I get a chance

You cant use the TTA counter to base this entirely. Simply look at the tacview for that moment (use a flare drop), and see how far the missile actually is (active range is 15km, hardcoded), the TTA counter is not the most accurate.

they arent by this bug, and I think you very well know that, as you know itd mean exactly 0 Pk for the ER under all circumstances

So you want this to affect ERs as well? And R-77s? Sure if thats the case, lets make applicable to all missiles, as it "should" in your words.

Alamo Squadron was founded in 2020 as a squadron focused on excellence in the air combat (specifically BVR) arena. We are an air to are focused squadron, but we occasionally do A2G to chill. We offer a cadet program that progresses you through the various skills and concepts needed to excel at BVR combat. We also participate in and practice for PvP events, such as the upcoming SATAL 2021 tournament. Our specialty aircraft are the F-14/15/16/18, but we fly many others such as the FC3 jets, Mirage 2000C, and JF-17. Currently, we are looking for 3 more pilots to add to our roster. Our squadron forums group is here: https://forums.eagle.ru/clubs/320-alamo-squadron/ We hope to see you in the virtual skies!

Yes and no. Yes in the sense that we can launch outside of seeker range, what the radio correction is there, no in the sense that its not modeled properly. In DCS AFAIK it just models SARH as having infinite range seekers, rather than limited range seekers and a distinct radio correction phase. So for practical purposes it is modeled, just not technically correct.

Except that it does now . And the F-18 wont jam unless you STT it, wont jam you in TWS/RWS

no, only PD

They stated a few years back (like 2012 or smth?) that they had the docs for a FF Flanker, its not the issue here. Its legal issues, as have been the problem for ED from the start

If you call a M1.3 AMRAAM at 40k much of a threat compared to a M1.7 ER (those are the speeds when they hit the same distance, not accounting for target closure which will benefit the ER in a tail chase with the shorter TOF, but will benefit the AMRAAM in terms of Rmax as the target had more time to cover more distance for the missile) and are going off pure Rmax termination criteria well yea it will, thats just a consequence of the 20s longer battery life, has nothing to do with kinetics, CFD wont fix that.

Dont have tracks, but I do have tacviews and the telemetry: From 40kft M1.5 the ER will beat any AIM-120 out to its battery lift of 60sec

No, the bug happens after active only. Burnthrough doesnt matter to missiles. Any missile that has gone active can be trashed like this.

For relative range, maybe, for absolute range (what you need), nope They can, but not the older ones we have in DCS (C-5/B)

It shouldnt no, but it does for some reason. After all, percise lofting (as implemented in DCS) requires range information. Ableit, simple G bias lofted could theoretically work even under ECM as no range info is needed, but thats not whats happening

If you ignore the loft, the ER in DCS actually will beat both variants of the AMRAAM (B by a sizeable margin, C by a smaller one) in a straight-line drag race out to its battery life of 60sec, and this is at 40kft M1.5 launch. Im not sure how your managing to get an ER to run out of energy before battery life from any sort of high altitude shot profile, unless theres significant target manuevring involved here. The only reason you have shot profiles where the 120s beat the ER in DCS is the lofted kinematics (which only really matter above 20-25k, and outside 20nm), which begs the question, what "range" is being refered to here? NEZ? Rmax? MAR? There simply isn't enough context to declare that the ER-120C range imbalance is "flipped", at least in any significant way.

"Associate launched TWS AIM-54 with a track rather than object; to disambiguate multiple tracks with the same target object." Slightly curious, what is the practical effect of this?

Alamo Squadron Alamo 1-1 | dundun92 Alamo 1-2 | Dankguy

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 February 13th, 2021. 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 February 12th. OBJECTIVES AND TOURNAMENT STYLE Each match is conducted as best of three rounds. The objective is to destroy all enemy aircraft, and keep at least one of your aircraft flyable. 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 80nm. There will be two arena's, so that two matches can occur simultaneously. 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 February 11th 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. ECM is banned Use of PH/ACT switch outside of 10nm is banned. 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 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. ========================================== 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-9M. Alternate: 6*AIM-120C, 2*AIM-7MH, 2*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 (1/16): Alamo Squadron RESERVE TEAMS: None

Im not nessecarilly doubting this, but have you tested vs the actual acceleration charts to see if the clean drag is actually too low, or it it just speculation (no offense intended here)?

Fortunately for us ED made the F-18 despite this

The F-15 is described as being that easy to fly and forgiving IRL with very few adverse characteristics like that, so no thats not unrealistic. And ive been able to induce plenty of "bad stuff" from intentional ham fisted flying, such as flatspins and such.