dundun92

Magic INS is gone, has been for some time. Seeker gimbals are ±60°. These 180° turns are being caused by datalink telling the missile where to turn (which as GGTharos said isn't realistic for the AIM-54 specifically when outside gimbals, but there's not much HB can likely do in that regard, its just a DCS thing), the seeker isn't actually seeing the target.

if its a harrier thing its not an R-73 bug, RAZBAM would be the best to report this to

The thing is that it already goes after a few flares, no spam is needed.

exactly what needs retesting is the question? The fact that you personally cant defeat R-73s? Happen to have a source of ED stating that flare spamming as you performed it in the track is guaranteed to defeat the R-73? I don't think so.

Pretty sure its more INS wonkyness causing that yes

We literally just had some fights with the KIAP under a week ago, and some a few weeks ago and we defeated plenty of R-73s with flares. Its very easy. IMO a bit too easy. But regardless, complaining on the forums isnt changing anything.

sadly, even basic IRCCM like this is completely absent from the game.

Its an FC3 bug. For example, if in the Su-27 you fly with a single ET, you HAVE to load it on station 3 else you get this bug

HB has stated that the F-14 has to tell the AIM-54 to go active for all variants, the manual states this and makes no distinction between the A and C

No that's not what PH/ACT is for. That tells the missiles on the rail to go active off the rail. It shouldn't have any effect on missiles in flight.

It means you broke the lock before the peak of the loft. This is an AMRAAM bug that I probably should get around to reporting. But at least it forces you to support missiles until they are fairly close to active.

All sparrows but the E HOJ in DCS

Its been like this from release. Its an ED side thing that they haven't bothered to fix.

Its not done on purpose, U is for unknown on the RWR. This clear when you realize that the F-14 itself shows AIM-54s as a "M" not a "U". ED simply hasnt updated the RWR codes for their jets. The SD-10, for exmaple, has been ping-ponging around between showing as a "M" vs a "U" (RN it shows as a "U")

"In PD-STT (Pulse-Doppler Single Target Track) the AIM-54 will be launched in a pure semi-active mode and be guided in that mode all the way to target without going active. This means that the engaged target will get an immediate engagement warning through its radar warning receiver from the AN/AWG-9 as soon as the AIM-54 leaves the rail. Like in TWS the missile will loft if fired at range." Is this not clear enough? Link: http://www.heatblur.se/F-14Manual/weapons.html#aim-54-in-dcs

Thats how its supposed to be, it was bugged all this time.

Nice! I use a similar-ish script for when I fly the Su-27 and F-15, its really helpful.

Yep here's the thread: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/bugs-and-problems-ai/weapon-issues/289734-amraam-chaff-bug If makes notching the AMRAAM ridiculously easy as simply dropping about 2-3 chaff while in the notch gate stops the missile reacquiring, as it is stuck on a chaff bundle with no radial velocity/doppler shift :music_whistling:

This part is definitely on EDs side, the AMRAAM has the exact same bug. I reported it a while back but no response.

Was reading the manual, and found this quote: So in PD-STT at least HB states the target should get a launch warning.

Thats because you have one of the game mode options on, forgot the name, but thats not the RWR.

============TOURNAMENT POSTPONED, NEW DATE TBA, LIKELY AFTER NOV 28TH============

There’s no need to defend super early. Thats one of the bigger BVR mistakes. In BVR, you have what is called the Minimum Abort Range (MAR), which is the closest you can get to a bandit and still be able to turn cold, and outrun his shots. Theres no need to do any super aggressive pre defending (although after shooting it is advisable you enter a crank + dive). For example vs a AIM-120C on the deck its 6-7nm, at 20kft its 12nm, and at 40kft its 26nm. As long as you turn cold before reaching the MAR you will always be safe in BVR. So in the example of you and a bandit both at 40kft M1+, youd want to shoot at around 40-45nm (whenever above 25kft and 25nm, be sure to pitch up 30° before firing), then crank + a maybe 30° dive to about 25kft. Once you hit the MAR, begin your abort, a simple split-S is fine. If you were at say 20k, shot range would drop to about 15nm (the reason for the drastic drop is the lack of loft effectiveness under 25kft). The most important thing is to always respect the MAR, unless you want to start notching missiles. Its doable, but when you are new I wouldnt mess with that yet. Focus on kinematically defeating missiles. Also, just my opinion, but I wouldnt use GS for anything but the very basics of BVR. He mixes up terminology quite a bit, and overall often simply doesnt know what he’s talking about. For the basics he’s OK but when it gets into tactics imo he simply isnt the best. As for notching, maybe this diagram will help. You are not trying to get zero closure. You are trying to get the same closure relative to the ground under the bandits aircraft.

Actually, RWS from my experience does have a slightly higher detection range (often ill get RWS hits, switch to TWS, and it wont see it for a bit). Also, forgot to mention, you need to use HPRF for the initial detection of targets. Essentially, outside 20nm use HPRF, inside 20nm or if he is cold use MPRF. Never use interleavened imo, it doesnt have enough range vs hot targets to detect it with enough time at high altitude. The F-15 does not have the ability to jettiston individual tanks. The default order drops the wings first, hence why you only take 2 unless you need the range (which is almost never in DCS). BTW, heres a quote from the F-15C manual about climb profiles: