Sedlo

I can't load the mission right now because I don't have the mods you have installed. I'm willing to be the reason is the frequency you're transmitting on. Change the frequency that the transmission is happening on to one that has only one decimal place and give it a go. (make 317.525 into 317.5 and see what happens). Don't worry about cockpit parameters, it's just a way to see, via the console, what the aircraft you're flying is actually doing. (it will list things like what frequency the radios are tuned to, etc...)

Hey Petecassar! Thank you, I really glad you are enjoying the campaign. It was my first major effort in mission building, and I'm also really happy with the way it turned out. Regarding pay, thank you for the offer, but it is not something that's required in any event. I learned a lot making this campaign, and am using the tools learned to make bigger and better ones. However, if you do wish to make a donation towards the cause, you can PM me here on the DCS forum. Thanks again! SEDLO

This may not be related, then again, it may be as well. When I was making my Red Flag mission, I was having problems with some transmissions on frequencies not working, and 317.525 was one of them. For some reason, it just didn't seem to work 100% of the time. Try switching the frequency to 317.5 and try again. It was almost as if there were problems with the 25khz channel spacing. In my case, the cockpit parameters of 317.525 would show as 317.5199996 (or something like that). That precluded my aircraft from receiving the transmission. My thinking is that although your aircraft radio says it's tuned to 317.525, it is in fact tuned to something like 317.5199996. I can check it out a bit if you send me your mission.

That looks very sharp, indeed!

With the Viper and Hornet, you've got just the two radios. Keep AWACS/Strike in Comm1 and the JTAC Comm2. You're not going to be in comms with more than two external (to your flight) assets at any given time, really. Plus, don't forget to monitor guard! If someone else wants to talk to you, they'll call you on that! :-)

You could push the wingman over to the JTAC frequency that you're working, that should do it.

I haven’t played around with it too much, but the set mission briefing action might be what you’re looking for for now. You can type plain text into the action, and it will appear when the player selects Alt-B. (It’s not a knee board but it’s a start.

Just downloaded, can't wait to give it a go! Thanks for sharing, Suntsag!

Thanks, Painter! Yes, the MANPADs are quite dangerous, I've found I get shot down a fair amount of times :-)

Sounds like a great idea, but my time is currently booked trying to finish my Hornet campaign. Perhaps in the new year (but maybe by then we'll have a Syria map)!

I have noticed that as well, I think it has to do with the outside air temperature. I took the mission and changed it to be above freezing and the engine seemed normal. I'm wondering if it has something to do with ED modeling the engine at lower temps. Not sure if it 's a feature or if it's a bug.

@Lukino81 and Viking 1-1, thanks for the kind words, I'm glad you enjoyed the missions so far!

I've just tested this on Nevada map, I've got a preset set to 37.5 but it shows up at 375.0 in the scratchpad DED when I cycle through the presets, and I cannot contact a JTAC on 37.5. However, when I take a look at the cockpit parameters, it will show COMM2 set to 37.5. Odd.

Thanks! Mission 2 the channel to push to is 13 Right (VHF), not 10. I think that's what the issue is here. I've changed the mission so the text message will stay up on the screen longer until you have time to set the correct frequency. I've found formatting tables in the briefing is a PITA, but I will see what I can do. I'll also speed up the tanker in Mission 3. Thanks for the feedback!

Here you go: https://drive.google.com/file/d/17MxuYNOjldkY-UKhU6EPf648VpQNQLI_/view?usp=drivesdk

This looks cool! Thanks for the resource, will dig into this!

Weird... I'm not sure, it was working last I checked. In any event, the mission is scripted that you should only need to fly within 300ft or so and then you can call refuel complete. I'll have a look next weekend and see if I can find the culprit.

Not yet, hopefully next patch.

The waypoints are they are now are about 500ft agl in the editor. I've just reuploaded a newer version that has them lower (version 1.96)

Thanks for the feedback! Are you using v1.95?

One more from me... Is it possible to make the mission briefing text formatted? Like the ability to define paragraphs, bold and bigger headings, insert tables, etc...

Are you using the correct keybinds for the different radios? The "" key won't work once airborne.

Totally! For me too, learning the quirks and idiosyncrasies of a new aircraft are indeed half the fun, be it real life or DCS. I'm having a blast the the F-16 so far!

Let me know how it turns out!