Nix Mills

Scoring system seems right to me, but you’d need to get all the targets for a 100 result. As for your loadout, you’ll need to push that one up the chain to CAOC who issued the ATO.

I can take a look. Do you have a screenshot or message log of the debriefing you can select at the end when you’ve landed?

Hi guys I'd really like to ask for the lua task "refueling" to be made so that it can be used for a Unit also, like many of the other tasks do. The task works for a Group, but if you give it to a Unit (such as your wingman), the Unit will "RTB". Examples: Refueling = { id = 'Refueling', params = {} Group.getByName('Ram-2'):getController():setTask(Refueling) <-- this works fine for an AI group Unit.getByName('Ram-2-2'):getController():setTask(Refueling) <-- if used on player's wingman, wingman will RTB Keep up the good work - love it.

Hmmm... that sounds a bit frustrating. I haven't heard of or experienced that problem before. It might not be caused by the mission. However, I have updated the failsafe now so that at least the bunker will be destroyed. I'll request for it to get pushed out with the next general update.

Read this first

I'd have thought that was an impossible bug to create. The error you got was because it was trying to calculate the bearing to the Gecko the moment it fires at the decoys, so that Shadow can call it out. It appears that you'd have somehow managed to destroy the Gecko at the same time it fired its first missile. Anyway, the script error you got should not have had any impact on your ability to complete the mission. I have however created a failsafe for this now.

Thanks - I wasn't aware of this until you mentioned it. Nevertheless, someone else had already reported it to ED, so hopefully it'll be resolved soon.

Thanks for reporting this. I was a bit surprised to see this as the Guard frequency was not actually controlled by the missions but a native DCS setting. It would seem that one of the recent DTC updates might have broken the Guard setting. For now, I suggest you simply put 243.000 into channel M (manual).

Thanks for letting me know. Apparently it has not been updated although mentioned in the patch notes. I'll resubmit for next patch then.

Yeah, the thing is, that message doesn't exist in any of the missions. Your standard message is: F-10 OPTION (I) TO CHECK IN WITH STRIKE (265AM)

I can't really find anything. Would you mind sending me a screenshot of the message history or something?

It seems to me that when the air pressure in the weather settings is increased, increasing the altimeter setting doesn't quite keep up. From what I've noticed, but I could be wrong, the difference between you what you see in your HUD and what is the 'true' altitude (which you can see on the F10 map) gets greater the higher the pressure. The script that talks out player's altitude (e.g. when checking in with Magic), is based on 'true' altitude and then rounded down to more or less match what you'll normally see in your HUD , which by default always seems to be 200-500 ft higher when you're up in the 20s. If you have also changed your altimeter settings, there could be an even bigger difference between what your HUD reads and what the true altitude is. You will also notice that this sometimes also affects your fuel state readings, which can be off with one or two decimal points - even when using the native DCS option to check in with Marshal. Don't worry too much about it. The missions are set up with enough tolerance and your altitude "in the CAS stack" or in the transit corridor doesn't need to completely accurate.

Check in with Devil, then establish orbit over Deiz-ez-Zur at 20,000 ft (stay within 9 nm of target). Make sure you're monitoring Devil on PRI and wingman on AUX. You'll get a reminder after a while you haven't passed this step.

I have "relaxed" the criteria for both a bit and added a failsafe to help detect impact on bunker, in case the others didn't work (it happens for some reason). Should be out with one of the next updates. Note that Player is reporting that they're on station when they start orbiting the target, not the moment they get visual on the target. The first task is to confirm civilian activity visually.

Glad to hear. If you could tell me what mission it was and I double check the scores.