Maverick Issue
-
I have the same issue. The Maverick seeker jumps to somewhere, but not where the FCR is locked or where you initially got Mav seeker SOI from the FCR.
Seriously frustrating. I used to be able to ripple 6 mavs in under 10 seconds, but that was before the cross had to not be flashing or alignment needed with the “keyhole”.
Even with the new mav funtionality I’m only get 2 mavs off in a single pass.
-
Thanx for taking that vid, I’m not sure what’s exactly happening but seems like the Maverick eye “jumps” sometimes. I don’t think it’s a big gap over there (seems like you are at the area of the target) but it shouldn’t happen just because of cursor movement. I’ll hopefully try to look at that stuff sometime soon (I got my hands full with other stuff that really demands a LOT of time, so not sure when I’ll be able to check this actually, but I’ll do my best). The other problem, besides free time is that I’ll need a reproducing scenario, cause if I can’t reproduce that by myself, small chances that I can fix…
Even with the new mav funtionality I’m only get 2 mavs off in a single pass.
Weird, I posted a vid up there that shows you how I launch 8 Mavericks in the same pass and still have ~7NM to go until target area. I’ll fairly say that this vid was taken before the Mavericks got their range shorten (to become more realistic) so maybe today you will be able to release all 8 and be at ~4NM from target when the last missile is away, but that’s still a good distance unless you are attacking some SAM system (But then the tactic must be smarter to take the FCRs in first pass from max range and then get back to take the rest).
-
Thanks I-Hawk for taking a closer look.
In this Vid there is a realtive small jump but its quite difficult sometimes to find the target again.
Anyways, if there is something i can do to help you just let me know.
I used a F-16 C52 for this if it helps to reproduce somehow. Never checked if this changes if you use other models. -
I have experienced this as well. I found through a little research that the mav is somehow slaved to the set point your a navigating to so it tries to point the seeker at the set point and not your slaved target. I go to my target set point and then switch to snow plow once I know the general area the enemy targets are located in. Doing that seems to have solved the problem for me anyways.
-
Just testet it and you are right.
If you do Snow Plow, this didnt happen.
OFC finding targets in Snow Plow is kinda difficult but i would consider this as a workaround.@I-Hawk may i ask you to do a test with using maverick from a waypont versus using maverick from snow plow?
In my tests i did a precicion waypoint on a watertower.
initially planned for using it to Boresight without searching for a target. -
OK thanx for more information, I’ll check.
-
A fellow Pilot of my Squadron did also a few tests, which make sense so far…
His conclusion is that as soon as you move the Cursor, the Maverick Camera jumps exactly in the direction of the nose of the Plane.
The Maverick Cam is centered so to say, no matter where it was before.
Which might explain why you didnt experience any glitch when you move from snow plow because then the camera looks allready in that direction.That also explains why there is only a slight glitch in my video. I had a precicion waypoint for easier boresight.
For that reason i flew with autopilot in good weather which means my nose was only slightly off because of the wind conditions. -
Also it is very very important to bore sight your Mavs. If you do not do this your accuracy will be very poor. There are several good tutorials on YouTube
-
Also it is very very important to bore sight your Mavs. If you do not do this your accuracy will be very poor. There are several good tutorials on YouTube
What if you’re not carrying a TGP?
Point being, the Maverick is a weapon that does not require the TGP to function properly. Therefore, boresighting to the TGP should not be necessary to accurately employ mavericks …. except when using the TGP as the sighting device for handoff.
-
Same issue, SP seems to be a workaround, but it doesn’t sound like the whole thing should work like this? No problem if you boresight the mavs to the tgp, but if you don’t and want to use the mavs by only WPN it’s a mess because of cursor jumping as soon as you touch it. Oh, and by the way, everyone in my sqd has the same issue: someone started even thinking it was intended to be this way.
Inviato dal mio Nexus 5 utilizzando Tapatalk
-
Also it is very very important to bore sight your Mavs. If you do not do this your accuracy will be very poor. There are several good tutorials on YouTube
What if you’re not carrying a TGP?
Point being, the Maverick is a weapon that does not require the TGP to function properly. Therefore, boresighting to the TGP should not be necessary to accurately employ mavericks …. except when using the TGP as the sighting device for handoff.
It doesnt matter if boresight or not for this particular topic.
Accuracy stuff is simply another issue.Here we are talking just about the process of using the Maverick on its own and the jump in the camera if you use the cursor.
Please lads, dont hijack my Bug Report for everything related to Mavericks.
If you have some new insights for this particular issue, you are welcome but this is no “how to boresight” or other thread.Sorry but please stay on topic and do that discussions in another part of the forum, maybe in the thread i linked at the first post.
-
someone started even thinking it was intended to be this way.
That’s me!
Well, just for internal use I made this video were I show how to minimize the jump from the second Mav: I use to direct the missile camera as long as I can through the FCR (GMT in this case)
-
nice vid - but my italian is not that great to understand
BUT iI get the picture
possible to have it in english ?
THX for making the vid in the first place.:bdance:
-
I figured out my issue.
If you point the mav seeker where the targets are when the next mav is selected it will be pointing at the targets. So basically point the entire jet at the targets, including pitch down, and you will be able to acquire them in rapid succession.
-
And what about the jump of the cursor?
Inviato dal mio Nexus 5 utilizzando Tapatalk
-
Sounds like there are multiple factors in play here:
- bearing and range to target differential (angle off between target and nose aspect, which affects weapon view acquisition)
- if in or out of keyhole parameters, if not all bets are off for a hit
- bore sighted or not (if TPG available or employed), where if bore sighted the weapon view is slaved to locked on TGP
- if target is tied to a selected target steerpoint or not whilst aspect angle is high
- if SnowPlow mode is used or not to keep the weapon view aligned with the nose of the a/c
The problem seems to be that if the current steerpoint is off bore from the target bearing, and there isn’t another FCR mode or synced SOI or physical alignment of a/c to target; then the Mav’s weapon view will snap to the off bore steer point on its next weapons station.
-
Hey guys thanks for the workarounds, but is there any word yet on if this problem is fixed, or is in the works of getting fixed? Dont mind waiting for it, just dont wanna start developing bad habits on the assumption that its not a priority and wont get fixed in the next 2 falcon weeks thats all. Thx!
-
Yes, please make this a high priority for fixing!
-
Yes I didn’t forgot about this and it is on my list, but honestly I currently have MUCH more important stuff to take care of, so my hands are full with that. The Maverick issue will be handled but I can’t promise it’ll be anytime soon. I already tried to do a quick run over the Mavericks code but couldn’t find any reason for such a jump to happen, so it’s not something that can be fixed fast, so it’ll have to wait.
-
A pity. This is a real usability feature that seriously affects gameplay and should rank high on the priority list imho.
Anyway, you’re doing a great job with BMS and being myself a software dev with open-source contribution experience i appreciate the work done.