Kreutzberg

I'm enjoying the new waypoint designation functionality. In the first mission of the Frog-7 mini campaign, waypoint 5 is preset as the VIP, which was a very intuitive way to learn that process. I wanted to designate waypoint 8 as IP and especially waypoint 9 as the target, as that would be a good way to tell that it's coming. However, the waypoint designation sub-menu only goes up to waypoint 8, and I don't see any way to get further. It also doesn't advance with the flight plan. In the attached screenshot (sorry for the low resolution--it was in VR), my current waypoint is 4, but I still can't get past 8. Is there some way to do this that I'm missing? Or perhaps a future feature? Thanks!

The other day, I noticed that the PAPI lights on the Syria map are quite dim even in 2D (see image). Some things like IFLOLS are much better in 2D than VR, but it seems like there may be a bigger issue. This is one of those core things that probably wouldn't be tough to fix but really hurts immersion.

I picked up the Kola map in preparation for the upcoming campaigns. It includes an F-4E mission, Red Dawn. I thoroughly enjoyed the whole experience. There's nothing online about this mission, so I figured I'd extend my recommendation. The operations from a Finnish highway airbase is quite engaging, the nuclear delivery profile is a lot of fun, and there's an interesting twist after. The nuclear delivery pairs well with the training mission from MiG Killers, which I would recommend before trying it under much more difficult circumstances in Red Dawn. My only piece of feedback is that it might be worth including the maximum height in the briefing. On my first attempt, I figured something like 500 feet was pretty safe, but definitely triggered the MiG 23s. I looked up the trigger in the mission editor and pushed hard to stay below 100 feet AGL to do it successfully (I actually thought I breached it so may have gotten lucky!). Thanks for the great mission!

One other note about engine sounds--I've noticed that while flying in external view, there are some oddities with the sounds depending on the camera is. From some angles, the sounds nearly disappear (nowhere near supersonic speeds). Thanks for continuing to improve the module!

Thanks for the continued improvements to this map. I definitely think it's the best out there for DCS, and I'm looking forward to exploring all of the new helicopter landing spots especially! I note that PAPI lights on this map and many others are quite dim. The issue is most noticeable in VR, especially with a high resolution headset. But they're pretty dim even in normal 2D (see picture). The PAPI lights are much brighter on the Caucuses map, and on Runway 32 at Groom Lake on NTTR (but not elsewhere on that map, which is odd!). That suggests there is a way to do that--would it be possible to implement something like that? Thanks!

Completely agree!

For sure--sounds like an AI thing more than anything else. Thanks for taking a look!

Thanks for all your work with the F-4! I'm looking forward to starting MiG Killers, but in preparation, I was doing the included missions. On your Covey 41 mission, the FAC can give two targets. Every time he's given me the beach (probably 4 or so times), I've attacked. Then, my wingman lines up like he's going to attack but doesn't drop. He'll then go around and do the same thing. Therefore, the mission isn't progressing. The issue does not seem to occur when the target is the hill, but I've only had that once. In that instance, everything progressed normally (but the MiGs got me--I need to work on those BFM skills in MiG Killers!). Here's a track (not my best procedural effort, just a quick and dirty to show the wingman's behavior). I've done things like actually hit the target and wait for the smoke before, so I don't think that's it. Are others experiencing this? There are videos online of it working, but likely from before the most recent patches. My best guess is that some recent AI change messed up the wingman's attack. Hopefully an easy fix. Covey 41 Wingman Stuck.trk

Thanks, guys. Good to know that this is meant to be more of a graduate level series!

This is about the Red Flag missions, by @Sedlo, that are included with the module. I'm having a ton of trouble, especially on the first one. In most cases, it seems like fighter sweep is not very effective. I usually wind up being bounced by quite a few enemy fighters before I even get to the objective. I've tried hitting the push time perfectly, delaying it to give more time for the fighters and everything in between, but the enemy SAMs and fighters seem to really beat up on the friendly fighters. From watching the videos of this mission in other modules, it doesn't seem like the player is supposed to do much air to air before the strike, but I wind up fighting enemy aircraft nearly every time (I ran out of missiles one time!). I've had more success with mission 2, but largely because my friendly forces do a better job. It's tough to maintain situational awareness in the F-4. That's probably more to do with the limitations of 1960s technology. I'm hoping that my skills will get better on that front, that the radar/Jester may improve, or perhaps even that DCS's AWACS calls will get better. Am I missing something obvious? I don't get the impression that these missions are supposed to be quite this difficult!

@Dominik96 It looks like the VOR issue is fixed in yesterday's patch, probably the following: Navigation: Fixed VOR showing true instead of magnetic bearings. That's a really interesting, bug, actually! Thanks for addressing it!

This appears to be fixed in today's patch, 2.9.7.58923. I checked easy communications and mirrors, though not everything listed by @Drewbacca!

Thank you--glad to hear it's not just me! I haven't been using mirrors so am not seeing that part of it. Disabling the launcher for now definitely works.

I think this is only since 2.9.6.58056, but it could have started earlier. Whenever I start DCS, the "Easy Communication" box under "Gameplay" is checked. I can uncheck it (and hit OK) and get regular communications, but restarting DCS results in that box being checked again. Some missions don't work at all when the box is checked, even when using full communications procedures. Are others encountering this issue? Thanks.

Great--thanks!

I'm eagerly looking forward to the MiG Killers campaign (even featured in the newsletter this week)! One thing I've noticed with your other F-4E missions is that the radio voices (and other sound effects) are quite loud. Turning down helmet volume low enough to be comfortable then means I have a hard time hearing jester. I'm hoping the MiG Killers campaign won't have this problem, or there is some other good workaround. Do you have a recommended volume setting for your missions? Thanks!

Thanks for the information! Glad to hear that the track will be helpful with the VOR/TACs. That makes sense as well regarding ADF. I followed the manual's instructions and set up beacon. Under the right circumstances, it also points to an ATC station, but only when it's actually broadcasting!

Thanks! That does make sense--some frequencies won't even input. However, what types of signals can be navigated to? I've tried things like ATC from the F10 menu and am getting the same issues (though I may still be doing something wrong!).

Yesterday's patch had some quad view issues, which I understand are being worked on. However, the long term answer to these issues is a more robust implementation as mbucchia described above, and quoted below.

Thanks, Heatblur for this great module! I have some questions about navigation with VORs and NDBs. The navigation computer and TACAN are certainly the primary way to navigate this plane (and they work quite well), but I would like to understand the alternatives! There might be bugs here, or just user error, so I would appreciate any feedback. I have done some searching but am not finding these specific issues. I also waited until today's patch to make sure they weren't just fixed, but everything is the same. For VORs, my understanding is that they should basically work just like TACANs. For the most part, they do, but I'm seeing some weird anomalies. For example, on the Nevada map, where we have VOR/TAC stations (which are both VORs and TACANs), dialing up different frequencies results in different bearing pointers and different radials. I'm including a track with this one, locking onto the TPH VOR/TAC with both systems showing the different results. For NDBs, I'm struggling to get any reading at all. When I dial up the beacon's UHF frequency, I can't seem to lock onto it with the bearing pointer in ADF/TAC mode. I've tried all sorts of permutations with front and after cockpit radios both set to ADF and the correct frequency, but the bearing pointer just goes to the bottom right. My suspicion here is that I'm just doing it wrong. I don't see a procedure in the manual and would appreciate feedback. Thank you! VOR-TAC.trk

I've been slowly working my way through the default instant action missions for this outstanding module. Today, I flew the Marianas ILS approach mission (a lot of fun if anyone wants a challenge). The briefing for that mission has the approach plate for the ILS with the DME arc, but it would be great to include that plate in the kneeboard for that mission to be able to refer to it. I note that the other instant action missions don't seem to include plates in the kneeboard, either (I checked the Kadena to Guam mission and the Gazipasa LOC landing on Syria). It's of course possible to manually add them as kneeboards, but the best option would be for them to be built into the missions. Thank you!

I did try with the generator switches and still outpaced them moving the switch quickly. That being said, I do think it's the animation speed, as I used Virgo47's solution, above, and it works (for what it's worth, I got it all the way down to 60 ms, so I don't think you need 600 ms). Thanks for that idea! I also took a look at the clickabledata.lua file. I'm not seeing a flaps setting, though it might be included in something more global. If that does work, though, I would be concerned about it resetting every patch. Perhaps this could be something included in a module setting? For hand-thrown switches, instantaneous animations might be a preferred option for a lot of us. Thanks, both!

Here's a screenshot of what I'm using. I should have said originally as well that it works completely as expected if I move between the positions a little slower. It's only when rapidly moving from Norm to Out&Down or from Out&Down to Norm quickly that seems to confuse it. But perhaps there is a better way to bind it. Thanks!

I'm running a VKB STECS Max and using the three position lever for flaps. I have it set up for instantaneous pulses at all three positions. However, if I move the lever quickly, the F-4E only registers the center position. Therefore, if I quickly move from full flaps to no flaps (or in reverse), the module is leaving flaps centered. The only other module I have with three position flaps is the F/A-18C, and it does not have this problem. I suspect it's something with the way the flap lever is coded to prevent inadvertent movement, but it seems to be blocking intentional settings. Thanks!

I'm working on the F-4 and am trying to find a really good airfield with working PAPI lights to practice getting on the glide slope. How are the PAPI lights on this map? I note that they are specifically advertised in the description, so I'm hoping they're good! The lights in the Caucasus are quite visible but at the wrong glide slope. Most of the other maps are more accurate but are very difficult to see in VR. Thanks!