_SteelFalcon_

Well, does it happen if you remove the mods? If yes, maybe run a dcs repair and try again

if you're close enough, you dont even need to turn in to shoot the HARM. POS EOM will make the HARM turn to the target. and it's quite satisfying watching them go off, up and around PGM2 should be plenty accurate for the HARM to find the target.

Check his screenshot. Yes he did

i'd guess that after the time to pull up (which is not necessary with a 0 degree "loft" angle), the symbology should switch to time to go to release as normal, like a basic CCRP attack.

How is this still marked as correct as is?

Well the evidence is referenced. One just has to look at the correct manual, i‘m pretty sure if i was able to find it, ED surely will too

There is a specific manual that mentions ripple function for the Maverick briefly and all it says in there is that ripple is limited to 2 stations (so let's say mavs on lau-88 on station 3 and 7) so max ripple is 2 missiles, 1 from the left wing, 1 from the right wing. no matter if lau-88 or lau-117 is used. Hint: 1-451 Also, on that same page in said manual, there is specific mention on what the STEP button on the MFD does, and the current implementation is also incorrect in that regard now sadly we're missing the ripple option on the SMS page when lau-88 is loaded. and please, get rid of the correct as is tag, the feature is in the changelog...

oh boy... something went hella wrong. good catch tho!

still doesnt explain why an STT lock doesnt show up. or a Fox 3 pitbull.... also the updated EA manual for the viper on page 420 says the Search button is not implemented

Alright here: Please take 10 min of your precious time and look at the 2 trackfiles provided + the video perspective of @Moonshine (especially the parts towards the end of the tracks) 4YA FOW PVP server EU. we both take off and fly straight to the enemy airfield. I'm flying behind moonshine about 20nm. He does not see my radar sweeping his plane at all. he doesnt see my STT lock. But he gets the beeping... Timestamp of STT lock from me on moonshine in the video at 4:42. this should correlate with my track file too. All the time RWR is beeping for new ground and air emitters, yet not a single new symbology shows up. In conclusion, this is sadly unplayable. Please find the tracks and the video here: https://mega.nz/file/U2gU1ZxD#LhkNQiKDVSRodQDGByB1Xatx7bgduR-qE_iH_EdYvt0 on a sidenote, in a purely 1v1 mission, no such issues appear. i suspect it has something to do with amount of "emitters", but adding 20 ships does somehow not seem to be an issue. granted, the ships were all the same type of emitter, maybe it's the amount of different emitters causing issues? mission file i tested that 1v1 with is added too. Test.miz

it constantly gives the beeps for new emitters detected, but on the RWR, no new symbols show up.

sad but true. it seems to work on ground emitters, at least in the nevada defensive systems instant action. but planes? nope

Without directly quoting a manual, please go find the m3 or another specific one just before year 2000 and read carefully the section about vis submode. Especially the very first line about what sensor is initialized as SOI and where the Weapon seeker is slaved to. This should answer that pretty clearly. Talk here is not about us expecting the mav actually Locking the target 90° off bore. What we expect the mav to do is to slew to the designated location once the target box gets within seeker FOV, which it currently does not do in vis submode but somehow does in PRE.

Please read the posts first before such comments… all the evidence is there and describes the currently questionable implementation.

does the terrain make a difference? if you look at the background of the test with Humvees, the background looks like it's out in the no mans land on grass and your test @Hobel is on an airfield. i remember there was once a post about the cbu 103 or whatever where there was a significant difference if the target was on an airfield vs out in no mans land

Looking great!

Manually enter local time using either the hack line on the time ded or you overwrite the zulu time with local time on the time ded or some quick maths in your head

In plane shows zulu time. F10 map for example shows local time. Be aware of the timezones

A Spi is a Spi, so the missile should try to acquire its location once designated. how else would that feature work? "yes you can designate with the helmet, but only if it is within MAV seeker FOV and no, we dont give you any visual info in the helmet of where its limits are." really? It would make the feature obsolete and possibly risky if the missile would not try to acquire the SPI location designated by helmet in EO VIS. The pilot sees a threat off his 3/9, designates it in EO VIS and when turning towards the TD box, the missile doesnt slew there because at the time of designation the Target wasn't within the MAV seeker limits? i am not referring to PRE, i am referring to EO VIS, which can be found in the M3 under the HMCS section.

But why would the Mav not try to line up with the TD box as soon as it gets within the seekers gimbal limit? M3 manual on page 84/85 describes the workflow in detail, and nowhere does it say that the target must be within seeker FOV for a designation with the HMCS in EO VIS.

Yes it does. Barely any server requires pure scripts. You‘re fine if you modify it.

I tried to replicate, but it seems to work fine. hint: if targets are too close together, the missiles shot very short after eachother will blow eachother up. looks fine to me tho AGM65D.trk AGM65H.trk

See tracks attached. There is no way to toss the bombs due to the symbology in the HUD being very strange. Track Mk84Air_1: As soon as the Fuse setting is changed, the HUD instantly shows the Toss Anticipation Cue, despite being very far away from the Target. Cycling the Fuse over and over reproduces this weird behavior. After that, a normal CCRP can be flown, level delivery the bomb hits. BUT: just before the Weapon release, the HUD again shows the solid circle for the Toss Anticipation cue Also in this track i could not for the life of me move the TGP. you can see the TGP having a seizure when i try moving it. Track Mk84Air_2: Same as above, but here i could move the TGP. now the funny thing: when entering point track, area track or pressing CZ, the HUD instantly shows the Toss Anticipation cue. The rest is as in the previous track. As comparison, Track Mk84 shows that everything seems to work fine with the normal Mk84. I have only encountered this with Mk84Air. I have not tested DTOS or CCIP, so i dunno if there is any strange HUD stuff going on there. Mk84Air_1.trk Mk84Air_2.trk Mk84.trk

You can find the CMDS Programs in the CMDS_ALE47.lua and you tecnically could change it. but it will break IC on servers that require pure scripts Semi and Auto cannot be changed in the cockpit on the CMDS DED page Also: none of the SEMI/AUTO programs have Flares in them. The Programs for Semi and Auto are the following: -- Auto presets -- Threat type 1 programs[ProgramNames.AUTO_1] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 4, salvoIntv = 1.5, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, } -- Threat type 2 programs[ProgramNames.AUTO_2] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 6, salvoIntv = 1, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, } -- Threat type 3 programs[ProgramNames.AUTO_3] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 8, salvoIntv = 0.5, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, }