Gretsch_Man

That's what I'm hoping for, too. Just imagine to sit in a 3D briefing room in VR, getting briefed of an upcoming mission...

I've just finished the campaign and I must say I do like it a lot. While it may lack the excitement that a story driven campaign can provide, it was really interesting to learn about the Constant Peg program. The missions are characterized by a level of professionalism (partially also thanks to the wonderful documentation) that makes you feel like a true professional (wishful thinking on my part ) among other professionals. The ATC chatter only enforces that vibe (speaking of which, really nice job done by Wags. He should be employed more often in this role by other campaign makers as well! But the rest of the voice-overs are also pretty good.). I think this campaign makes for a very nice training tool for any aspiring Mig-21 pilot. In this regard, the F10 reloading option comes in very handy, although it takes some of the mission flow away. All in all, a very good campaign that does justice to a very good DCS module.

Looking at all the modules currently available in DCS, I'd like to see a North Cape map. This would allow for: * carrier ops * modern day as well as cold war scenarios * a nice battle ground for the Viggen (although Sweden would not be in that map, but close) * would provide a reasonable background for smaller sized scenarios to save fps performance (I'd also love to see a German Fulda gap map, but trying to play a full blown WW3 scenario would probably bring DCS down on it's knees) Provided DCS gives us more Vietnam era modules (F4, A-6, A-7, F-8, F-105), I'd also like to see a Vietnam map.

I suppose that's fair enough. Besides, the Tomcat has one all important feature that the Mirage lacks - the tape player.

Difficult to explain. I mapped the gain and contrast functions to two rotating switches. After playing around with these switches, I was somehow able to get some stuff visible on screen, but in VR it's still pretty tough to see any targets.

I'm stuck with mission 4. After getting on station, I was told to fly to the FEBA to identify a SA15 (or was it SA18) sam side. After doing that, I was told to get back on station, which I also did. Thereafter I kept flying between WP3 and WP4 for almost 40 minutes, with absolute nothing happening. My radios are set to channel 6 on green and channel 2 on red. Am I doing anything wrong here?

I played through that mission just yesterday and it worked fine for me. Did you land at WP2? Although this isn't made clear in the briefing, it seems you have to land at WP2 or at least descend to very low level. This will trigger the final briefing by Meatball. After that, everybody takes off one by one, heading towards the mission target.

I think I figured how to get it to work, but boy it's not easy to use in VR for sure.

In VR the thermal vision mode doesn't seems to be working properly (I'm on the latest DCS Beta version), because I cannot get a clear picture. Both the gain and contrast buttons on the TV console and the left-side co-pilot stick don't do much, so I just end up with having an almost white screen. Am I missing something?

Just finished the campaign and I got to say very well done! Very immersive. I also very much liked the in-flight mission briefings/debriefings by Bio. Yep, the wildcard is pretty tough to spot in VR indeed, at least with lower resolution gear like my Rift-S (I only caught the wildcard once). But I'm not complaining here. I have to say that as far as SA goes, I still find those larger furballs utterly confusing. But this campaign has given me some ideas on how to work on that. I also got more confident with 1 vs 1 encounters and missile evasion. In conclusion, I think Zone 5 is a great campaign for the F14 Tomcat.

I thought so, but wasn't sure. Thanks for the clarification.

Which waypoint of the Jester nav wheel corresponds to the waypoint DP given in the missions? Is it waypoint MAN?

It seems I'm the only one who is having issues with mission 8. SPOILERS FOR MISSION #8 AHEAD! For me that Mig is coming out of nowhere. I can't get a visual (I'm in VR) and the player only has a few seconds from been alerted to going KABOOOM. I'm not even sure whether a missile hit me or I got destroyed by some sort of a mission timer. I tried this mission twice but absolute no luck. By the way, this mission (and I think another one or two in the campaign) are very fps heavy in VR to say the least (I think at least one of the culprits are all those fires on the ground). Otherwise I think it's quite a nice campaign (having played past mission 8 yet).

I also just finished the campaign. Overall, it was a great experience! Perhaps the best campaign in DCS I've played so far. But I agree with tsgucci that the first mission was indeed a bit of a shocker. I initially thought this campaign is going to be a chore heavy, trigger hunting sort of adventure. Boy, was I wrong. What followed was just, for the most part, entertainment of the highest level. Only mission 11 was a bit too long for my liking (which doesn't mean that mission was bad, far from it!). By the way, I really appreciated that with each mission briefing comes an estimated playing time. This is very helpful to assess whether there is still enough time for another mission before calling it a day. This is a campaign I would wholeheartedly recommend to anyone who wants to see some action in the F14A. I really hope to see more campaigns of this kind in DCS! Great job, Reflected!

Lucky me I got shot down by the fighters after playing the whole mission up until then without time compression (I kinda knew this was coming...). This mission certainly gives the player a taste of real world CAPs. Personally I would have preferred this mission to be somewhat shorter (it took me almost 2 hours, including doing the AAR, until I went BOOOM - GAME OVER).

Oh boy, I didn't think of that! And this did the trick. Thanks for the advice. Now with mission 1 completed, onwards toward mission 2!

Thanks for your reply. I did hit the 7nm (Jester told me to take a turn). He also commented on my landing). How am I suppose to request launch from the crew again? (I did check the comm menu but didn't notice anything out of the ordinary).

So what about mission 1? I made the first trap and that was the end of it. Taxing back to cat 1 did nothing for me, as the (supercarrier) crew were just standing around twiddling their thumbs. Am I missing something?

Well, for me this update completely wiped out my hotas setup for the Hind! Was that necessary?

Would be nice if the player could tell Petrovich which kind of target to prioritize when searching. For example, been able to tell him to "search for AA threads" would be really helpful.

You can very easily make your own mission like that. You just have to set a trigger that will start playing an OGG format audio file. I actually did that with the Huey, where the music starts with the start of the mission. Flying the Huey at sunset in VR while listening to all those classic Sixties rock sound tracks is an amazing experience!

I'm also having performance issues with 2.7. in VR (Rift-S). What helped me quite a bit was switching from Steam VR to Opencomposite and Oculus Tool Tray. OTT Default ASW Mode set to 18Hz. That may seems to be a very low frequency setting, but fps appears to be MUCH smoother now. Any Rift/Rift-S may want to give it a shot. I also use an older Nvidia driver 457.30,which is said to perform well with DCS: NVIDIA DRIVERS GeForce Game Ready Driver WHQL My spec: i7-8700 RTX2060 32GB Ram

I got lost after been asked to check in with ground for taxing. According to the kneeboard, I'm supposed to be on CH3 (G) and CH1 (R). Trying to contact Nellis via comms menu, I have to ask permission for engine start-up, but no response whatsoever. Am I missing something?

Thanks for the confirmation and upcoming fix.

Same problem here. I got all the radio chatter from Ghost and Cheavy 5-1 while hanging around WP2. Once I turn towards WP3 (after been cleared in hot), no more comms except players voice. My radio settings are Green CH3 and Red CH1. Checked both with simplified radio comms ON and OFF under options, which made no difference.