ChillNG

I'd honestly not even considered it before...but now you got me thinking....

Hi thanks for the comments! Hope you enjoy the rest of the campaign as much .

All sorted thanks, campaign is out now!

Ha ha thanks. You know I never thought about it lol, maybe one day but my plates pretty full for the next few years.

Thanks, hope you enjoy the campaign!

Hi, hot topic of discussion this one...I have a feeling the SA-18 has become more dangerous in an update since the campaign was built...but no proof of this lol. There is quite a bit discussion on it, I and others give advice on it here: As for F-16...see here, my campaign is almost complete:

OK this one's easy to solve, you went to the wrong runway. You went to runway 23, not runway 05. Basically after you turned left onto Golf loop you made an extra left on the taxiway and went off to towards runway 23 (the X on the picture). You should have gone straight over instead. Note this can be confusing as you actually take off in the opposite direction to Poodle - this was my mistake in building the mission, but I never wanted to change it back as it can mess up various timings by giving Poodle a shorter taxi.

Yeah changing weapons is always risky as it might break the mission as some triggers are based on the weapons themselves, but with 'user beware' message issued..you paid for the campaign so feel free to experiment as you see fit. Like Jettax said though the weapons load-out is often chosen to give you a challenge/certain experience so you will possibly miss out on that., and given the threat environment having to lase a GBU-12 will be pretty risky.

Fair enough

Ok thanks for confirming, yeah if you send a track when you can I'll run it my end and see if I get the same result and we'll take it from there. Also worth trying it without mods if you have any installed, can cause all sorts of unexpected issues.

Thanks for the feedback, glad you enjoyed it! And I'm with you on mission 6, love that one too.

New feature that will be part of FIWOS:

Yeah it's a known hornet issue, all liveries seem to be affected. Waiting on an ED fix.

Hi thanks for the comments, appreciate the feedback! There will still be a lot of chatter, but like in my other campaigns I do make some of it optional as I know not everyone wants it, especially the more 'expositional' dialogue. Always down to personal preference this one, I argue it's a much needed element of story development and player instruction, given there obviously isn't a real briefing or ready rooms to sit in and discuss things with your squadron, but appreciate it's not for everyone (and certainly not realistic).

Just checked, all worked fine for me. Experience (plus no other reports) tells me it won't be a bug but more likely something specific at your end so we'll need to figure out what's causing it. First step is to check the conditions for the F10 takeoff option to be added are being met, these are: You must have first requested taxi. You need to be at the hold short for the assigned runway (05 on mission 1) - see attached picture. Radio needs to be set for COMM2 ch2 (128.200), advise you press UFC ENTER as well. Don't overshoot the hold short line as this can remove the F10 option if you enter the runway. If you are meeting all these conditions and still have no joy, then if you can provide a track that would be helpful so I can investigate further. Many thanks

Did you press enter on the UFC after selecting channel 2? It's a long standing irritation in the Hornet, the channel selection isn't always registered unless UFC enter is pressed.

HI thanks very much, appreciate it! Nothing planned for the Ka-50, Apache is a maybe one day in the future. I have an idea and rough draft ready, but I'm not currently finding George or the wingman AI to be ready for how I build my campaigns. Once they're in a more suitable place for me, I'll certainly think about it in more detail.

Hi, can you check your keybind for the Comms menu, this sounds like you are using the Comms menu keybind (which is a more DCS wide generic option) as opposed to the Hornets radio keybind. The one you are looking for is called something like COMM1 or COMM2 switch (either should work) and is under the HOTAS keybinds. Nothing in the campaign should affect the autostart, there are nothing programed in that touches any of that.

Thanks! Should be completed and submitted to ED in July, release date will be up to ED but I would hope they won't keep you all waiting too long.

No probs

Sounds like you are using the wrong command. There are two radio commands - a generic DCS one which is called 'communication menu'. which will work on the ground but not in the air. Instead you need to use the command named 'COMM SWITCH - COMM 1 (call radio menu)' which is located on your 'Throttle Grip, HOTAS' controls. This uses the Hornets radio not the default DCS comms menu. Hope that helps!

Can you post a shot of your radio panel please so I can double check your settings and offer some guidance? From experience this issue is always the radio being set incorrectly (it's the only variable in play).

Thanks very much for the great feedback, great to hear you enjoyed the campaign. Hopefully you'll find OCN raises the bar again, and you'll also find a much more detailed ATC system to get stuck into!

Hi it's a simple solution this one, and a common error so don't sweat it. Sounds like you aren't using the F10 option in the radio menu, when you open the radio menu you need to press F10 (which is custom commands for the campaign). If you're getting called Enfield it's because you have selected the F5 option - which is the default DCS ATC system. Through the campaign you will only need the F10 option. Hope that helps!

Should be out before the end of the year all being well.