Default774

Additional tracks/tacviews to look at, now from the target POV with an AI shooting me within NEZ. The missile can be consistently defeated by diving, then pulling up while chaffing. The missile loses track, then tweaks out and loses all of its speed. 120_POV_chase.trk 120_POV_chase_2.trk 120_POV_chase_2.acmi 120_POV_chase.acmi 120_POV_chase_3.trk 120_POV_chase_3.acmi

The AIM-120 currently does not guide properly onto targets using ECM in tail-chase scenarios. The guidance gets progressively worse the higher vertical aspect you have to your target. A few seconds before impact, the missile will pitch up and down for seemingly no reason. The missile might still hit the target, but not always. In the LOOKUP_2&3 tracks/acmis, the problem is especially evident; the Missile pitches down inexplicably and loses track, then proceeds to start twitching away left to right, losing all of its speed. This guidance behaviour only occurs in tail-chase scenarios with the target using ECM. All shots fired within NEZ. 120_ECM_tailchase_COALT.trk 120_ECM_tailchase_LOOKDOWN.trk 120_ECM_tailchase_LOOKUP.trk 120_ECM_tailchase_LOOKUP_2.trk 120_ECM_tailchase_LOOKUP_3.trk 120_ECM_tailchase_LOOKUP_3.acmi 120_ECM_tailchase_LOOKUP_2.acmi 120_ECM_TAILCHASE_COALT.acmi 120_ECM_TAILCHASE_LOOKDOWN.acmi 120_ECM_TAILCHASE_LOOKUP.acmi

Hello, The AIM-120 is still easily notched even in a look-up situation when chaff is deployed in a specific way. When chaff is deployed in single burst, the AMRAAM seems unaffected, however when chaff is deployed in bundles of two, the behaviour changes completely. This behaviour also seems to occur in multiplayer, with an added effect of the missile desyncing massively when it gets decoyed by chaff. For the shooter the missile aggressively goes for chaff. For the target the missile goes straight without making any erratic manoeuvres. I can attach these trackfiles/acmis if needed later. The AIM-120 also seems to behave weirdly after getting decoyed by chaff, snapping between the targeted aircraft and the chaff bundle repeatedly. This does not give an RWR warning to the targeted aircraft. I'm personally not very good at notching, but even I managed to perform this with about 50% success rate. All-in-all, this behaviour doesn't seem right to me, I remember reading that the CCM value of the 120C is set to 0.1 as to mimic rare sensor/seeker failure, this behaviour seems too consistently repeatable to me to be intentional. Trackfiles/tacviews attached. Used CMDS profile(F-16) also attached. nr3.trk nr1.trk nr2.trk nr3.acmi nr1.acmi nr2.acmi CMDS_ALE47.lua

the CCIP(post designate) and CCRP solution cues for high drag Mk82s are incorrect and always result in the bomb overshooting the target by around ~10-15M. This occurs with both the Mk82AIR and the Mk82SE CCIP_highdrag_Miss.trk CCRP_highdrag_Miss.trk CCRP_highdrag_Miss2.trk CCIPPD_highdrag_miss.trk

Fixed in latest patch

Планируется ли добавить ступень Husky HPRF к ракете AIM-120? В настоящее время он отсутствует. На данный момент такой ступени нет, и ракета сразу же отправляется на Pitbull.

Using the dcs weapon lua datamine for reference https://github.com/Quaggles/dcs-lua-datamine The SD-10s reflection(RCS) attribute as listed in the weapon lua is 0.045. Comparing this value to other air to air missiles it doesnt seem to make a lot of sense. The AIM-120, which is smaller than the SD-10, has a reflection value of 0.07. The AIM-7, which has a similar diameter but larger fins than the SD-10, has a reflection of 0.08. Furthermore, the SD-10s RCS doesnt even match up to the RCS of the LD-10. The LD-10 has a reflection value of 0.07 which seems more appropriate for a missile its size. Is this discrepancy in RCS intentional? References: LD-10: https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/weapons_table/weapons/missiles/LD-10.lua SD-10: https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/rockets/SD-10.lua AIM-120: https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/rockets/AIM_120C.lua AIM-7: https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/weapons_table/weapons/missiles/AIM-7P.lua

The new 120 does a random 40G pull a couple of seconds after a maddog launch aim_120_backflip.trk

Может ли любой из наших реактивных самолетов стрелять из 120D, или это подготовка к Eurofighter?

Есть ли планы сделать ракету AIM-120C-7 после завершения С-5?

The backup radio access door clips through the HMCS rotary knob when opened. accessdoor.trk

The AIM-120 pitches down to 30 degrees when manually lofted beyond 30° nose up. When fired beyond 30° nose up the missile will pitch down to achieve a 30° loft angle. loft_15_50.trk loft_30_40.trk

The AIM-120 lofts 5-10 degrees when fired in mad dog/without lock. This might be intentional, but this doesn't seem right to me. maddog_loft.trk

This doesnt work on some pedals because the axis' are different, for example, this method works fine on G29 pedals, but its literally impossible on fanatec pedals

Sadly not, you'll have to apply it for every aircraft you own. Yes. Make sure you save the merged axis as a profile. In Joystick Gremlin settings you can set the program to run on startup and apply your profile on startup. You can also check it to stay in system tray so its out of the way. Side note, the run on windows start up option doesnt work for me, YMMV.

I have the pedal Z-axis(clutch) set as upper half and X-axis(throttle) as lower half. However, you should do it the other way around because the way I have set it up requires you to invert the axis every time, which is a minor inconvenience!

I have Fanatec CSL LC pedals and I ran into the same problem you did. I used to use G29 pedals which, with some axis tune trickery, could be used as rudders. After upgrading to Fanatec pedals I found its no longer possible. I don't think there is a way to do it without 3rd party software sadly. I ended up using Joystick gremlin to merge the clutch and throttle together. In the end this is a better solution than using in game axis trickery even if it was possible as it allows you to press both pedals at the same time without getting jitter from the axis input switching.

(This is based on my current, possibly incorrect, understanding on how these features work in DCS) The current implementation of radar cross sections(RCS for short) in DCS is a single static value for each aircraft. For example, the RCS of the in-game F-16 is 4.0, Su-27 is 5.5, and an A-10 is 10.0. This current system has its drawbacks, namely that this value is completely static and doesnt change based on aircraft aspect or external stores. For example, the F-16 and MiG21 have a fairly small frontal profile, resulting in a lower frontal RCS, but this is not the case for side/top/bottom aspect angles, where the RCS would obviously be different to frontal aspect. The current system in DCS does not reflect this at all. The current system doesnt express all the nuance there is in terms of how visible your aircraft will be on radar depending on your aspect. More importantly, the current RCS implementation also doesnt take into account external stores on your aircraft. This means that (for example) a clean F-16 will have exactly the same RCS as one loaded up with six mk82s, two wing tanks and four amraams. This obviously doesnt make any sense, and it results in far lower radar detection ranges than you should really be getting in reality. The IR signature implementation is also relatively simple. Planes have two values for IR signature, one for military power, and one for reheat. This in practise means theres actually no difference in IR signature between being at MIL power and idle power, remember this next time you slam your throttle to idle when defending an IR missile! In short Make the Radar cross section of a target change depending on target aspect and external stores. Make the IR signature values change depending on throttle setting and stages of reheat, replacing the current two-value system.

Having the same problem. Sometimes cycling the power on the mistrals helps, but not always. The target could be full cold and with reheat and you won't get tone, but another time it will work fine. Just as a note this started happening after the patch for the gazelle that fixed the RWR threat database among other things a couple of weeks ago