Jump to content

Recommended Posts

Posted

Generally when aircrew call, "MISSILE, break!" it is usually because they have visually spotted the physical missile or missile smoke trail and they are instructing the recipient of the message to evade/countermeasure the missile. Otherwise, there would be other calls to "turn cold", "crank", "notch/beam", "slice", "split-S", etc. for more typical and less emergent kinematic missile defeats.

 

For SAM launches where it is unknown what the SAM is currently targeting (usually during the initial portion of the missile's flight where it travels vertically) are usually called "SAM launch" or other ambiguous terminology that is simply noting a launch and not describing its target.

 

I'm confused, therefore, why Jester constantly calls out missiles from well beyond visual range as "MISSILE BREAK." This terminology should only be used for missiles inside of approximately 5 NM (probably more like 1 NM given how small they are and how fast they are moving). If the missile is not smokeless, perhaps up to 10 NM might be reasonable. Also, missiles from directly below or behind the airplane would be invisible to Jester as well.

 

I assume that additional voice lines for Jester are unlikely to be recorded, so I would like to see the "missile break" gated down to only missiles within a certain range of the aircraft. This line should not play unless missile range to your aircraft is <10 NM (preferably less than 1-2NM). This would make the call both more realistic and more useful.

 

Currently Jester calls out so many missiles that are no factor to his jet that the pilot becomes numb and simply ignores the calls even when the missiles are an actual threat ("the boy who cried wolf").

Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights!

 

I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII

  • 3 weeks later...
Posted (edited)

Nothing to add Sir!

 

Those constant missile call outs by Jester make it very very hard to survive on the battlefield.

In MP nearly impossible!

 

They really need to fix that. :thumbup::thumbup::thumbup:

Edited by Niehorst

NZXT H400i case

i9 9900k @ 4,9GHz (cooled by NZXT Kraken X62 4x140Fan - Push/Pull)

Asus RoG Maximus XI Gene with 32GB G.Skill CL14

Samsung M.2 970Pro 1000GB

ZOTAC RTX 2080ti Triple Fan 11GB

34" RoG Swift Curved TFT

 

runs smooth like Beck's Gold :D

 

HTC VIVE pro eYe (still freaking out!)

Thrust Master HOTAS Warthog on MONSTERTECH table mounts

15cm Stick Extension + red spring by SAHAJ 8 (<-- love them)

(TM F-18C ordered)

TPR (Thrustmaster Pendular Rudder)

T.Flight USAF Headset

  • 4 months later...
Posted (edited)

Jester: "JSOW! JSOW!!"

 

Similar issue with Jester, but a funny one. I was testing flags and SA-15 emitter on/off in mission editor. Created a flight of F-16Cs to wipe the floor with JSOW (WCMD variant). Moments after the JSOWs came off the rails of the F-16Cs, Jester yelled out loud: "Okay, here we go... missile, missile". I thought the mission creator had more complexity in controlling a SAM emitter function then what I had expected.

 

I went to external missile view, and chuckled at none but several salvos of JSOWs--all without a single SA-15s in the sky. Mind as well he yelled: "JSOW! JSOW!!" Jester, you silly joker you. You still the best, buddy. :megalol:

Edited by Pally
grammatical error
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...