Jump to content

[REPORTED] AGM65F+TGP locking issue (bug?)


Burner1111

Recommended Posts

  • ED Team

Hey all, I have reported this.

 

The Seeker should slew to the target point when uncaged, but if it doesn't get a lock, such as you are out of range, or just doesn't manage a lock, then it should should move freely, right now it looks like it is trying to continue to slew back to the target point, even when maneuvering, that is what is causing the jitter and the loss of ability to slew it manually.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

Hey all, I have reported this.

 

The Seeker should slew to the target point when uncaged, but if it doesn't get a lock, such as you are out of range, or just doesn't manage a lock, then it should should move freely, right now it looks like it is trying to continue to slew back to the target point, even when maneuvering, that is what is causing the jitter and the loss of ability to slew it manually.

Thanks, NL. Does that also mean that the seeker should stop trying to slew back to the target point if it does manage to get a lock? Because now it keeps trying to do that, even if there's a valid target that it can lock, resulting in it rapidly switching between locked and unlocked states.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

  • ED Team

Yeah, I already got a fix in, and now it's locking immediately on uncage, which means it doesn't properly slew to the target. So it's still being looked at.

 

I believe it should slew to the target point if it's in range, and the seeker gets a good look, then a lock should be possible, otherwise, it fails to lock, and you have to slew to adjust and try and get a lock manually.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

Yeah, I already got a fix in, and now it's locking immediately on uncage, which means it doesn't properly slew to the target. So it's still being looked at.

 

I believe it should slew to the target point if it's in range, and the seeker gets a good look, then a lock should be possible, otherwise, it fails to lock, and you have to slew to adjust and try and get a lock manually.

Yes, there should be logic in place that enables the seeker to attempt a lock AFTER it has slewed to the target point, but not during the transition from boresight to target. I don't have any documented info on that but it's the only thing that makes sense.

 

Look at my previous post https://forums.eagle.ru/showpost.php?p=4090933&postcount=8.

We initially had logic #3, we currently have #1 into the game, the fix you're talking about takes us back to #3 and we'd ideally have #2 or #4, whichever is realistic.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

  • 4 months later...
Hey all, I have reported this.

Latest OB

Also plz take a look at this:

With "realistic TDC slew" unboxed, I can't move MavF seeker (mav uncaged & SOI. TGP locked).

 

With "realistic TDC slew" boxed, I can move MavF seeker (TDC depres & slew at the same time) & lock another target.

 

I imagine the majority use "realistic TDC slew" unboxed.


Edited by CoBlue

i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.

Link to comment
Share on other sites

  • 3 months later...

It happened to me that AGM65-F, since last OB update, is (again) suffering the same issue reported here.

 

When you lock target by using TGP or, most of all, TGP offset, Maverick, in its own DDI, moves back and forth the target and loops into lock/unlock state really quickly, without stabilising. To fire the Mav, you have to quickly continuously press the fire button, hoping to press it while Mav is looping through the lock state. Or, while the Maverick is going back and forth from the target (locking/unlocking), you have to quickly cage/uncage the Mav and, only then, it goes far from the target and then moves back to it in a stable way.

 

When you lock target by using Maverick sensor on its own without TGP aid, instead, all runs well.

 

EDIT: realistic TDC slew here. But the TDC slew method is not part of the issue.


Edited by Saruman
Link to comment
Share on other sites

It happened to me that AGM65-F, since last OB update, is (again) suffering the same issue reported here.

 

When you lock target by using TGP or, most of all, TGP offset, Maverick, in its own DDI, moves back and forth the target and loops into lock/unlock state really quickly, without stabilising. To fire the Mav, you have to quickly continuously press the fire button, hoping to press it while Mav is looping through the lock state. Or, while the Maverick is going back and forth from the target (locking/unlocking), you have to quickly cage/uncage the Mav and, only then, it goes far from the target and then moves back to it in a stable way.

 

When you lock target by using Maverick sensor on its own without TGP aid, instead, all runs well.

 

EDIT: realistic TDC slew here. But the TDC slew method is not part of the issue.

 

 

I have similar behavior, as you can see in the attached video. All is set as it has be (AFAIK) but with the SOI in the left DDI the MAV F doesn't fire at all, and the lock only happens for a milisecond randomly (seems to be related with the AOA).

But, as soon as I put SOI in the right DDI (nothing more), the problem disappears, the lock is achieved and the mav is fired O_O

SOI in Left DDI (mav) --> lock KO

SOI in right DDI (TGP) -->lock OK

 

https://www.dropbox.com/s/wicep9w3q9nuk6k/F18_MAV_bug.mp4?dl=0

 

(track attached also)

f18lasemav.trk

Link to comment
Share on other sites

Hah. Just spent two full hours trying to figure out why I couldn't get a consistent lock from my Laser Mavericks. Looks like I've been hitting the exact same bug that everyone in here's been calling out.

 

Well that was a waste of an evening. :(

i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S

Link to comment
Share on other sites

Hah. Just spent two full hours trying to figure out why I couldn't get a consistent lock from my Laser Mavericks. Looks like I've been hitting the exact same bug that everyone in here's been calling out.

 

Well that was a waste of an evening. :(

Have you tried doing SOI the TGP? For me at least it worked

Link to comment
Share on other sites

Have you tried doing SOI the TGP? For me at least it worked

 

 

Just tried it, and it works perfectly. Thanks for your help, Daemon. :thumbup:

i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S

Link to comment
Share on other sites

  • 2 weeks later...
I couldn't get a consistent lock from my Laser Mavericks.

Can you plz confirm this issue was with the E variant of the Maverick and not the F? I'm Having similar problems with the tgp handoff over to the MAV seeker for the IRMAV. On the handoff the seeker slews to tracked moving target but the crosshair is off a bit never centered on the tracked tgp target?

Nobody likes me because I'm unsafe.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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