KnightHawk75
Posts: 1450
Joined: 11/15/2018 Status: offline
|
quote:
ORIGINAL: SeaQueen As cool as this idea is, I'm not sure it's really possible to do without violating your user agreement. The best thing to do is put in a DB request for a hypothetical platform. B-1s with forward firing ordnance is awesome though. I strongly encourage this addition. Huh? How is it against said agreement? Also the newer b-1b in the db have air-air fcr already apg-83 sabr-gs aesa local u = SE_GetUnit({guid='UNITGUIDHERE'}) local arcT={'PB1','PB2','SB1','SB2','SMF1','SMF2','SMA1','SMA2', 'SS1','SS2','PS1','PS2','PMA1','PMA2','PMF1','PMF2'}; local arcD={'PB1','PB2','SB1','SB2','SMF1','SMF2','SMA1','SMA2', 'SS1','SS2','PS1','PS2','PMA1','PMA2','PMF1','PMF2'}; --remove the arcs you don't actually want applied above does full 360degree arcs. -- ADD APG-77 AESA LPI ScenEdit_UpdateUnit({guid=u.guid,mode='add_sensor',dbid=4477,arc_detect=arcD,arc_track=ArcT}) --## Tomahawk Command Datalink 1600 160ch needed for re-attack\post launch control of lrsm etc ScenEdit_UpdateUnit({guid=u.guid,mode='add_comms',dbid='134'}); --## AIM 120 Command Datalink [two-way offboard] 8 ch? [act like e2-d remote control if unit also cec comms] ScenEdit_UpdateUnit({guid=u.guid,mode='add_comms',dbid='317'}); --## Standard version of AIM 120 Command Datalink [two-way] --ScenEdit_UpdateUnit({guid=tostring(myunit.guid),mode='add_comms',dbid='294'}); Also attached a script to do it all (create the unit, add a clean vls mounts,sensor,comms,weapons) result is mythical b-1b with aim-260's aim-120d's some aim-9x in addition to it's monster loadout (which should probably be a ferry loadout when doing this but whatever..) b1-custombomber.txt attached.
Attachment (1)
|