Jump to content

Recommended Posts

Posted

Just a question about Mavericks and SPIs

 

When I slew my maverick seeker head to a TGP SPI, even if the TGP is dead on target, the Maverick will not lock on. It requires a slight twitch of the seeker head using a slew command for it to 'find' the target. Is this normal or am I doing something wrong?

Posted

Press TMS Up Short for an instant lock.

"Never give in, never give in, never, never, never, never-in nothing" - Winston Churchill

_________________

Windows 7 64bit - AMD 1090T OC @ 4.02ghz NB @2.6ghz - MSI 990FXA-GD80 - 4x Geil Black Dragon 2GB 9-9-9-28 @ 1666mhz - 2x Geforce 580 GTX SLI OC @ Core 900Mhz Shaders 1800Mhz Memory 2100Mhz - Samsung 24" T240 @ 1900 x 1200 - 2 x Velicoraptor 150GB HDD - TM Warthog - Track IR 5 - Saitek Rudder Pedals - iPad & iPad2 running iControl DCS

Posted

Personally I always slew the seeker once I slave it for guaranteed lock. If you do as above it can still miss Target in my experience

i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64

[sIGPIC][/sIGPIC]

Posted
Personally I always slew the seeker once I slave it for guaranteed lock. If you do as above it can still miss Target in my experience

 

Are you waiting for the tracking gate to indicate a GOOD lock? You can lock it and the tracking gate's ( or lines ) won't touch each other in the centre. I usually wait for the gates to close on the target which I'm guessing is indicating a good lock.

 

There's a gap in the centre before you lock a target, if that gap is still there upon locking it then you should wait for it to close.

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

Posted
If the gates show a solid cross that's force-correlate which actually is a worse lock than plain centroid tracking (gap in the cross).

 

Bare with me whilst I take a screenshot to explain, it's 100% not in force correlate, doesn't work on D Mav's if I recall.

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

Posted

There is a tiny gap just before they touch, here two screenshot's, the target is 100% locked in both screenshot's. I had to re-lock the target as I got in closer ( resulting in a good lock ), the 7.1 mile lock was confirmed since the tracking gate was shaking indicating a lock. Sometimes it will change to a good lock on it's own.

 

I'm not an expert and I haven't read up on this, but my guess is that it's indicating the quality of the lock.

Screen_110503_203251.thumb.jpg.1784617055c939115789433a13403335.jpg

Screen_110503_203313.thumb.jpg.54888c31fbb64aff6a4e214f166e576f.jpg

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

Posted

The 2nd picture is the one I look for myself. There are so many different ways things can be done its a surprise the real hog pilots remember it all:)

i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64

[sIGPIC][/sIGPIC]

Posted
The 2nd picture is the one I look for myself. There are so many different ways things can be done its a surprise the real hog pilots remember it all:)

 

No harm in me checking :). They fly daily I think so it's much easier to remember. If I don't fly for one week I forget how to start her up. I've forgot that procedure around 6 times from taking little breaks.

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

Posted
There is a tiny gap just before they touch, here two screenshot's, the target is 100% locked in both screenshot's. I had to re-lock the target as I got in closer ( resulting in a good lock ), the 7.1 mile lock was confirmed since the tracking gate was shaking indicating a lock. Sometimes it will change to a good lock on it's own.

 

I'm not an expert and I haven't read up on this, but my guess is that it's indicating the quality of the lock.

 

Ah I see that's not force correlate. Is there a noticeable difference in lock quality between those two states?

Posted (edited)
Ah I see that's not force correlate. Is there a noticeable difference in lock quality between those two states?

 

Going to do some tests with the D model firstly firing four off in the first bad lock and then four in the good lock, see if it makes a difference.

 

Edit: Found an interesting thread on the forums. It appears the Maverick employment with regards to symbology may be incorrect at current. http://forums.eagle.ru/showthread.php?t=71672

 

From what I can gather on that post a steady cross should indicate a good hit chance and a flashing cross should indicate that the Maverick might break lock during it's flight to the target.

 

This quote from an actual USAF training guide,

 

"A flashing Pointing Cross in the Weapon MPD indicates that because

of the current geometry to the target, there is a chance the missile

may break lock when launched. For best results, ensure the pointing

cross is not flashing before firing the missile."

[/Quote]

Edited by Sinky

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

Posted

Interesting, the "could break lock due to geometry" is an interesting note. I imagine you'd have to be pretty close or at high aspect to have the launching of the missile cause problems for keeping lock. Maybe the Mav doesn't like the target point undergoing high relative motion.

 

Godspeed with testing. Mav misses for me are so rare I wouldn't envy trying to figure out if good/bad lock was responsible for the difference between 1% miss and 2% miss.

Posted

I've only managed one test so far and 3 of 4 mavericks missed for one reason or another, couldn't seem to replicate the "bad lock" so these were on what I think were good locks, upon flying closer in I was having more success. Will possibly be doing more tomorrow. I'm at the conclusion so far that the range at which you launch is the main factor, think my tests were around 6.5 miles.

[sIGPIC][/sIGPIC]



 

ASUS M4A785D-M Pro | XFX 650W XXX | AMD Phenom II X4 B55 Black Edition 3.2ghz | 4GB Corsair XMS2 DHX 800mhz | XFX HD 5770 1GB @ 850/1200 | Windows 7 64bit | Logitech G35 | Logitech Mx518 | TrackIR 4

 

My TrackIR Profile ( Speed 1.2 / Smooth 30 ) - Right click & save as.

 

  • Recently Browsing   0 members

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