Maverick Issue
-
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. -
Think this bug is not tied at all to the TGP , I was in harrier+ (also other planes) no TGP ,… FCR(STP)->WPN and maverick allways ‘jumps’ near boresight on first slew. … circle starts near boresight, like it is not FCR tied at all when made SOI just on first slew.
So, WPN is already SOI, but is reset , (bugged) on first slew.Cycling master mode AG->NAV->AG , resets SOI back to fcr and WPN is again re-slaved to SOI(FCR). So , error is somewhere (for AGM65 only?! ) in initial slew SOI as WPN, is reset to X,Y (boresight?).
–also, for another thing but related to weapon of choice, … in AF it was possible when GM/GMT bugged target , and second mfd was WPN, … SOI was auto-transferred to WPN , for refinement and vis-lock.
(and stayed there until manual commanded different)
So is it possible in BMS also, similar behavior… this manual switch between FCR/TGP<>WPN is kinda ‘old-school’ -
Hi.
There seem to be two or even three separate jump-bugs,
which render the Maverick pretty much useless for every other procedure than the new TGP handoff.
Here is what I found:I. Big jump bug with FCR
Setting: FCR on left MFD, WPN on right MFD (with powered, uncapped Maverick)
Steps to reproduce:
1. A-G mastermode -> SOI: FCR
2. move cursor -> Mav. view moves in sync
3. lock something up on FCR -> SOI: WPN
4. move cursor -> !Big jump, Mav. view seems to jump to boresight!II. Little jump bug with TGP
Setting: TGP on left MFD, WPN on right MFD (with powered, uncapped Maverick)
Steps to reproduce:
1. A-G mastermode -> SOI: TGP
2. move cursor -> Mav. view moves in sync
3. switch SOI -> SOI: WPN
4. move cursor -> !Mav. view jumps upwards!
5. switch SOI -> SOI: TGP
6. move cursor -> Mav. view jumps back, is synced again
7. switch SOI -> SOI: WPN
8. move cursor -> this time no jump (some wrong initialization when A-G mode is set?)III. Little jump bug with FCR
Setting: FCR on left MFD, WPN on right MFD (with powered, uncapped Maverick)
Steps to reproduce:
1. A-G mastermode -> SOI: FCR
2. move cursor -> Mav. view moves in sync
3. switch SOI -> SOI: WPN
4. move cursor -> !Mav. view jumps upwards!
5. switch SOI -> SOI: FCR
6. move cursor -> !Mav. view does not move at all (not synced with FCR anymore)!
7. switch SOI -> SOI: WPN
8. move cursor -> Mav. view continues to move on its own (impossible to sync with FCR again)Hope this helps in tracking down the bug(s).
I’d really look forward to good old Maverick deployment with the FCR in Falcon BMS -
–also, for another thing but related to weapon of choice, … in AF it was possible when GM/GMT bugged target , and second mfd was WPN, … SOI was auto-transferred to WPN , for refinement and vis-lock.
(and stayed there until manual commanded different)
So is it possible in BMS also, similar behavior… this manual switch between FCR/TGP<>WPN is kinda ‘old-school’IIRC TMS-UP on the GM/GMT to lock a target WILL move SOI to the WPN page. Manual SOI management is only necessary if you aren’t locking anything but still want to move to WPN.
TBH I don’t quite remember what was EXACTLY with old-style Mavericks (i.e before the last over haul and SPI implementation). But 1 thing I can assure you:
This Maverick behavior is as closest to real as possible, otherwise I would have heard some negative feedback about something in the implementationRegarding the jump, again this isn’t forgotten and I will take care of it when the time for that comes, I can’t promise when though.
-
Thank you Hawk!
-
Hi.
There seem to be two or even three separate jump-bugs,
which render the Maverick pretty much useless for every other procedure than the new TGP handoff.
Here is what I found:I. Big jump bug with FCR
Setting: FCR on left MFD, WPN on right MFD (with powered, uncapped Maverick)
Steps to reproduce:
1. A-G mastermode -> SOI: FCR
2. move cursor -> Mav. view moves in sync
3. lock something up on FCR -> SOI: WPN
4. move cursor -> !Big jump, Mav. view seems to jump to boresight!Yes! Thank you for coming up with good repro steps for this. This is exactly the problem I’m facing in my 1989 Korea campaign where I don’t have access to a TGP. It drives me crazy. Glad to see that it’s a known issue. Hopefully it’ll fixed in a future patch. I’ve been using VIS mode in the meantime, which isn’t ideal in some circumstances.
This may be related, but I also notice that when I get that jump bug, it seems like it sometimes takes a long time for the keyhole cross to become solid. It’s inconsistent. Sometimes it happens within 5 seconds, which is normal, other times it can take up to 30 seconds and I’m practically over the target at that point. I wonder if these might be related issues. (Or maybe not issues at all?) When I use VIS and BORE mode, the cross goes solid usually within a few seconds.
-
Exactly!
YetAnotherViper, you’re spot on.
This is the same thing I experienced. I’ve been mostly playing the “other” combat simulator for quite a while, and I decided to give BMS a try this weekend.
I was literaly blown away by all the details in the simulation; I was f*ck#ng loving it; didn’t mind at all about the graphics quality (which is quite good by the way), but then I stumbled upon this nasty “jump” with the mavericks (specially when usin the FCR alone, no TGP).
Went through all the documentation (as I figured I was doing something wrong)…asked google…no joy…and today I did a search here and voila! So it was not me after all
I hope it gets fixed soon; it’s quite annoying (though it seems to get minimized when using the TGP and correctly boresighting the mavs).
Aside from this particular glitch, BMS simply rocks. Keep it up guys!
-
Couldnt find any Bug Report about it so i write it now, maybe devs will take a look at it:
Currently if you want to use the Maverick via the WPN Screen, the Camera jumps on first slew of the Cursor.
Sometimes you have a hard time to find your target again.
No matter if you Boresight or if you lock anything via TGP or FCR.You dont need any special Mission to reproduce, just put some Mavs on and try to use them with the WPN Screen and not TGP.
I dont think that behaviour is as intentend, right?
The Thread where others also discovered the Problem:
https://www.benchmarksims.org/forum/showthread.php?29601-Problem-fine-tuning-mav-slewI don’t mean to make trouble and refute more capable players, but I just did (2019 FEB 17th) the training mission with Mavs (D & G) in BMS 4.33(?) and the Mav seeker head behaved nicely in boresighting at the DD at SP4, and again when doing the handoff from TGP to WPN(Mav D) for that ZSU-23-4 to the west (left) end of the convoy.
I did use DSB1/2* tho, don’t know if that matters. The training literature for the mission didn’t mention resolution for the FCR, but I naturally did DSB1 & 2 only because I “cheated” after boresighting the DD at SP 4 and jumped to SP 7 and cut corners so I started looking for the ZSUs from beyond 20nm out.
Also, this was the mission with CAVOK, not the same mission in the soup.
Again, not making trouble, just saying I didn’t see any misbehaving D-verisons. (Never got around to using the G, wife came home so I had to shut down).- proceedure used:
FCR to acquire in a general sense. I do NOT “lock” with FCR.
Switch to TGP.
Lock with TGP.
target handoff to WPN.
- proceedure used:
-
-
I have an idea!
Lets start a new poll-vote, “Who in here has seen real Viper MFD’s while delivering Mavericks” ! Training TGM’s will do fine too. Preferably beyond Viper Block 4x.
-
I am having the same issue as most people. Attempting to use Mavs without TGP is a lottery. I find the TGP hand-off process to be really cumbersome so it would be great if FCR/WPN alone could be used reliably. Whatever bug came up between 4.32 and 4.33 is surely related to these changes?
-
I am having the same issue as most people. Attempting to use Mavs without TGP is a lottery. I find the TGP hand-off process to be really cumbersome so it would be great if FCR/WPN alone could be used reliably. Whatever bug came up between 4.32 and 4.33 is surely related to these changes?
Nope. I get 90% pk just using mav camera/seeker. The only thing TGP handoff does is extend your visual target ID range and acuity. You’re not flying the correct parameters; it’s not easy IRL either.
-
“cumbersome” … so with the TGP you can positively identify your selected targets, pick out the highest value targets from a group or column and declare them, in TV mode x4, at something like +20nm, hand it off at around 15nm select another specific target hand that off then cruse into about 12 to 10nm and fire both MAVs off within a couple of seconds and turn out secure in the knowledge that, if you did not have a flashing cross, you will hit the two targets you specifically selected.
I will take cumbersome over the old method any day of the week !!!
To use your own words if you find the TGP Hand off process “a lottery” and “cumbersome” you just aint doin it right !!!
-
Also, the TGP method certainly helps as Ironman states; however, I Don’t like to be a slave to it; what if your TGP malfunctions or is not loaded onto the jet or your squadron just doesn’t have any. Old school baby.
-
To use your own words if you find the TGP Hand off process “a lottery” and “cumbersome” you just aint doin it right !!!
So what’s the right way?
-
So what’s the right way?
BMS\Docs\Checklists & Cockpit Diagrams\F-16 Checklists*Weapons Checklists.pdf* → start from pp. 5
The checklist gives you all the necessary steps. It just works if you follow it. Please note that the Maverick cannot get the handoff outside 15 NM (someone please correct me if I remember wrong). Note also that AGM-65A’s or -B’s cannot be boresighted.
-
BMS\Docs\Checklists & Cockpit Diagrams\F-16 Checklists*Weapons Checklists.pdf* → start from pp. 5
The checklist gives you all the necessary steps. It just works if you follow it. Please note that the Maverick cannot get the handoff outside 15 NM (someone please correct me if I remember wrong). Note also that AGM-65A’s or -B’s cannot be boresighted.
Cool, thanks!
-