Bahger

Thanks again, guys. So I kept the original SEAD order but set it to activate only after the SA-11s are destroyed. The Tornadoes do this affectively, going for the radar only (Druid, where did you see that I had targeted the launchers? I did this once but am sure I corrected it before posting the file here). I then eliminated the SEAD En Route command. I gave the SEAD flight an extra WP for the racetrack orbit. Now the Tornadoes still burn like crazy, do not appear to orbit and RTB long before it seems to me they should. I don't think they are going after the AAA or SA-9s although I've seen them do it before and would love to figure out how to replicate. I'm going to add a tanker and then re-post the .miz.

Druid, I appreciate your response, as always. Re. Arty: That's the point, I don't want them to attack the tanks on the hill. I want them to shell the town. Indirect fire should be commanded, and not a function of finding the nearest target in range/LOS, right? Re Tornadoes: I will implement the changes you suggest, thank you, but the big caveat is this: If I rely on the initial SEAD tasking, the Tornadoes will not threat-prioritise. They will go after the SA-9s on the map instead of targeting the much more mission-critical SA-11s. That is why I had to use a Waypoint/Advanced targeting command to force them to go for the SA-11s first. I then want them to loiter, picking off the remaining SEAD targets. Your suggestions may well implement this...

Artillery: i. LOS: It appears to need LOS to the target or it won't engage. This is obviously inappropriate. Is anyone aware of a spotter unit that is supposed to be deployed tio overcome an apparent requirement for LOS between artillery batteries and their targets? ii. Uncommanded targeting AI: I have often used artillery in missions. Before the recent update, I have always been able to get it to target any area of the map regardless of the deployment of opposing forces within its range. In my current .miz, I set the arty to target a town but the presence of opposing tanks between the arty units and the briefed target causes to arty to target those units, every time, ignoring the correctly set player-inputed "Fire at Point" targeting instructions via the WP/Advanced targeting options. These are both distressing developments as they obviously go against the inherent purpose of artillery as an asset in the ME and seem to preclude its use, at least by me. Uncommanded RTB: In the same .miz I have two AI SEAD flights tasked with acquiring specific SAM units, killing them and then returning to altitude to orbit over the battlefield, spotting and/or prosecuting other SAM targets as part of their pre-set SEAD instructions. In each case, the flights behave in the following anomalous ways: i. They RTB after the initial attack run and before orbiting. They retain their drop-tanks so I cannot imagine they are out of fuel. ii. They fly very low after the initial attack run, in full a/b (they are Tornadoes) which obviously does consume fuel. They never attempt to regain their briefed altitude. I am becoming a little weary of the ME and the sim's AI eccentricities. If I cannot overcome these issues in my currrent .miz, I might stop making missions as it's time consuming enough without the "issues". I am happy to accept responsibility for user/ME input error (perhaps expecting the Tornadoes to regain Angels 30 is ambitious but they do have two big engines...) but I am confident you'll find all the reported glitches present and correct. If anyone wants to look at the attached .miz and comment I'd be grateful. Battle of Khashuri Pass 10_SP Test.miz

Has anyone noticed, and, if so, can anyone explaing, the new "Event" box in the Left hand column of the conditions menu? I've taken a look at it but am not understanding the logic quite yet.

The "Unit Dead" or "Group Dead" conditions are probably the ones to use here. These have to be user-placed objects recognised by the ME as being Red or Blue.

So do you recommend changing Win audio settings to stereo before using a headset?

How do I get the radio menu text back? I switched it off a while back and cannot find the setting to switch it back on...

Good suggestions from Olgerd and Nate, many thanks both.

...yet sometimes it does, which makes the rest of the startup/alignment awkwardly one-handed, as you hold down the wb (for those that do not have brake-capable pedals). Pausing the sim with wb engaged then unpausing works to offset this but obviously only in SP. It's a nuisance. Not a huge deal...but a nuisance, as it will sometimes roll with the throttles at zero.

Thanks, Ells. Quick follow-up: Is it true that 1.0.0.8 enables you to start the alignment as soon as APU Gen is on? If so, should I adjust my startup procedure to start the alignment before engine startup? And if so, will engine startup cancel out the alignment?

Nah, you did great, glad you enjoyed it, always good to get a full flight.

Well, Druid, I'm making progress in that my 2-ship Hog AFAC now talks to me but he's ignoring his assigned target (a FARP group) and FAC-ing a column of tanks instead. I may take your advice and re-plot the whole FAC flight/triggers but can you suggest the optimal FAC commands in the waypoint/advanced menu to get the FAC flight to 9-line its briefed target and the best distance at which to set the start FAC-ing WP?

Druid, as always, thank you. The JTAC logic in the sim is indeed mysterious. Sometimes they will continue to FAC other, non-assigned targets after their assigned targets have been destroyed, which is impressive, at other times they are "on rails" and only see the specific targets they've been assigned. In one of my missions, an AFAC tasked to artillery at one end of a valley then directed me to infantry at the other, most gratifying, but you never know what you're going to get. Before I entered the frequency/modulation next down from the top entry in the Waypoint/Advanced menu for every WP located in the area where he might actually have to transmit, I was getting no response on AM or FM, from any type of unit/target combo. Nada, nothing. I never had this problem or needed this workaround, when making JTAC missions for SP. I always use "FAC Assign Group" rather than "FAC Engage Group" as the latter seems to imply orders for the FAC to actually engage. Re. priorities, am I correct in stating that 0 is highest? And you get this option in "Engage" but not "Assign". Hmm. Finally, I find AI on/off to be quite useless. Maybe I'm not understanding something but I have tried to use it to simulate SAM radar units switching on intermittently, as IRL, but overflying a/c always respond as though being painted.

Damage, many thanks. I really appreciate the assist. I might have come to the same conclusion independently, please see my other thread here. (Mods, feel free to merge threads, sorry about the doubling).

I may have found a solution, although I still have to test it in my mission. It appears that JTAC will not work in MP unless the JTAC unit's frequency/modulation is entered as the first available value in the Advanced command menu for every waypoint where the JTAC might be called on to transmit the 9-liner/responses.In a test mission I made last night, any JTAC without the frequency/modulation command in first position (under the immovable flight mission line, that is) entered at every WP, above even the "FAC Assign Group" command, would not work. I have never had to do this to get JTAC to work in SP; either one waypoint radio freq/mod order at the first WP "carries over" to all the others, or it'll work simply by entering the freq/mod information in the unit's "Comm" field. I'm going to test this in my misssion and let you know how that goes.

Excellent solution, Frosti, especially as I have both the brake problem and the Logi keyboard. Thanks for the detailed instructions; I've never used the software before but will now! Rep inbound.

I had a thought (it happens occasionally): Discounting ME user error (I am very experienced in putting fully-functional JTACs into missions), the fact that the JTAC appears not to be transmitting to the player at all, even routine Bullseye reports, may be attributable to the player's (i.e. my) choice of a/c when testing the mission in a closed LAN server. I've heard before that only the host gets reliable contact with JTAC in MP. I have been testing the .miz in one of eight client a/c, not the first one I created. In a MP mission with a JTAC, should one a/c, for the host, be "Player", not client? I know this is clutching at straws. I'm making those test missions, starting with one "Client" Hog and a JTAC transmitting on 35 MHz FM. I will then experiment with JTACs that take off in-mission rather than start in the air, and JTACs that have orders to change frequency en route per waypoint instructions. If it works, I cannot think how I can troubleshoot the .miz in which every form of JTAC/target combo does not work.

Yeah, I wanted not to be able to contact the AFAC until he reached WP3 because before then he should be on the package common AM freq. However, even after WP3 he was uncontactable. I will make those little test missions, test them and post them here, thanks as ever, Nate.

Hey Nate. I did that in every case, i.e. set the frequency and modulation in the Waypoint/Advanced/Perform Command menu. For aircraft, as opposed to land-based FAC units, JTAC has always worked for me after inputting the frequency/modulation one time in the unit's Comm field. When I use land-based FACs, I always set the frequency/modulation in the Waypoint/Advanced menu. For the .miz attached in this thread, I tried both methods, to no avail. I cannot test it right now so can you tell me: Did you get the JTAC in my .miz to work, and, if so, how? The upload had either 75 or 30 MHz FM set in the WP menu, but only at the WP containing the FAC orders-- the method I've always used -- not all of them.

Many thanks TRoe13. If you -- or anyone -- can get AFAC "Chevy" flight to respond to calls on any FM freq in the attached mission, I'll owe you big time. Apart from the JTAC glitch, it's a well-evolved medium-scale .miz with some radio placeholders. It's a Beta but there is a full briefing and all client Hogs have loadouts. No pre-loaded flightplan, use the briefed nav points I inputted into the data base which can be accessed in cockpit via the CDU. You don't even neeed to fly the .miz, really, just take a Hog up to where you should be able to talk to Chevy but stay out of the SAM envelope. Thanks again, I'm at my wit's end. Note: I have attached 2 files, the latest version of the mission (it's MP only) and a "FacTest" version that starts you in the air as "Player" and might save you some time; this version has slightly different FAC tasking. You will also see that I want the FAC to push to his FAC frequency at a waypoint. If you can get the FAC to respond, please post your radio transmission settings because I cannot receive anything from him on FM, nothing. MP2_08.miz MP2_08_FACtest.miz

This looks great! Must fly it soon. Thanks for all the hard work, Speed.

I've spent hours in my new MP-only .miz (created with all client flights/AI and saved to the DCS/missions/MP folder) trying to get JTAC to work. I have tried almost every possible combination of platform (A-10s, Predators, infantry), proximity to the target and target unit/group. Only using FM for JTAC (I want to reserve AM for package common comms) but trying different frequencies, I have never, not once, been able to get JTAC to respond on check-in. He doesn't even broadcast position or target info from Bullseye, on his assigned frequency. Just to be completely sure that something hadn't gone haywire in the sim, or with my default radio settings, I went back to older SP missions I've made...JTAC still worked fine. Mission making is my main contribution to this community but I am out of ideas and on the verge of giving up trying to implement JTAC in MP, which is a pity as it is a superb feature in SP that distinguishes this sim from all others. Rather than make a track file I'm wondering if a dev, or tester experienced in the ME could take a quick look at the .miz. As you know, I rarely pull the emergency cord like this, but this is the most vexing and seemingly inexplicable problem I've ever had in DCS A-10 and I've been flying it and making missions since the first Beta. I'm at the end of my rope with this, out of ideas. Thank you in anticipation for any guidance and/or support.

Thanks ndp. The truly vexing thing is this: I simply can't receive on my FM radio. I do not hear the flight on 75.00 calling position, yet I can hear the SEAD flights I put in on AM. I have tried all sorts of combinations of rotary/push-pull button settings in the Intercom Panel but no luck. There must be something awry with my radio settings. Arrgh.

I do not understand the Intercom Panel. Is the radio selected by the rotary the one at 12 0-clock? And what difference do the push-pull buttons make? I tried every possible combination this evening and at no point have I been able to receive on FM. Vexing.

You may be onto something there, Damage, thank you for taking the trouble to think about this and reply. The default switch state of the player's a/c often varies in small but important ways and this may indeed be the culprit. - I rarely use ground crew but will check position of the Intercom Panel rotary and confirm set to VHF. - How do you suggest cycling the radios? Do you mean just cycling through the 3 different mic transmit buttons? - I can confirm that the FAC units are not getting hit. - I have not tested the mission with TARS, only in singleplayer and in a closed LAN MP server. After getting TARS (what a wonderful realism enhancer) I moved my non-TARS mic tk buttons to the equivalent shifted functions on my HOTAS, freeing up the corresponding unshifted functions for TARS mic tk. I thought about TARS while puzzling over this but see no reason why it would affect JTAC comms; I appear able to transmit to JTAC (i.e. the radio menu functions are present and correct) but either JTAC is not receiving or I cannot receive. Odd though it seems, it appears to me that JTAC basically works in SP missions but in MP it's a bit borked. However, as I said, I tested this .miz in the SP exe. Stop Press: Oddly, I have never had to switch the Intercom Panel rotary to FM to monitor and transmit to/from FAC units on FM frequencies before; do you think this might be the issue? it's odd that every different kind of FAC unit/target combo failed to respond but all were on FM...