Jump to content

Recommended Posts

Posted (edited)
I have just run a simple test with 2 AI Mig-29s coming at me at altitude (although I had a few thousand feet on them), and got the Shoot cue at about 22 miles

The range is less important than the Rmax triangle (@ 6 O'clock) but 22 NM seems reasonable, IIRC the shoot cue was appearing at 10-15 NM (head-on non-manoeuvring target) but I quickly realised it was bugged and started ignoring the non-appearance of the "Shoot" cue.

 

I've no idea how it's "fixed" itself but it is what it is.

 

E̶d̶i̶t̶ ̶-̶ ̶i̶t̶'̶s̶ ̶t̶h̶e̶ ̶c̶h̶a̶n̶g̶e̶ ̶i̶n̶ ̶s̶y̶s̶t̶e̶m̶ ̶t̶i̶m̶e̶,̶ ̶s̶e̶t̶t̶i̶n̶g̶ ̶m̶y̶ ̶P̶C̶ ̶t̶o̶ ̶2̶0̶1̶9̶-̶1̶2̶-̶2̶1̶ ̶c̶a̶u̶s̶e̶s̶ ̶t̶h̶e̶ ̶H̶U̶D̶ ̶S̶h̶o̶o̶t̶ ̶c̶u̶e̶ ̶t̶o̶ ̶n̶e̶v̶e̶r̶ ̶a̶p̶p̶e̶a̶r̶ ̶i̶n̶ ̶m̶y̶ ̶t̶e̶s̶t̶.̶

 

:doh: It was user error, I was letting the Steering Dot drift outside the ASE Circle, so although the target was within Rmax, I didn't get the "Shoot" cue.

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted

Glad to hear it's fixed as I was having the same late shoot que as well... but what a bizarre reason for it to break/ fix itself...

Posted
... what a bizarre reason for it to break/ fix itself...

 

In my case, it's turned out to be user error - I was letting the Steering Dot drift outside the ASE Circle, so although the target was within Rmax, I wasn't getting the "Shoot" cue.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • Recently Browsing   0 members

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