Jump to content

Recommended Posts

Posted (edited)

Hi Guys,

So, per my understanding any inaccuracies before the missile "leaves" the aircraft are handled by your team not ED. 

My understanding of the F1 manual, the 530IR and the 550 magic 1, can and do have an "automatic uncage" behavior. I.e. when they get a tone for a target they unlock the seeker so it can track the target thats over some minimum signature. So good job there.

However. US missiles used on the mirage this is generally not the case.
Bug 1:
Aim-9B cannot be uncaged on the aircraft until fired at all. I.e. you have to keep the missile within the sidewinder IFOV of 4 degrees until launch, where it uncages. (Current bug, seeker acts as if auto uncaged once you get tone, it is impossible to do this with this missile). I.e. lock target and then move the missile centerline off the target. It should loose lock outside of the 4 degree IFOV cone. (source F8 tacman Pg 1-149, as well as F4 tacmans pre-1980)
 
Bug2:

Aim9J. Again does not automatically "uncage/lock", basically you have to maneuver the target into the seeker FOV (2.5 degrees in this case) centered on the flight path. THEN you either manually must depress (and sometimes hold down) the "uncage switch" or you can hit fire and shoot it caged like a 9B (will uncage when fire is pressed). Source (most USAF -34s have this info f4/5/15/16). With the uncage switch pressed the seeker will track the target through the 40 degree seeker gimbal. Presumably the 300/600/gun lock switch does this 

Bug3: 
Aim9 Juli, basically similar issue to the Aim9J i.e. "auto lock" but more complex since its basically a 9L seeker which does have the ability to be pointed by either the radar or "seam" but in each case you basically have to "lock" the target by using the uncage switch. most USAF -34s have this info f4/5/15/16. Presumably the 300/600/gun lock switch does this. Also there is likely a way to switch between SEAM/radar modes. 
 


 

Edited by Harlikwin
  • Like 5

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

  • 3 weeks later...
Posted

Hi @Harlikwin. I haven't tested this part bu the changelog of today's OB update says it's fixed:

Quote
  • AIM-9B seeker head now always remains caged, until it is launched.
  • AIM-9B seeker head has now an instantaneous FOV of 4 degrees.
  • Reduced AIM-9B seeker head detection range.
  • Updated all Sidewinder missiles audio. Removed the steady high pitched tone when a target is tracked. It should be present in AIM-9M only.
  • AIM-9B now gets no audio tone when the tracked target is centred in the missile FOV.
  • Reduced all Sidewinder missiles launch delay down to 0.8 seconds.

Can you please check everything is now OK for you?

  • Like 1

---

Posted (edited)

No its still in error.

AIM9B is correct.

J/P/Juli caged/uncaged and lock on mechanization still bugged ...... Reported in the Closed beta area.

Edited by IvanK
  • Like 1
Posted
On 9/2/2022 at 11:58 AM, Flappie said:

Hi @Harlikwin. I haven't tested this part bu the changelog of today's OB update says it's fixed:

Can you please check everything is now OK for you?

Well
#1 the aim9B got fixed really nicely (Awesome and thank you), with that null in there it actually works super well (and now has the distinction of being the only entirely working 9b in all of DCS)

#2 When I briefly tested it the 9J/P still did the autolock.  Basically should work like the 9B but can be uncaged with the (300/600 button) so that they will track within the gimbal limits before firing, allowing you to pull lead for the missile in close combat. And also the seeker IFOV on the 9J is 2.5deg instead of the 4 deg of the 9b. (basically how the 9P works on the F5E)

#3 The 9J/JULI, Honestly IDK if the JULI on the F1 can autolock or not, if it can, then that would be plane side weapons computer integration much like radar pointing. The 9L seeker is theoretically capable of both being cued by radar, and autolocking, but I don't know if it was ever integrated onto the mirage F1 that way. Given how basic the F1CE weapons computer is at a guess probably not.

Also

#4 The 550 should autolock in a wide search pattern, but then when the 300/600 button is depressed it should run a narrow pattern at the boresight. (This is to make sure you lock the right guy in a furball) 

At any rate if Aerges fixes 1 missile a month I'm a happy camper. Esp if its done well like the 9B was. 

  • Like 1
  • Thanks 2

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted

Spanish CE,EE and M version never had seeker radar slaving. So the only posibility you had was look for tone in the upper part of hud and then uncage the missile using misile lock/unlock button on the throttle.

  • Like 1
  • Thanks 2
Posted
On 9/6/2022 at 3:20 AM, chichowalker said:

Spanish CE,EE and M version never had seeker radar slaving. So the only posibility you had was look for tone in the upper part of hud and then uncage the missile using misile lock/unlock button on the throttle.

Thats good to know and not really that surprising. On the upside it should have the expanded SEAM search pattern.

So the only radar slaveable IR missile should be the 530IR in that case. 

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

  • Recently Browsing   0 members

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