Jump to content

Recommended Posts

Has anyone else noticed this behaviour from the Lightning pod? Sometimes when turn into a target, the t-pod loses lock and wobbles off to one side as I roll back to wings level. It then stabilises on the wrong piece of real estate and I have to re-aquire the target before I can make it go boom.

Is this correct? It seemed to arrive with 2.7

Cheers,

Morat

Link to comment
Share on other sites

I don't know if it's a bug or works that way in R/L, someone like Snoopy could give us the scoop on that.  But, it did this before 2.7, though not as bad.  Basically IIRC it has to do with gimbal limits or terrain masking.  I am in the habit of throwing down a markpoint once I find targets, for quick re-acquisition. The JHMCS is a God-send for this now, too.

  • Like 1
Link to comment
Share on other sites

In my experience, that's what happens, when the TGP is in area or point tracking mode, and you fly high-g maneuvers. I do not know whether this happens with the real TGP as well.

What I do to prevent this: If I have to fly aggressive maneuvers, or fly away from a tracked target, to which I want to return, I put the TGP into the INS mode. This way it preserves the location it is aiming at.

Link to comment
Share on other sites

It's infuriating. Happens all too often in gradual and moderate G-turns. I can't tell you how many rockets and (laser) bombs I've wasted by this nonsense. I can't believe that this would be indicative in real-world TGPs. The pilots I've worked with wouldn't stand for it. Bombs and rockets guided to civilian houses and buildings.

I've tried power cycling the TGP but still no joy.

Link to comment
Share on other sites

Maybe TGP realigning after a gimball limit? If it this to avoid it dont low your nose below your target.

If you are fliying to the target to launch a laser rocket or maverick if your velocity vector is above your target and you point it below the TGP rotates and realign to avoid achieve the gimbal limit, losing the target, if you, then, point you vector above the target it will rotate again

i7 9700K | Corsair Pro Vengeance 32Gb 3200 Mhz | KFA2 GeForce RTX 3080Ti SG | Gigabyte Aorus Z390 Pro | Western Digital SN750 1TB | Samsung 850 Evo 500GB | OCZ ZX 1000W | Asus ROG Shift PG27V | Xiaomi P1 55" | Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | Thrusmaster Warthog Throttle | Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

 

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C Warthog | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | Ka-50 BlackShark II | Mi-24P Hind | SuperCarrier

Link to comment
Share on other sites

28 minutes ago, 5ephir0th said:

Maybe TGP realigning after a gimbal limit? If it this to avoid it don't low your nose below your target.

No, that's not it. I always reset the gimbal to boresight when it's been to the limit for whatever reason. It still happens anyway.

Link to comment
Share on other sites

The behavior in-game is that of TV image tracking problems, not a gimbal limit.  POINT and AREA modes supposedly track the target, not by the targets known position, but by moving the camera to track an area on the TV image by contrast and shape.

 

Video tracking modes only seem to work at certain angles--you can see in other areas when they turn into P-INR and A-INR, the video tracking is presumably off temporarily and turned back on when the camera is in a better angle.

 

The area in question is about 10 degrees wide about 20 degrees down from the boresight cross.  If the camera passes through there, the video tracking algorithms fail for whatever reason.  Unlike to the side and rear, the TGP does not revert to INR mode, again, for whatever reason.

 

Whether this happens in real life, I have never heard any substantial information to confirm it does or does not.


If it DOES, I would suspect it's a failure in the video tracking algorithm near the camera's longitudinal axis.  The algorithm probably tracks the image with simple up/down/left/right commands, but as you get closer to that axis, the left/right commands become less and less accurate, since they tend to spin the camera more than translate left and right.  At some point, the algorithm commands full scale left/right commands and can't keep up, and it gives up in petulance.  This could be avoided by reverting to automatically reverting to INR mode like in other areas, of course.

 

Of course, that's all speculation on my part, but I'm still hoping we'll someday hear someone with RL experience corroborate any of this


Edited by jaylw314
Link to comment
Share on other sites

10 hours ago, King39 said:

No, that's not it. I always reset the gimbal to boresight when it's been to the limit for whatever reason. It still happens anyway.

 

Imagine you fly towards the target which on your -5 degree mark, you boresight your TGP, point it to the target and then you low your nose below the target, TGP will still roll and lose the target due to this and you will see "Gimball roll" momentary on the TGP.

i7 9700K | Corsair Pro Vengeance 32Gb 3200 Mhz | KFA2 GeForce RTX 3080Ti SG | Gigabyte Aorus Z390 Pro | Western Digital SN750 1TB | Samsung 850 Evo 500GB | OCZ ZX 1000W | Asus ROG Shift PG27V | Xiaomi P1 55" | Virpil T-50 CM2 Base + Thrustmaster Warthog Stick | Thrusmaster Warthog Throttle | Thrustmaster MFD | Saitek Combat Rudder Pedals | Oculus Quest 2

 

DCS World | Persian Gulf | Syria | Flaming Cliff 3 | P-51D Mustang | Spitfire LF Mk. IX | Fw-109 A-8 | A-10C Warthog | A-10C II Tank Killer | F/A-18C Hornet | F-14B Tomcat | F-16C Viper | Ka-50 BlackShark II | Mi-24P Hind | SuperCarrier

Link to comment
Share on other sites

1 hour ago, 5ephir0th said:

 

Imagine you fly towards the target which on your -5 degree mark, you boresight your TGP, point it to the target and then you low your nose below the target, TGP will still roll and lose the target due to this and you will see "Gimball roll" momentary on the TGP.

Hi. I m with you. To me it looks like the TGP comes to a point where the tarbet is exactly on the longitudinal axis and it gas to re acomodate, loosing the targt loxk. Again with you, dont turn so hard that the velocity vector is underneath the target position, keep the aricraft nose comfortably above the target, to avoid the TGP to reacomodate.

Saludos. 

Saca111

Link to comment
Share on other sites

I think this is a well modeled limitation of TGPs when in Point or Area track as this modes relies on algorithms to track an object or areas of the ground. In these cases high G or just masking the target for a second can cause a tracking problem.

This is solved by using INS mode that use coordinates. If I recall correctly Wags posted a video about this although I think it was using the Viper (same Litening pod, same limitations)

I'm other modules like the Jf17 IIRC the pod automatically enters INS mode when any masking or high G maneuver occurs.

Enviado desde mi ELE-L29 mediante Tapatalk

Link to comment
Share on other sites

Posted (edited)

I think I'll have to experiment and see if I can get a video of the behaviour.

Thing is, you don't have to be manouvering very hard to put the target above your nose if you're at a relatively low altitude. Even 30 degrees of bank can mean you're moving the target above your wingline (which I guess is the crucial aspect for the pod), especially if you're turning towards the pod. The odd thing, for me, is that the pod tracks just fine as you enter the turn. It's when you roll out that it loses track. At least, that's my impression before testing.

 

If we have any RL Hog pilots, I'd be fascinated to hear their view! 😄

 


Edited by Morat
Link to comment
Share on other sites

40 minutes ago, Morat said:

If we have any RL Hog pilots, I'd be fascinated to hear their view! 😄

I agree with your opinion but as I stated above I seriously doubt this occurs in real life. The chance of a H.E. rocket or (lased) GBU landing on a civilian populous would be far too high to justify the continued (TGP) use with this defect. I suspect this problem is limited (somehow) to the game and it's AI. They (aircrew) just wouldn't stand for it and I know squadron CC's simply wouldn't allow this situation to occur unabated.

Imagine a 2000lbs GBU landing on a Afghani village by mistake (due to this TGP hop)...

My $.02

Link to comment
Share on other sites

27 minutes ago, King39 said:

The chance of a H.E. rocket or (lased) GBU landing on a civilian populous would be far too high to justify the continued (TGP) use with this defect.

 

I don't think I've ever observed the behavior described in this thread, so I can't say anything from personal experience in DCS.

 

However, in real life there are countless procedures and limitations in place to make sure that things don't go wrong. For instance, I've read that IRL pilots would put the TGP MFCD on the same side as the TGP, so when the TGP is hanging on station 2 it's the left MFCD, and station 10 they'll use the right MFCD, just so pilots get an intuitive understanding where the pod is hanging and how it affects masking by the aircraft. We can do this in DCS, no problem at all, but the manual doesn't mention it.

 

So if there's kind of a blind spot within the TGPs normal field of view where no masking occurs, but where the optics rotating back and forth could easily tangle themselves, I wouldn't be surprised if pilots were taught how to fly the aircraft so that this kind of entanglement does not develop into a problem.

 

And as far as I'm aware, the type of ad-hoc LGB attack that we tend to do in DCS isn't the way it's normally done IRL, where controllers on the ground or wingmen could, and often would, provide lasing to allow the attacking jet to get the hell out of dodge and take care of evasive maneuvers during the bomb's fall time.

 

Also, you speak of rockets; if you're referring to laser guided rockets, all of the above applies. But in case you're referring to unguided rockets, pilots really need to acquire the target visually AFAIK. I don't think they'd just rifle on a caret on their HUD, unless in a very permissive environment where friendly fire and collateral damage are of no concern.


Edited by Yurgon
Link to comment
Share on other sites

  • 2 weeks later...

Well, I stand corrected and I apologize ED. The TGP "Hop" as I call it is a real thing.

Look at exactly 1:00 on this video just as he is coming off target...

 

 

Again E.D., my apologies. 

John

Link to comment
Share on other sites

1 hour ago, King39 said:

Well, I stand corrected and I apologize ED. The TGP "Hop" as I call it is a real thing.

Look at exactly 1:00 on this video just as he is coming off target...

 

 

Again E.D., my apologies. 

John

 

Hey, uh, I'm pretty sure that's just a shot from DCS run through some blurring and video filters 🤪

 

Link to comment
Share on other sites

i was able to get a track of this issue. the tgp wandered a couple times.

20210906.zip


Edited by silverdevil
file download hosed

AKA_SilverDevil AKA Forums My YouTube

==============================================================

Go to Heaven for the climate, Hell for the company. Mark Twain

==============================================================

Alienware Aurora R12, 2TB M.2 PCIe SSD, RTX 3090 24GB , i9 11900KF, 128GB Quad Channel DDR4 XMP at 3400MHz, Dell AW3420DW

Link to comment
Share on other sites

  • 2 weeks later...

Since this post appears to have lost interest, how does one get the pod to go back to the original point before the wander? I must move the SPI back to where the targets are... with hope I can find them. TIA.

AKA_SilverDevil AKA Forums My YouTube

==============================================================

Go to Heaven for the climate, Hell for the company. Mark Twain

==============================================================

Alienware Aurora R12, 2TB M.2 PCIe SSD, RTX 3090 24GB , i9 11900KF, 128GB Quad Channel DDR4 XMP at 3400MHz, Dell AW3420DW

Link to comment
Share on other sites

  • 2 weeks later...

Silver,

 

I have gotten into such a habit of making a mark point for just about every target (everything almost) because the TGP so much likes to wander off and at the worst time.  This is from my own experience and from the advice of allot of veterans who have posted.

 

If the TGP wanders off I simply re-set (re-cage to bore) the TGP using the top right button on the right MFCD with the TGP as SOI.  This function I have mapped to my HOTAS.  With the STEER PT switch in Mark I make sure to have the correct mark point for the target I want selected on the HUD.  I then slave the TGP to the steer point using China Hat aft long.  On the MFCD, the TGP gate bars will extend and the TGP changes mode (I believe it is steer point mode, but not positive).  To place in back in for example INR-A I simply slew the TGP slightly. 

 

So... 

 

With two button presses on my HOTAS I can quickly re-set the TGP back on target when it wanders off.  I can do this easily in the middle of an attack run.  Just be careful, because if the TGP is in "steer point mode" the auto lase feature for GBU's will not work.

 

Caldera

DCS World:   P-51D A-10C ii  F/A-18C  Combined Arms F-5  F-16  UH-1H  AH-64

                      Caucasus   Persian Gulf   Normandy   Nevada   Syria

System:        I7-10700F  16GB  RTX-2060  1TB SSD Windows 10  TrackIR 5  Cougar MFD's

HOTAS:         VPC WarBRD Constellation CM3

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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