Sinclair_76

Got it. Wrongly put the standalone version of stopgap in the mix. Since SA it would probably override the original cfxMX. Now no more errors.

It is null

Updated a whole bunch of scripts since there was an error regarding destroyed units popping up. Now, instead, I have these errors regarding the radiomenu and bomb range prior finishing loading the miz and another after slot selection and prior jumping in cockpit. What am I doing wrong?

JSOW as well but not the CBU-103/205 since those don't have gps.

Beside the JDAM absolute mode not being simulated at this time. The tape number ED is simulating within DCS has no other means then the steerpoint to pass coordinates to the JDAM as a preplanned mode. Basically the engineers decided to stick with the logic of the early models while upgrading. In combination with lack of blast/shrapnel damage. Preplanned JDAM are useless in DCS F-16. You can trick you're way around by forcing JDAM relative mode by using the TGP and updating the target coordinates. The DCS F-16 is therefore useless in cloudy conditions. Especially compared to other aircraft the viper feels handicapped. In general I am happy with the realistic behaviour of TGP and INS. But the way they implemented the absolute mode but not the relative mode for just the F-16 I think they screwed up. Either implement it together for every aircraft or not.

Smoke can be deployed by spotter aircraft, i.e. the OV-10 in Vietnam used smoke to mark targets. The A-10 also has done this in recent times (OIF/OEF/ISAF). Artillery (M109/PHz2000) can be used but don't know if they operationally did so. Mortars have been used as well (of 60mm at least) they have a range of 4km. Lastly underslung (M203/AG36) with a range of 350 can shoot smoke grenades. Dedicated automatic grenade launchers like the Mk19 or HK GMG have a range of almost 2km. A link to a video where an A-10 is guided to a target by using smoke.

Thinking of buying one. @FatShadow Still happy with it? @Rogue Trooper Have you received yours yet? Are the grips strong/firm enough to handle the weight of your arms?

Bug is stnullill present. Overhead lighting present which does not illuminate the surrounding area or cockpit ftm.

Muwaffaq Salti some HAS have no lighting effect (in cockpit). Specifically parking 17/18/19/111 and possibly others. Seems like all the HAS of the same type are affected.

The HTS locates emitters through triangulation. For triangulation to work effectivley the HTS builds a dataset to finetune different measurements. That is the reason to maintain offset of more than 30 degrees. More than 60 degrees will be out of limits for the HTS (forum LINK). Lesser offsets will take more time to get a PGM2 solution needed?/preferred for POS/EOM shots. But for AGM-88 kinematic purposes a launch direct to threat is preferable. Even a 30 degree offset will need a massive amount of energy to correct. Energy that would be otherwise used to maximize the velocity of the missile in the terminal phase.

One of the exceptions where ME is easier then. Thanks for looking in to it.

This is how I do it with the ME Given this does not work on FC3 aircraft. But above does work for f-16/f-18. AFAIK the parameters are not the same on all aicraft.So DML would have to figure out the type and apply correct cockpit parameter.

Is it possible to add a requisite frequency to the radio menu? So the menu only bangs a flag when item is selected and the correct radio frequency is tuned?

Yes. And although it was a dirt strip it was pretty level Not like the rollercoaster it is now.

IIRC before the lead uses TDOA, all wingmen need to drop their tracks.

@cfrag hope you're doing well after the ED induced friction. Is there a tool to count the amount of player groups active in a zone and use that number to say limit the amount of cloned groups? Example, you have 2x active player groups and you want to limit the clones to 1x cloned group per player group. And only clone again when first cloned group gest destroyed. Concurrently cloning another group when another player group joins the game.

The Tarin Kot runway is beyond awful. Looks nothing like the real thing.

While I really value that ED is trying to further realism in simulation, the fact that the JDAM implementation is still halfway done is frustrating to say the least. Instead of introducing a new, but feature complete solution, ED introduces a half baked (only relative mode) on only the F-16. It’s been a couple of months at least now and some information is welcome. Furthermore it would be prudent to apply this to all things coming out of ED’s hands. Recently all solutions seem to introduce more problems than they solve.

@cfrag Could you tell us more about convoy?

Well done @cfrag! Good code does not limit imagination. I am designing a mission were aircraft can be tasked for XAI (airborne alert air interdiction) / XCAS (airborne alert CAS). To keep it interesting randomness is key. Enter DML. My latest mini project is to have random insurgent roadblocks. With the latest addition in code I requested it is working out really well. Included are some pictures. Random vehicles, random barrier types, random insurgents, camo nets and of course random locations. Was a slight challenge to get them positioned correctly on the road but I've overcome that issue as well.

Works like a charm now. Thanks!

Close! But useHeading as well as useOffset have the clones facing the original direction. With the offset I would've expected that. With the useHeading I would have hope it would align it's direction with the lead vehicle.

Pasted the updated scripts but it doesn't appear to work.

Yes this is what I want. And indeed I am living on the edge...

A small test mission. Basically my intent is to clone a 'lead' vehicle on a random location in a zone. Then, using useHeading clone 4x MLRS in a specific formation on to the "lead' vehicle. In this small mission it is only a MLRS but in the mission I am scripting the vehicles are more random (per zone) especially paint scheme's) to liven it up a notch. Once the MLRS battery is in position kill of the lead vehicle. (Hence the question regarding linkedUnit to a small static item but killing of the lead vehicle is even better) to not always have the same vehicle in otherwise random formations / conglomerations. Radio Menu is enabled to fire flag 1: this clones the lead vehicle in the END zone (yes my feable attempt at humor). Firing flag 2 will clone a M1 randomly close to to the lead vehicle as a QED Firing flag 3 will clone a MLRS battery using useHeading to maintain formation Firing flag 4 will kill the lead vehicle. Test-DML.miz It seems to stay at the original location. My hope was, that it moves with the lead vehicle.