Bahger

It's a fallback. If the datalink fails you'd be screwed if you didn't know how to use the CDU to find the target via coordinate.

It was probably the SA-19 that got him. It's cunningly placed, if I say so meself.

Thanks! With TAD as SOI, you'll see NET in the lower right hand corner of the MFCD, next to an OSB button (sorry, I forget which number). Hit that button and you will see two fields in the TAD, for "Group" and "Own" NET settings. By default they will read something other than 01 and 01. Using the Up Front Controls (UFC) keypad, enter 01 into the scratchpad and hit the OSB buttons next to each of these fields, re-entering the number into the scratchpad each time. For datalinking to work in SP missions, both "Group" and "Own" have to be set to 01. Hopefully this glitch will be addressed in the patch.

Greywo1fg, as lone as you're updating it, take a look at the arty coordinates, as well as the MLRS. After several playthroughs, I can confirm that one out of the two arty targets I've been assigned (most usually the first one) is way off.

Thanks! I'm in the middle of a follow-up mission, same location, but at night, with some randomisation of target assignments, JTAC laser designation and a ramp start. Voice comms. It should be ready in a week or two. Thanks for the encouragement.

Bookmarked, Evil, thanks a lot.

Ok, this is what I mean: ASOC: Air Support Operations Center, USAF organization responsible for planning and coordinating CAS missions in support of ground forces. Is there tactical communation between ASOC and CAS pilots in-fligh and if so, how would ASOC personnel identify themselves on the radio? Edit: I believe ASOC identifies itself as "Tombstone"

No, I just want to know how airborne tactical units interface with direction and/or command provided from ground units assigned to a mission. For example, if AWACS spots a target, which unit in the chain of command would provide the ultimate authorisation for attack aircraft to strike it if it was not already fragged? There is nothing classified about any of this, it's about procedures and protocol.

I'm looking for authentic detail regarding the following aspects of US/coalition air-ground ops: - What would a "ground controller" type of entity be named (acronyms or full title)? Not some bunker in Kuwait, but a local unit, tasked with aiding pilot target i/d and tasking. Under what circumstances would this entity be able to overrule pilot/AWACS calls? Would this entity be on a guard frequency or have a dedicated frequency for communication with mission pilots? All detail/specialised knowledge much appreciated, thank you.

Ladies and gentlemen: Thanks for your enthusiastic response last time. One more, I need American voices for the following roles: - Ground task force commander (male) - Mission coordination (female) There may be one or two more roles, depending on how the mission progresses but the above requirements are confirmed. I'm looking for raw Audacity files, i.e. not yet exported as .ogg files, so that when I receive them, I can filter them to sound like radio comms and then convert them to .ogg. If interested I will send you message texts. The messages are organised in the .txt as separate paragraphs; please make one recording per paragraph/message so that I do not have to edit the .aup to separate the messages. Audacity outputs the following files for every recording made (I'll need both for each recording): 1x .aup file 1x folder with the same title as the .aup file I do not believe I can attach files to PMs here so could anyone interested please say which role they want and PM me an email address and I will send out the appropriate .txt doc. Thanks!

What a dunderhead you must think I am. OK, I think I've got it. Will test it. Thanks for your patience. Edit: Made those changes. They seem to work, although when I tried to increase the target number to 5 (each with 20% probability) the mission kept selecting the same target in the first instance, so I abandoned that and went back to the 3 target/30% version, which randomised the initial selection as it should. What I need to do now is figure out a way, once the player has destroyed 2 targets of the 3 that the program randomly selects, that no more target assignments become available, even if he returns to the hold (which triggers additional target assignments). This way, you have to play the mission more than once to be assigned all available targets. Ideally I'd like to be able to set it up so that it assigns 2 out of 5 rather than 2 out of 3 each time but it appears that I am already exceeding my very limited mathematical skills. Updated file posted.

OK, Grimes, I think I get it. This is not the way my mind works but I'm determined to master it and I believe I have wrapped my head around the concept. In the attached .miz: Flag 4 = The initial condition for every task, Unit in zone "Hold". Before each task is assigned I want the player to be established in a hold, therefore in each case there is the following condition: Flag 4 True && Flag 4 + 60 "Trigger Trigger" (You need to be a fan of The Clash to get why this is amusing) is merely the zone for the "Activate Mission Conditions" trigger. Do I still need it? I have added victory triggers for each of the 3 assignments to clear the associated flag when the mission objective is destroyed. I think my flag iteration logic in each trigger, referencing the other two triggers, is correct but this is most likely where I am making a conceptual mistake. Once again, would you take a look? 30 seconds of your time = 2 hours of me tearing what's left of my hair out. You will definitely receive credit on the mission. Thank you!

Thanks, Grimes, as ever. Can you explain flag iteration? I've never got my head around what "Flag less than..." or "Flag more than..." actually mean.

A while ago I asked about how to set up a mission with random target assignments so that, once the player enetered a trigger zone, a series of triggers with randomized conditions would ensure that the same target assignment of three would not occur first on successive plays. I'm using Grimes' elegant formula: The problem is that the program cycles through all the targets (in randomized order) every time the player revisits the initial trigger zone, when what I have decided I want is this, for replayability: - I will create 5 targets, with accompanying radio messages, spawning them to coincide with the narrative/players actions/triggers, if necessary. Each should be given a 20% chance of selection by the program. - Player enters initial trigger zone (a CAP hold at a waypoint) - Player is assigned one of the above 5 targets on a randomised basis - Player hits target - Player returns to the CAP hold - Player is assigned another randomised target - This ends the target assignment phase. Player receives message to RTB The idea is that the player never knows which two out of the 5 targets he will receive. In fact, of course, I could make 10 targets each with a 10% probabability of selection assigned. I don't want the player to be able to receive all targeting assignments on one play-through, every time he returns to the CAP trigger zone. Is there a way I can adapt the logic I already have to acccomplish this? Grimes? This could be a good mission so I'm grateful for any help in ironing out the kinks. Thanks!

1. Mid-air refueling 2. Low-level attack techniques and profiles, using unguided munitions, including threat evasion. (Poko24, FWIW, I have made a track for an ILS tutorial with commentary in IMC [instrument Meteorological Conditions], featuring an approach to Vaziani from 20,000 ft using GPS and ILS. If there is more interest I will get on with it, but not if it's high on Wags' to-do list).

It is. Look up ^^.

You can be a bit of a berk, Mower. Of course it's enlightening; primarily for those who still need to learn how to do this. When the head developer of the sim takes the time to make really well put-together tutorial videos, why bite the hand that feeds?

I will definitely try this, thank you. I'm hoping to make good contributions to the community through the ME, too. Fixing datalink for MP in the upcoming patch will make a huge difference; MP without working JTAC/datalink is a very significant omission that I'm glad is being addressed.

Yup, once. I got a polite but firm message from someone with a very convincing Russian accent advising me either to get permission to proceed through Russian airspace, or to turn back. I did not need to be asked twice.

Well, WarriorX and I had a great sortie this evening, Wx flying Lead, myself #2, both commed up with TIR3. We were assigned the artillery first and when he spotted it, he read the point target coordinates off the TGP and passed them to me via radio. We hit the Arty with CBU-105s, then got the dam, which we shacked with the remaining CBU-105s, then ran in on the radio mast and MANPAD with GBU-12s. Finally we decimated the coastal convoy with Mavericks. We brought fiery death to bad guys everywhere and flew well as a two-ship, maintaining good comms and SA. It's a terrific mission, with a real sense of operating over a battlefield. And the defenses keep you on your toes. What is the "50" symbol in the RWR? This was the best experience I have had online in any combat flight sim to date, thanks to a good mission and Wx's very high level of competence in the sim.

It's a delicate balance (re. off-coordinates). I think mtuckner makes a good point above, which is to provide some kind of talk-on if the grid refs are unreliable (whether deliberately or not). In real life I read about CAS pilots spending hours at a time searching fruitlessly for targets at briefed coordinates but that is where most people want even the most realistic sim to make concessions. Truly great mission, though; I am about to fly it again with WarriorX.

Thanks Speed, as always.

Gents, I have read that I need to divide the last two digits by 60 to convert grid outputs in the ME map to a format which the CDU will acccept in-flight and render an accurate location. I am mathematically challenged and anyway am unsure if this applies in all cases, or whether it applies only to the N, or E half of the coordinate. Using the folllowing coordinate from the ME (which I want to place in a radio message giving orders to a player in a mission) could someone please take me through the formula for converting it, confirming the accurate grid ref for CDU entry purposes, along with any other format changes I might need to make? (Also, please mention whether or not there is a missing zero that needs to be added to the beginning of either line). 43 2 4 N 44 45 18 E Thanks very much in anticipation:

No, "For 35" is the glideslope intercept altitude. Turn to the heading and set up a descent to the altitude. Then you be set up to ride the glideslope down to the runway if you are set up for an ILS approach to a suitably equipped field.

Well, one way to relieve the occasional needle-in-haystack target spotting -- when targets are in dense terrain or otherwise not either in the open or on top of their precise coordinates -- would be to incorporate JTAC, using an AFAC (like the Predator you already have in the mission) or a SpecOps FAC team. If/when a patch makes datalink work in MP, that'll be a great addition to this mission. Until then I guess it would work only for the host.