Trouble reseting SOI to HUD when engaging with mavericks VIS
-
So I’ve been reading through the Maverick part of the BMS training. Some new stuff with 4.33 to learn I see.
Here’s what I’m having trouble with: DMS up does not reset SOI to HUD for VIS mode. Doing the same in PRE mode to switch from WPN -> FCR works just fine.
How I tested this: In VIS mode, I start with HUD as SOI, TMS up to stabilize near my target, fine tune on the WPN page before finally locking my intended target with TMS up.
Here’s what then goes wrong: Suppose I wish to unlock the target and go back to HUD as SOI. Well, I just TMS down and then DMS up right? TMS down indeed unlocks the target, BUT DMS up does not give the SOI from MFD/WPN -> HUD :P. It’s still on the WPN page as SOI.
Is the process of reverting SOI to HUD for VIS mode different? Is DMS up the wrong input? I could not find anything in the training docs…
NOTE: If I only stabilize and then immediately DMS up again to revert SOI to HUD before moving my cursor at all when WPN is SOI, DMS up does work. But as soon as I move my cursor even the slightest DMS up stops working.
NOTE2: If I enter an override mode (e.g. MRM override) and then back to A2G mastermode, I can stabililze and then reset SOI to HUD again no problem. But as soon as I move the cursor after stabilizing, reseting SOI to HUD with DMS up stops working.
Is it a bug??
NOTE3: My two multiplayer wingmen trying to figure it out (different tms and dms combinations) actually both experienced CTDs here :S…EDIT: Answer found here - TO-BMS1F-16CM-34-1-1.pdf page 157 Seems like a limitation in BMS
[i] Target rejection should be commanded by manually selecting the HUD as the SOI with DMS up and positioning the TMS down. [b][u]Currently you need to switch master mode (for example to MSL OVRD or DGFT) and then back to A-G to return SOI to the HUD.[/u] [/b][/i]
-
Not a bug.
-
depends on your manual
-
Not a bug.
ok - So, what is the correct SOP for moving SOI back from WPN to HUD in VIS mode?
Or if it is something I can read about in one of the manuals, which one should I be looking into?I would be really grateful if I could find any information on the subject really… So I can learn what Im doing wrong
-
from TO-BMS1F-16CM-34-1-1.pdf page 157
[i] Target rejection should be commanded by manually selecting the HUD as the SOI with DMS up and positioning the TMS down. [b][u]Currently you need to switch master mode (for example to MSL OVRD or DGFT) and then back to A-G to return SOI to the HUD.[/u] [/b][/i]
So seems like a limitation in the current BMS version. Is my interpretation correct?
-
Sorry, misunderstood or you can even call it a brain fart.
Moving the SOI to the HUD form the WPN page is not possible in BMS. It is a bug. There is nothing you or your mates are doing wrong.
Apologies.FYI, the whole EO-VIS mode needs a revision, especially when used with the TGP. Currently EO-VIS HANDOFF is not supported.
-
Mavs have definitely come a long way in BMS There is definitely room for future improvements again, though.
-
The discussion of real airplane behavior vs BMS continues but it is not a bug. A bug is software behavior other than intended by the programmer. This behavior is intended.
My understanding of BMS 4.33u1 is that SOI in EO-VIS can be changed freely away and back to HUD until Maverick slave is broken (TDC is designated onto the ground or the Maverick slewed manually). After this has happened the Maverick must be deselected and reselected to reset to the Maverick slaved state.
Note1: Correct as per above.
Note2: If you mean “move the cursor after stabilizing” as move the TDC after designating then correct.
Note3: Reproduction instructions please for CTD.
-
The discussion of real airplane behavior vs BMS continues but it is not a bug. A bug is software behavior other than intended by the programmer. This behavior is intended.
My understanding of BMS 4.33u1 is that SOI in EO-VIS can be changed freely away and back to HUD until Maverick slave is broken (TDC is designated onto the ground or the Maverick slewed manually). After this has happened the Maverick must be deselected and reselected to reset to the Maverick slaved state.
Note1: Correct as per above.
Note2: If you mean “move the cursor after stabilizing” as move the TDC after designating then correct.
Note3: Reproduction instructions please for CTD.
Regarding the CTD - we’ll get back to it if we see it again.
We should really close this thread as it is not a bug but known implementation limitation in the current version of the sim - as answered by both you and the bms manual itself.
-
No need to close it, if anybody else has a question on that he can find it and post here
-
Did test all that stuff here… but I am still not able to get my Mavericks SOI in VIS mode… what the hell I am doing wrong… since 4.33 all my mavs miss the targets and just fly straight ahead… I have good lock, have DLZ, I am within the keyhole and so on… and thos fu…ing missiles do not work anymore
-
…what’s your boresight picture looking like? No boresight, no kill.
-
It sounds like you’re firing without a track. Maverick in VIS won’t let you SOI Maverick in the pre-designate state.
For VIS attacks:
1. Slew the TDC onto the target area.
2. Designate with TMS forward. (SOI WPN automatic)
3. Slew the Maverick over the target.
4. Designate track with TMS forward.How to check if the Maverick is tracking:
A. “BSGT” label is displayed.
B. Tracking crosshairs gate the object.
C. It is not possible to slew the crosshairs away from the object.As always confirm that the range is not more than the maximum and the pointing cross is not flashing before firing.