buceador

This is simply a question, not a complaint! Ground units can be placed and designated LATE ACTIVATION - VISIBLE BEFORE ACTIVATION. Aircraft (seemingly) cannot? Now I am aware that placing an aircraft IN FLIGHT with LATE ACTIVATION - VISIBLE BEFORE ACTIVATION would be counter intuitive but why not ON RAMP / RUNWAY / PARKING? I know you can designate UNCONTROLLED to kinda get around it.

Indeed so. Actually I just gave it a waypoint route and an AI task push SWITCHWAYPOINT (to the desired airbase) when a certain condition was met.

Despite having little or no interest in the Mudhen I have to say what an outstanding job they have done on the Pilot / Wso, especially from external (F2 / F4) views. Hopefully ED will follow their lead with the F-16 / F-18.

Same here - around 90 seconds now ST/MT and around 34 seconds before - this doesn't make me suicidal but it's a big percentage increase in loading times...

Sounds great, could you elaborate on how to achieve this using a flag please? I have worked out how to do it, again, many thanks!

Thanks in advance for any help on this... I can get AWACS to RTB on (for example) UNIT / GROUP damaged / destroyed by using an AWACS waypoint that is set to LAND and using AI PUSH. However is there a way of getting the AWACS to RTB without using waypoints, for example if the AWACS is set to ORBIT?

Thank you for your reply! I had downloaded the zip and read the README.md but could not see where to install / locate the files that were contained in the zip file?

Undoubtedly a dumb-ass question but... I don't see a download link on Git Hub... Releases No releases published Nor any installation details?

The viper also has pitot heat.

Obviously every little helps but after 3 years of playing I have less than 800MB (about 1800 files) in that folder, track files are VERY small.

I think GS would beg to differ...

Model viewer is very interesting! Unfortunately the \DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\clickabledata.lua doesn't seem to correspond with the arguments in Model Viewer. For example ARG117 is the right gear wheel animation in model viewer but 117 doesn't exist in the clickabledata.lua file, also gear animation is from 361 in clickabledata.lua but 361 / 362 in Model Viewer reports as unused? I am aware that this query is pretty niche!

I want to trigger an event based on F-16 gear down using x: cockpit argument in range... Gear is 361 or 362 I think from my G:\DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\clickabledata.lua But... what are the relevant min / max values related to gear down? Many thanks in advance

The Viper has an extended list of available callsigns in the ME However if you assign one of these "newer" callsigns ATC doesn't use it in their replies to you? Are these only really available for AI? Edit: I've just noticed a post from Northstar98 Posted December 24, 2021 - asking for the newer callsigns to be voiced... F-16 Callsigns 9 Viper 10 Venom 11 Lobo 12 Cowboy 13 Python 14 Rattler 15 Panther 16 Wolf 17 Weasel 18 Wild 19 Ninja 20 Jedi

As the title suggests, what graphics settings causes or improves shimmering lines / edges? (see video - bomb approaching runway lines)

I've noticed the same thing, obviously it detracts from immersion and realism and looks like an arcade game...

Many thanks! Such a simple error! Also thank you for the tips!

Has anyone else had a problem with AWACS not reporting BRAA on bandits and no AWACS entry in COMMS menu? I set a sample mission - AWACS in USA coalition, F-16 in USA coalition - SU-30 in Russian coalition. F-16 and AWACS on 251 AWACS shows on RWR and visually. On mission start you hear AWACS calling in then nothing? No AWACS contact.trk

As perhaps you remember I was having problems with bomb release but once that was sorted I had no problems with the bombs following the laser (1688) and I have many mods installed.

Understood. What about this though? "What surprises me is how close to the minimum distance marker I get before the caret drops?" Is that the norm?

Ok, this time it worked but only just within the minimum distance. TGP TEST - Success but only just!.trk A big thank you to everyone who responded! What surprises me is how close to the minimum distance marker I get before the caret drops?

No mods and an air start? Did you actually run my mission, by changing the track file to a .miz file?

This is the base track, I just changed altitude and loadout... TGP LASER GBU10 FAIL.trk

Yes, I fully understood this point. I flew this scenario 8 times, changing altitude and laser guided bomb loadout, every time but one, mínimum distance was reached before the second caret dropped to release point, which was causing the problem, the attached screen grab shows the ONLY time it worked and then only just. So? Which mission parameters are incorrect?

Ok, so I waited for the second cue drop, ASL centred and got the same result, ie no bomb release. I tried with the Paveway on PRE just to check lasing / weapon release button mapping etc and everything worked as you would expect.