Bahger

I would never have figured that out, guys, many thanks.

Thanks very much indeed, Grimes. I think I have solved the RTB trigger using three-line OR conditions -- it worked when tested today -- but I'd be grateful for your input re. the other (and probably only remaining) issue, which I mentioned in the another thread here, i.e. whether ambiguity in the logic pertaining to Flag 10 can, in certain circumstances, cause the player to be assigned another target before he has completed the previous assignment. My intent is for the player to have to return to the CAP and remain there for 30 seconds before another target is given. Posting file now, thanks, as ever. (The file is 1.97 MB because it is almost finished and contains 2/3 of the radio voice files.)

Very helpful, gents, many thanks. All the above functions are set to FWD/BACK/DOWN on that hat, so that takes care of the 3 pinky switch lights functions. UP on my hat is "Left Throttle Button" so it must be mapped to AP engage/disengage, something I never noticed before as I had mapped this function to another button, which I will now eliminate as redundant. Thanks! One thing, what's the trick to getting the formation lights, nose floodlights, and nacelle floodlights functions to work individually?

The only condition is to set Flag 10 is "Unit in Zone". But because the trigger zone for Flag 10 is virtually the same as the CAP zone, and the CAP zone disables Flag 10 as part of the routine by which the player is given a new assignment (he has to be in the CAP zone, plus 30 seconds) it seems possible to me that Flag 10 can be switched on again when it is supposed to be off until the player completes the assignment (which takes him out of both trigger zones) and comes back for a new one.

I need to get this right for a mission voice comms file. N 43 02.067 E 044 45.300 Would UK military personnel say the "N" as "November" and then read the numbers (using "niner" for nine, if there were a nine)? Then would he/she read out the next line starting with "E" as "Echo"? Or is there another format for broadcasting coordinates? How would the decimal point be broadcast, if at all? Would he say "Break" between the two lines of coordinates? If anyone could supply broad guidelines or text for the above grid ref as spoken, I'd be grateful, thanks.

I must be missing something simple here. I do not have a TM Warthog so the A-10's left throttle button ("pinky switch", I believe), is mapped to UP on a four-way hat on my CH HOTAS throttle. I cannot seem to figure out how I use this hat to enable certain exterior lights functions that do not seem to work otherwise. In fact, I do not know what this left throttle button is for at all. Can anyone enlighten me? Thanks!

I'm using a switched condition ("Unit [Player] in Zone") to trigger a flag (Flag 10)that needs to be on for a series of random target assignments to work. Every assignment, once selected, deactivates the flag, which is then activated again before the pilot gets his next assignment. The pilot has to resume holding at a CAP waypoint. Outside the trigger zone associated with the waypoint is a slightly larger trigger zone whose only purpose is to reset Flag 10. My question is: - If I am still in that zone when the mission assignment is made, and Flag 10 is therefore switched off, will it switch back on again immediately because I am still in the zone and therefore still meeting the conditions for it to be on? - If the above is true, is there a better way to make this flag switch so that there is no ambiguity? I am asking because on testing the mission I got two target assignments one after the other, i.e. before the first was completed. I'm pretty sure the target assignment logic is sound (it's Grimes's) so I'm wondering if the main trigger is the culprit because of the way I set it up as a Unit in Zone trigger that might contradict itself.

Ha, yeah, that may be what Nikola neglected to consider, too. Using 3600' MSL as a guideslope intercept altitude for Vaziani Runway 14 approach might fly you into those tower blocks just outside the outer marker!

Thanks, Tharos. I'll try using a GS intercept alt of 3600'. (Don't forget, field elevation at Vaziani is nearly 1500' [1492']).

Thanks Nicola. I'm IFR-qualified in r/l but without published procedure altitudes, there is a certain amount of improvisation in DCS A-10. In approaching Vaziani from the NW, I use 5k as both a Minimum Safe Altitude and a Glideslope Intercept Altitude. At about 12 nm out, it does indeed capture the GS from below, resulting in a nice, easy 3 -4 degree pitch down descent to the threshold after the GS passes through the center of the AI.

I am still struggling with a trigger to end the mission: - player has completed 2 mission assignments out of the available three, no more can be given - Player flies back to the hold waypoint to resume CAP - 60 sec after the above, I want to trigger an "RTB" message. I have tried setting unique flags (100, 200 and 300) on completion of each mission and then putting all possible combos of the 3 (100 & 200 OR 100 & 300 OR 200 & 300) in the conditions field with the "Unit in zone plus 60" condition, but it doesn't work. Any ideas? Mia389, since posting the updates posted helps you -- as well as making poor Grimes sob into his breakfast -- I will post another one soon.

DarkEagle, I bet that's my issue, thanks. This is the problem with starting missions in the air or on the runway ( I only do either for training/testing); there are occasional inconsistencies re. what gets switched on. I will test this, many thanks. RogueRunner, it's not receiving a signal when I am at 12 nm and 5000ft that bothers me!

I do occasional tutorial vids. I had a track all ready for an ILS tutorial with commentary but have been sabotaged by the incessant beeping of the ILS receiver in the latest patch, which cannot be turned off or down. Not sure what to do about this.

Anybody? I tried it again tonight, same approach (from the NW at Angels 20) as the mission where the ILS works, but in this one I get tone but no localiser, GS or beacon tone...what on earth can be the issue?

I can no longer see allied ground units as green crosses in my TGP, or white crooses in the HUD. They showed up before in the previous build. All these units are set to broadcast on the net (I forget the acronym but it's enabled by default in the ME). No big deal but I was wondering if anything has been tweaked here...

I made an air-start night mission to demonstrate an ILS approach to Vaziani at night, and another, a runway start out of Vaziani, with a full flightplan, targets etc., also at night. Whereas the ILS for Vaziani works perfectly in the first .miz, in the second, the localizer, glideslope and beacon tones never come alive even with: - ILS receiver tuned, and ON, emitting tone - correct final approach course entered in HSI - ILS ON in front panel (behind joystick) In each case I follow the tower's given heading after I check in, and navigate to intercept the glideslope at 5000ft for Runway 14. Using the HSI CDI in the second mission I can approach and land very accurately but I wonder why the localizer and glideslope don't show up? Is there anything I should be enabling, either in the ME or the airplane, that I might be unaware of? Many thanks for any assist.

This is to confirm that I cannot turn it off, from the intercom panel or anywhere else. This sabotages my plans to release an ILS tutorial video so it would be good to know if it's on a bug-list, in which case I might wait until the next patch.

Ta much Nate.

What is the control for NVG intensity?

Thanks Castle. I don't think the ILS volume knob on the right works. Luckily it works to change the frequency to the right of the decimal point but no amount of right or left clicking affected the tone volume when I tried. Edit: Cannot lower ILS tone volume on either the right panel or the left. Has anyone had any luck with this?

Can someone refer to the knob referencec by Effte by the green tooltip text that shows up when you mouse over it? I'm having trouble finding it. The ILS tone is a great addition, especially beacon tone, but I'm about to record a track for an ILS tutorial and don't want the constant beeping. Thanks!

Yes, bit of an own goal there, xjics, and off-topic.

Yup, huge kudos for this, guys. Cooperative target i/d and prosecution is what makes this sim completely unique and state-of-the-art. Full functionality in MP is really exciting.

First-off, thanks for the update to an already great product, ED, this is not a whine. I'm just curious: Devs stated in the forum that MP datalink would be functional in this patch, but there is no mention of the subject in the changelog. Does this mean -- as I suspect it might -- that, whereas fixes have been made, it's still a bit of a WIP? If so, at what level might we expect MP networking/datalinking to work?

I'm looking forward to putting some badass audio files from you in my next .miz!