Using the AGM-65F

[AG-51_Sabot]

I have one of my squads missions I run. 30K and 15nm out I'm locking targets and firing. I fired 3 AGM's with good hits on targets, but when I tried to get a lock on the 4th I was too close (5.4nm)

 

After each shot the cursor caged and I had to slew to the target area

Edited December 27, 2018 by AG-51_Sabot

[javelina1]

Yes. I absolutely love the laser MAVs. Dead on accurate. Can't wait until we can "self lase".

 

 

exactly, will be awesome when we can pick out our targets. :)

[Alphamale]

I have one of my squads missions I run. 30K and 15nm out I'm locking targets and firing. I fired 3 AGM's with good hits on targets, but when I tried to get a lock on the 4th I was too close (5.4nm)

 

After each shot the cursor caged and I had to slew to the target area

 

Try to put your velocity vector in the target area, you won't have to slew as much after each shot

[Hog_No32]

[...]

After each shot the cursor caged and I had to slew to the target area

 

I think that is understandable because after a shot, you‘re now looking at the seeker image of a different missile which was not slewed to your previous target. I don’t believe the seeker heads of multiple missiles aboard are synchronized in any way. You only control and slew the seeker of the individual missile on the station you have selected.

Edited December 28, 2018 by Hog_No32

[poochies]

Yeah the only way for the next MAV to be looking at your last target is if you had a TGP locked onto that area. Then uncage your next mav and it slews there automatically, as in the A10 and Harrier

[Eagle7907]

Yeah the only way for the next MAV to be looking at your last target is if you had a TGP locked onto that area. Then uncage your next mav and it slews there automatically, as in the A10 and Harrier

 

 

 

I believe you are correct. Judging from how the F-16 is able to slave ALL the Maverick seekers. However, it is a different platform. We will know in time.

 

 

Sent from my iPhone using Tapatalk Pro

[skidog1st]

is anyone else getting a blank screen on there ddi when the push the maverick button on the stores page twice?

 

I know it is supposed to bring up the targeting camera but I get nothing?

forgive my ignorance if this has been brought up before or is just a bug.

[majapahit]

is anyone else getting a blank screen on there ddi when the push the maverick button on the stores page twice?

 

I know it is supposed to bring up the targeting camera but I get nothing?

forgive my ignorance if this has been brought up before or is just a bug.

there's a warm up time from takeoff 1st time, shows a timer (2:30 I think I remember), air start no warm up time

[skidog1st]

there's a warm up time from takeoff 1st time, shows a timer (2:30 I think I remember), air start no warm up time

 

I don't get a timer showing up anywhere. I am beginning to wonder if it is something to do with me exporting it to another monitor. but it is also blank on the main monitor as well.

[majapahit]

I don't get a timer showing up anywhere. I am beginning to wonder if it is something to do with me exporting it to another monitor. but it is also blank on the main monitor as well.

disable your export mod and chk your main monitor?

[skidog1st]

disable your export mod and chk your main monitor?

 

that didn't work either. I uninstalled the module and reinstalled and now it is working even exported to multiple monitors it works fine now.

 

thanks for the help.

[holce]

Maverick Problem

 

Don’t know if this is a bug or a problem with my machine, but when I arm the maverick and then select maverick page ,my mfd goes black, no maverick ir image or labels for the osb’s. but I can then come out of that page and all is normal,

I have exported my mfds but the a10 Mavericks and tgp display no problems

I wondered if anyone else has this or just me?

Thanks for any feedback.

[Sparky1b09]

Don’t know if this is a bug or a problem with my machine, but when I arm the maverick and then select maverick page ,my mfd goes black, no maverick ir image or labels for the osb’s. but I can then come out of that page and all is normal,

I have exported my mfds but the a10 Mavericks and tgp display no problems

I wondered if anyone else has this or just me?

Thanks for any feedback.

 

If your Mav is looking into an open sky you will get that blank image. Try pointing your Mav at a known land mass before you try anything else just to be sure it's not something super simple.

[Sparky1b09]

Are you using the left or right DDI? You have to use the left DDI for the Maverick. Perhaps that's the issue.

 

This isn't true. I always use my right DDI and it works fine. You just need to make sure the right side is you sensor of choice. Either side works.

Edited December 31, 2018 by Sparky1b09

[Sarge55]

Ya my bad, was thinking Harrier... too many planes to fly.

[Sparky1b09]

Ya my bad, was thinking Harrier... too many planes to fly.

 

I hear that!

[majapahit]

Someone else mentioned this exact problem, he uninstalled and reinstalled the module (prob your exports mod messed up the install)

[holce]

Seems I edited my mfd lua wrong, reloaded f18 module the edited my mdg_strokedef lua to stroke thickness = 0.4 and stroke fuzziness =0.1 my hud and mfds look a lot crisper and I can now see my maverick page

 

thanks for the advice.

 

[/img]

[/img]

Edited January 1, 2019 by holce

[Sgt_Fresh]

AGM65 Wont Lock On Target

 

Yup tried everything. Sensor select TD Down. Cross slews over target but wont lock no option for fire the missile. I have viewed many tutorials on YouTube and followed them to the letter no go. What works?

 

I still cant get auto pilot to engage

My rear stabilizer points straight down creating a giant air brake

 

Is anyone fixing bugs?

 

Same results on X55 and Logitech 3d pro FCS.

[majapahit]

Yup tried everything. Sensor select TD Down. Cross slews over target but wont lock no option for fire the missile. I have viewed many tutorials on YouTube and followed them to the letter no go. What works?

 

I still cant get auto pilot to engage

My rear stabilizer points straight down creating a giant air brake

 

Is anyone fixing bugs?

 

Same results on X55 and Logitech 3d pro FCS.

Sensor diamond on TV screen?

your pitch has double binding in controls ?

[majapahit]

you need sensor diamond on TV screen

[shagrat]

 

Is anyone fixing bugs?

.

Apart from the things already mentioned (likely you have multiple controller axis mapped to pitch, and forget to push the sensor select switch right/left or press TDC release), l can assure you, others don't have that "bug".

 

In addition there is a proper way to file a bug report. Things like what did you do exactly, maybe a track file? Anything more than "I can't make this work", helps a lot.

[Tomsk]

Yup tried everything. Sensor select TD Down. Cross slews over target but wont lock no option for fire the missile. I have viewed many tutorials on YouTube and followed them to the letter no go. What works?

 

There are several reasons you might have trouble with Mavericks.

1. Did you warm your mavericks up first? Otherwise you will get TIMING and a countdown in the top left until they wake up.
    
    
   
2. Did you use the castle switch to move the diamond into the Maverick sensor? Easy to forget to do and if so you can move the TDC all day long and nothing will happen. Sadly this is a really non-obvious state in the Hornet, unlike the F-16 or A-10C where the 'NOT SOI' over the display makes it pretty obvious what is happening.
    
    
   
3. The cage/uncage mechanic can be a little counter intuitive. When the maverick is CAGED (as shown in the top-right of the maverick display) the maverick triangle will stay stuck pointing near the nose of the jet. If you try to slew it when it is caged, nothing will happen. You first need to UNCAGE the maverick (using the cage/uncage HOTAS button) and then you might be able to slew it around. Just to add to the confusion, it seems that in some situations the maverick will UNCAGE itself, which can lead to the seeker head pointing nowhere near where you want. I've found that generally the best procedure is to keep it CAGED until the nose of the jet is near the target, then I UNCAGE and slew.
    
    
   
4. If you have have a waypoint designated (using WPDSG on the HSI) then the maverick triangle will stay pointing at the designator diamond when UNCAGED, and you will be unable to slew it around. When CAGED it will of course point near the nose of the jet. In order to slew away from the designated waypoint you'll need to undesignate the waypoint (with the NWS/Undesignate button).
    
    
   
5. To actually do the slew you need to hold down the TDC depress whilst you are slewing. This is the same button you use to lock radar contacts. If you don't hold TDC depress the seeker won't slew anywhere.
    
    
   
6. Additionally I have found the maverick slew does not work properly with the Warthog Throttle TDC nipple: it will only slew along the diagonals. The TDC cursor does work properly in other contexts (Radar and HUD slew) and so this is presumably a bug. Using a 4 way hat for the slew does work okay.
    
    
   
7. Lastly even once you've got it to slew the seeker okay it can be fiddly to get the maverick to actually lock. You need to be close enough and you need to have a good contrast. This is probably not a bug and is likely simulating something close to real maverick behaviour.
   

 

It's complicated enough that I actually have a little checklist that I run through in my head before using mavericks.

 

I still cant get auto pilot to engage

 

I find the BARO autopilot is extremely finicky. You have to get the plane absolutely level before engaging it, and even then you might have to jiggle the FPM above and below the horizon a few times to get it to stick. Otherwise it can get itself stuck in this weird mode where it is sort of doing a BARO hold .. except it will continuously lose or gain altitude. I think it is fair to say that it is buggy.

Edited January 2, 2019 by Tomsk

[Eaglewings]

Autopilot engagement is working as intended here. No issue at all with Barometric, heading and altitude functionalities.

 

It is recommended to set some measure of deadzone on most hotas setup. Did not have to do these for my warthog flightstick.

 

Might want to set a deadzone of 3-5 on your pitch and roll axis and see how it goes.

[Ramsay]

I still cant get auto pilot to engage

 

Autopilot engagement is working as intended here. No issue at all with Barometric, heading and altitude functionalities.

I've found the Barometric autopilot harder to engage in Open Beta 2.5.4 but the HUD climb rate is bugged (x2 standby VVI/real value), so perhaps is also effecting the autopilot.

 

Attitude and heading engagement hasn't changed as far as I can tell, YMMV.