[CORRECT AS IS] mavericks be already powred on if you start up in the air?

[CrazyGman]

as the above question, also it seems that in pre mode the maverick missle slaves to the steer point, and won't slave to where the targeting pod is looking can't seem to figure out how to slave the maverick to just the targeting pod

[Viking 1-1]

Pre mode with tpod worked fine for me.

 

Maybe check Wags video again to be sure you dont miss anything.

[Frederf]

I don't think so. The missiles have a finite amount of time they can be on before they have to be shut off. The A-10C doesn't start with EO power either.

 

Missile should follow SPI (or SPI plus offset when there are offsets) regardless of how that point is moved around. HUD slewing or FCR slewing or TGP slewing the missile and all the other sensors follow. "Slave the Maverick to just the targeting pod" is not how the F-16 works. The missile follows the notional target direction when slaved. The notional target is SPI plus any offsets (and there are none in DCS so SPI). SPI is determined by the selected sensor which is supplying valid location data.

 

Try the following: EO PRE, left MFD WPN, right MFD TGP. Make HUD SOI and slew. The HUD TD box, TGP LOS, and missile LOS will follow the slews. Then set TGP SOI, TMS right to begin area track and slew again. Again HUD TD box, TGP LOS, and missile LOS respond to slewing.

 

Where this breaks is SP which is not quite right. This master-slave relationship between sensors should persist in SP mode. If SP mode is used and somehow SPI and TGP LOS get separated then a bug has occurred and normal behavior isn't guaranteed. In general commanding area track from TGP SOI seems to be the best way to designate when in SP pre-designate condition.