Jump to content

[CANNOT REPRODUCE, PLEASE PROVIDE A TRACK] MAVF Not Working with TPOD


Recommended Posts

Posted

My issue is I have the TPOD locked on the target in PTRK and designated. I hand it off to my MAVF. The MAVF automatically uncages and points to the target and locks on. "IN RNG" is in the HUD, but the crossout on the "MAVF" in the HUD never goes away and so I can't fire.

 

 

Anyone know what's wrong?

 

 

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted
My issue is I have the TPOD locked on the target in PTRK and designated. I hand it off to my MAVF. The MAVF automatically uncages and points to the target and locks on. "IN RNG" is in the HUD, but the crossout on the "MAVF" in the HUD never goes away and so I can't fire.

 

 

Anyone know what's wrong?

 

 

v6,

boNes

Just to be sure, did you make sure master arm is set to armed?

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

Posted

Yes on both counts

 

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted
My issue is I have the TPOD locked on the target in PTRK and designated. I hand it off to my MAVF. The MAVF automatically uncages and points to the target and locks on. "IN RNG" is in the HUD, but the crossout on the "MAVF" in the HUD never goes away and so I can't fire.

 

 

Anyone know what's wrong?

 

 

v6,

boNes

 

Something is definitely not right.

 

Locking the moving target with Tpod is not a problem (in spite of inability to move PTRK bracket and let it re-lock if needed. Well, they have the docs...)

You're absolutely right about MavF not locking on it properly. I only had time to do one quick test and gonna follow up tonight but so far the MavF was way off (in FLIR or CCD) from where Tpod was locked onto. I'm certain anyone can reproduce this.

 

My targets were T80's. Very clear contrast and heat sig.

Posted (edited)
My issue is I have the TPOD locked on the target in PTRK and designated. I hand it off to my MAVF. The MAVF automatically uncages and points to the target and locks on. "IN RNG" is in the HUD, but the crossout on the "MAVF" in the HUD never goes away and so I can't fire.

 

 

Anyone know what's wrong?

 

 

v6,

boNes

 

 

 

 

 

 

 

Hey Bones!

 

 

EDIT: The stuff I wrote below was my experience PRE-UPDATE. I just flew a quick mission and ALL IS WELL with MAVF and TPOD. I could designate with TPOD, switch to MAV seeker video and get a perfect lock with no X through the MAV.. BONES... make sure you are DESIGNATING with the TPOD (TDC DEPRESS) not just getting a POINT TRACK. That won't SLAVE the Maverick to the point the TPOD is pointing at. IT WILL WORK FOR LASER MAVS because that is the spot the LASER is firing at.

 

 

Known BUG... Apparently some conflict between 2 Sensors trying to lock the same target. here is what works for me:

 

 

1) Sometimes you see the crossed out MAVF flicker.. If you hit the PICKLE button while it is temporarily uncrossed out it will fire.

 

 

2) More reliable method: Hit UNDESIGNATE. It will undesignate the TPOD and let the Maverick Lock on by itself. SOMETIMES, however lock will jump to a different Target.

 

 

3)SOMETIMES WORKS: WIth TDC on the MAVERICK, HIT the TDC DEPRESS (DESIGNATE) and slew the seeker slightly. Often the Maverick will find it's lock..

 

 

 

 

Have a look at this thread in the BUGS forum..

 

 

https://forums.eagle.ru/showthread.php?t=253903&highlight=mavf

Edited by Recluse
Posted
Something is definitely not right.

 

Locking the moving target with Tpod is not a problem (in spite of inability to move PTRK bracket and let it re-lock if needed. Well, they have the docs...)

You're absolutely right about MavF not locking on it properly. I only had time to do one quick test and gonna follow up tonight but so far the MavF was way off (in FLIR or CCD) from where Tpod was locked onto. I'm certain anyone can reproduce this.

 

My targets were T80's. Very clear contrast and heat sig.

 

 

Hey Gripes,

 

 

Did you DESIGNATE the FLIR target (TDC DEPRESS) first? This should slave the MAV seeker. I have to go back and see if JUST doing a AREA or POINT TRACK without a DESIGNATION will do the same, but out of Habit I always DESIGNATE when SLEWING to a target. When using WPDESIGNATE or VVSLV, it is already DESIGNATED, but I typically use VVSLV or WPDESIGNATE to get somewhere CLOSE and then SLEW over to my desired Target and RE-DESIGNATE.

 

 

Note also if you are trying to WPDESIGNATE on a WP where the elevation is wrong (like the default 6562 ft) your FLIR will point up in the sky not at the ground.

Posted
Hey Gripes,

 

 

Did you DESIGNATE the FLIR target (TDC DEPRESS) first? This should slave the MAV seeker. I have to go back and see if JUST doing a AREA or POINT TRACK without a DESIGNATION will do the same, but out of Habit I always DESIGNATE when SLEWING to a target. When using WPDESIGNATE or VVSLV, it is already DESIGNATED, but I typically use VVSLV or WPDESIGNATE to get somewhere CLOSE and then SLEW over to my desired Target and RE-DESIGNATE.

 

 

Note also if you are trying to WPDESIGNATE on a WP where the elevation is wrong (like the default 6562 ft) your FLIR will point up in the sky not at the ground.

 

Before the last update it was working great. I was getting too cocky after being able to smoke 4 stationary or moving targets in one pass.;)

I agree with what you advised bonesvf103 with respect to sending the MavF when the firing solution comes on and off momentarily but that worked before this update, at least for me.

 

Now, it's a different ballgame. I'm gonna tinker with it some more tonight.

And yes, I did designate the moving target and the MavF reacted but did not lock on it. It looked like it acquired the 'spot where the target was at the moment of designation but did not track. The Tpod was tracking with no issues.

I'll put it through the wringer later.

Posted
Before the last update it was working great. I was getting too cocky after being able to smoke 4 stationary or moving targets in one pass.;)

I agree with what you advised bonesvf103 with respect to sending the MavF when the firing solution comes on and off momentarily but that worked before this update, at least for me.

 

Now, it's a different ballgame. I'm gonna tinker with it some more tonight.

And yes, I did designate the moving target and the MavF reacted but did not lock on it. It looked like it acquired the 'spot where the target was at the moment of designation but did not track. The Tpod was tracking with no issues.

I'll put it through the wringer later.

 

 

OK.. I realized after re-reading that you were trying to track a moving target. This is something I have not tried. Wags demonstrated point tracking a moving target with the TPOD in the latest video.

 

 

Just now, it seemed that MAVF is working great for Stationary targets acquired with the TPOD. I have seen threads that LASER MAVS were broken, but they are also working fine for me, especially using AUTO-LASE.

Posted (edited)
OK.. I realized after re-reading that you were trying to track a moving target. This is something I have not tried. Wags demonstrated point tracking a moving target with the TPOD in the latest video.

 

 

Just now, it seemed that MAVF is working great for Stationary targets acquired with the TPOD. I have seen threads that LASER MAVS were broken, but they are also working fine for me, especially using AUTO-LASE.

 

Just did a quick test with the same target setup - 4 T80's moving at default 11 miles/h.

I was able to finally get the MavF to cooperate... just barely. Tpod was tracking great.

The Mav uncaged and acquired the target momentarily then let go of it. After numerous TDC presses On the Tpod designation, the Mav finally stayed on it long enough for me to 'rifle'... one!

 

This happened at 3.5nm from target (it was blasting at me already and knocked out my L gen.)

I hope this has something to do with my mech. and not the way ED has 'envisioned' it for us:noexpression: If that's the case, I'm sticking to Mark 83's and 84's. JDAM's and JSOW's seem to be working fine too.

 

I haven't seen any issues with Lmavs yet. Worked fine in Auto lase and manual. I had to assign a button on my WH throttle base to quickly deal with LTD/R tripping off. I only tested the Lmavs on stationary targets.

Edited by Gripes323
Posted
I tried Lmavs on moving targets and they worked fine.

 

 

 

 

I was mixing up my forums :) People were complaining about LMAVS in the AV-8B not the Hornet. I tried them out in the AV-8B just now, and they worked FINE for me...

Posted

OK, so I changed FOV to narrow before locking it on. On this run, I tracked with the TPOD with PTRK. The TPOD followed the target as it moved and the MAVF uncaged automatically and slewed to the target. I switched to the MAVF MFD and attempted to launch when it was in range. THere was the X on MAVF in the HUD and it did not launch.

 

 

Now, I think I have done it before without designating with the TPOD after PTRKing it. But this was before the update. So maybe the update changed things? I am enroute to try it again this time with TPOD designation.

 

 

AND RECLUSE! Let's fly sometime for old time's sake! Email me, my address is still the same. Me and the guys I fly with will be flying tonight.

 

 

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted

THAT did it!

 

 

PTRKing is not enough. You also have to designate with the TPOD.

 

 

Or alternatively, just use the Maverick stand alone.

 

 

Thanks!

 

 

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted

Now, did anyone notice that if you choose MAVF standalone and your TPOD is on in the other MFD, that you can't slew the MAVF around, even if there is no designated target? I think the only way I was able to do so was to put the TPOD into standby or off.

 

 

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted (edited)
Now, did anyone notice that if you choose MAVF standalone and your TPOD is on in the other MFD, that you can't slew the MAVF around, even if there is no designated target? I think the only way I was able to do so was to put the TPOD into standby or off.

 

 

v6,

boNes

 

 

 

 

You ought be be able to SLEW the MAVERICK independently if you have the TDC diamond in the MAV display. To SLEW MAV, you need to hold down TDC DEPRESS as well. BUT I will try it and see if THEORY and PRACTICE match up in this case..

 

 

EDIT: Just tried it. TPOD in RIGHT DDI MAVF in LEFT DDI. TPOD was in SNOWPLOW, no target designated. SCS LEFT to MAVF, HOLD TDC DEPRESS, SLEW ONTO TARGET, LET UP ON TDC DEPRESS.. LOCK.. FIRE.. HIT..

Edited by Recluse
Posted

 

 

AND RECLUSE! Let's fly sometime for old time's sake! Email me, my address is still the same. Me and the guys I fly with will be flying tonight.

 

 

v6,

boNes

 

 

Yeah! Lets fly. I get together from time to time with some other folks on SIMHQ to fly the HORNET. Haven't seen you around. Do you guys use the SIMHQ Teamspeak server or go elsewhere?? I'll email you!

Posted

So far the main issue for me is Mav F's seeker. The range at which I could get a steady lock on a moving target was between 4 and 2 nm. At 4nm I had to keep re-designating multiple times before I got a steady lock.

Before the update I had a Tpod lock on a mover at 15 ~ 18 nm when zoomed in. The Mav F was able to aquire at 8 or 7nm. Even at 6nm was no reason to whine.

  • Recently Browsing   0 members

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