Jump to content

[ALREADY REPORTED]MAV+TPOD doesn't work against moving target


Recommended Posts

Posted

MAV is constantly slewed to the initial position desginated by TGP, even if uncaged. There's no handoff. If it happens to lock the target and the target moves, it will fight for a while, switching between ground designation and target tracking several times per second, and eventually it will loose the target.

 

The only way to stop this is to undesignate and loose TPOD track.

 

In the attached track you will see that after locking the first vehicle in the convoy, MAV will constantly jitter and switch targets, until the whole convoy passes through the initial designation point.

MAVPTRK.trk

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

  • ED Team
Posted

Hi

 

This is already reported, the jittery lock will be looked at by the team, however I want to mention you are trying to get a lock to far out, at maximum range it will be more difficult.

 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)

Locking distance is not the subject of this report.

 

The problem is Mav can't follow a moving target once locked, because it's constantly forced to look at the point designated by TGP. No matter if it locked at 5 or 10 nm. This creates the "jittery" lock effect.

Same happens when the target is not moving, but the TGP designation is not right on top of the target.

Edited by some1

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted
Locking distance is not the subject of this report.

 

The problem is Mav can't follow a moving target once locked, because it's constantly forced to look at the point designated by TGP. No matter if it locked at 5 or 10 nm. This creates the "jittery" lock effect.

Same happens when the target is not moving, but the TGP designation is not right on top of the target.

 

Just in case they are looking at the wrong issue...

 

  • Recently Browsing   0 members

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