Mark points and Mavericks?

[-Ice]

Hi guys! I seem to remember a discussion about using mark points to setup a Maverick attack but I cannot seem to do the technique. I've not been able to search the threads either. Can anyone help?

 

IIRC, the technique was to lock up each target, mark, then switch CDU/EGI to MARK and then cycle each mark point, slave Mav to mark point, then fire. My problem is basically my mark point is not where my TGP is pointed at, but where my aircraft is at :helpsmilie:

[Chrisakky]

Tried firing the laser while marking?

Edited April 16, 2011 by Chrisakky

[EtherealN]

TGP as SOI and set what it's pointing at as SPI?

[roob]

http://www.youtube.com/watch?v=25MgpCEe114

 

I myself haven't really learned how to master mark-cycling and controlling yet... but the video shows how to do it for one anyhow.

 

 

A clip focusing on markpoints and the laser.

[asparagin]

My problem is basically my mark point is not where my TGP is pointed at, but where my aircraft is at :helpsmilie:

 

That means you are creating overhead marks. You should use TMS-right for marking.

 

After you create your markpoints, you must change steerpt to "mark".

Make markpoint 1 SPI, slave mav to SPI: China Fwd long, lock, fire.

Change to mark 2 and repeat.

[-Ice]

asparagin, thanks for that. I guess that's what I'm doing wrong. Will try again.

[-Ice]

A question for TM Warthog users --- have you mapped your UFC Steer switch to your hotas? I find it hard having to set HUD as SOI to change mark points, and using the mouse to click the UFC Steer switch is a bit cumbersome as well.

 

Or is there a way to cycle mark points outside of setting the HUD as SOI?

[MTFDarkEagle]

You could use another switch (the paddle, mic push/up or something) as modifier, and set modifier+DMSup/short for UFC steer switch.

[159th_Viper]

have you mapped your UFC Steer switch to your hotas?

 

Mapped to my UPARROW and DARROW keys respectively on the keyboard - Much easier.

[-Ice]

MTFD, won't that mean I'll have to use TARGET software to set modifiers? Or are you talking about in-game modifiers?

[MTFDarkEagle]

No: just ingame modifiers.

If you go into your controls section, at the bottom left, you can see "modifiers". Click it, and you should be able to assign a new modifier there. Use any available control there (paddle, mic up/push, slew push), and you can use that just as any other modifier (i.e. alt, shift etc).

[-Ice]

I see... but I'm running out of buttons on my Warthog... maybe the Mic IN switch?

[StrongHarm]

You can simplify that method. Don't use China FWD Long.. that slaves to SPI. Use China AFT Long, that slaves to steerpoint so you can page through steerpoints and have your mav (or TGP) autoslew to them. So your method is:

 

• Create some MarkPoints

• Change to MARK for Stpt on AAP

• China AFT Long to slave TGP to steerpoint

 

You can now change markpoints and your TGP will autoslew to each one. If you have your Mav slaved to TGP, your Mav will autoslew with your markpoints as a result.

 

HOWEVER.. if your targets are in the same general area, there's no reason to use markpoints to slew your mav. Read more about it HERE.

 

That means you are creating overhead marks. You should use TMS-right for marking.

 

After you create your markpoints, you must change steerpt to "mark".

Make markpoint 1 SPI, slave mav to SPI: China Fwd long, lock, fire.

Change to mark 2 and repeat.

[-Ice]

SH, correct me if I'm wrong, but if you China AFT Long, the Mav will be looking at the mark point, but you'll have to do so again to get the TGP looking at the same, yes?

 

ie, looking at Mark A via Mav, then fire a missile, then look at Mark B via Mav, but want to confirm with a TGP look, when you switch to TGP, you'll have to China AFT Long again, yes?

[StrongHarm]

True. The MAV won't move with the markpoints, but the TGP will. So you have to slave the MAV to TGP. Firing on one group, there's no need to use seperate marks if you follow the steps in the link above. However, if you want to aquire and engage groupA at markA, and then groupB at markB, it's necessary to switch back to the TGP after you're done with groupA so you can chinaAFT to slave to markB, then slave Mav to TGP to engage groupB with Mavs.

[zamboni]

True. The MAV won't move with the markpoints, but the TGP will. So you have to slave the MAV to TGP. Firing on one group, there's no need to use seperate marks if you follow the steps in the link above. However, if you want to aquire and engage groupA at markA, and then groupB at markB, it's necessary to switch back to the TGP after you're done with groupA so you can chinaAFT to slave to markB, then slave Mav to TGP to engage groupB with Mavs.

 

Hopefully they will get that fixed in the next patch :)

[StrongHarm]

It's not a bug. Once you fire the mav, the missile where the mark data resides is destroyed with your target.

 

To clarify, you can make a mark, slave the TGP to the mark, slave the mav to the TGP, then move through the marks and watch your mav seeker head track each mark as you cycle through them. After you fire that maverick though, you must reslave the missile that is now active to the TGP.

[zamboni]

Guess I need to clarify also (or need a clarification on what is a bug or not) :)

 

From what I gather right now the "Slave all" functionality is kinda broken.

 

If you create the markpoints, switch to Mark on the AAP and then Slave all to steerpoint, it should (sans bug) slave the TGP and the Mav seeker to the markpoint. Shouldn't you be able to (without the bug) to just change the markpoint with the Mav seeker head switching to the next mark point without having to go back to the TGP?

[Frederf]

With the TGP it will cycle with the active SPI is still in slave mode. You'd think the Mav would do the same thing though. For example you can make TDC SPI and slew the Mav around slaved to the TDC by slewing the TDC.

 

If Mav follows TDC-SPI why not follow STPT-SPI?

[nomdeplume]

Mavericks do follow SPTP-SPI as far as I can tell. I just did a test and it worked exactly as expected - its seeker will follow your SPI, whatever your SPI is.

 

Whenever you slew a sensor, you break the link if it's slaved to the SPI. This also applies to locking a target with the Maverick - which makes sense if you think about it. So, china-hat-fwd-long will slave everything to the SPI, and if the SPI is set to STPT, then cycling steerpoints will cause the Maverick seeker to slew to the active STPT.

 

The moment you either slew the Maverick seeker or command it to track a target, you break that slaving. The Maverick seeker will no longer follow the SPI, since it's been given an independent command.

 

Since you can't fire the Maverick without tracking a target, you'll need to china-hat-fwd-long after firing the missile in order to re-slave the Mav sensor to the SPI.

 

And to clarify some of the discussion above, china-hat-aft-long slaves the TGP to the STPT, and no other sensor.

[zamboni]

Mavericks do follow SPTP-SPI as far as I can tell. I just did a test and it worked exactly as expected - its seeker will follow your SPI, whatever your SPI is.

 

Whenever you slew a sensor, you break the link if it's slaved to the SPI. This also applies to locking a target with the Maverick - which makes sense if you think about it. So, china-hat-fwd-long will slave everything to the SPI, and if the SPI is set to STPT, then cycling steerpoints will cause the Maverick seeker to slew to the active STPT.

 

The moment you either slew the Maverick seeker or command it to track a target, you break that slaving. The Maverick seeker will no longer follow the SPI, since it's been given an independent command.

 

Since you can't fire the Maverick without tracking a target, you'll need to china-hat-fwd-long after firing the missile in order to re-slave the Mav sensor to the SPI.

 

And to clarify some of the discussion above, china-hat-aft-long slaves the TGP to the STPT, and no other sensor.

 

 

You're absolutely right. Sorry for adding unnecessary confusion. (My mistake was thinking China Hat Aft Long was "Slave All to Steerpoint"...it only slaves the TGP).

 

I just went through and did a test of things and what nomedeplume said was correct on all counts.

[StrongHarm]

To reiterate; you must China AFT Long to slave TGP to steerpoint, then slave Mav to TGP, before you can cycle marks and watch your mav autoslew. Such a helpful community :)

[nomdeplume]

You don't need to slave the Maverick to the TGP at all. You need to use 'china hat fwd long' to slew all sensors to the current SPI. That's all. If your SPI is set to STPT, then when you cycle through them the Maverick (and everything else) will automatically slew to it.

 

Your way does work of course, but it adds an extra layer of indirection which can be helpful (if you want to e.g. use the TGP to fine-tune the target point rather than the Maverick sensor) but it's not necessary for the task of 'make the maverick sensor point to the steerpoint'.

[StrongHarm]

nomdeplume go into DCS and use china hat fwd long to slave all to SPI, then try to cycle steerpoints and see if your TGP slews to the steerpoints you cycle.

 

You want to slave TGP to Steerpoint first.. not slave all to SPI.. to acheive autoslew to cycled steerpoints.

Edited April 28, 2011 by StrongHarm

[nomdeplume]

The question was about Mavericks, which is what I did test before I wrote that post (although I was sure it'd work, I'm never sure enough until I do it myself :D).

 

I'm not sure about the TGP cycling to steerpoints when you have all slaved to the SPI and the SPI is set to steerpoint. I think it ought to, and I can't think of any reason it wouldn't, but again, unless I actually see it for myself immediately I'm not going to state that it does.