Roosterfeet

By "hangs," you mean you can't advance the mission or DCS freezes and won't respond? I just flew this using single thread in the current OB without skipping the first part of the mission and it worked fine for me. Pretty sure I used the \ key to bring up the coms menu to select F10. You might check your key bindings to make sure nothing is conflicting with the coms menu or F10. Assuming DCS isn't crashing, If you start the mission from the tanker, and quit after encountering the problem, your track file might be small enough to post here which could be helpful. Also, if you find your way past that issue, It's probably best to do everything yourself so Smoke doesn't wander off to Iran.

It would be great to have more moving map resolutions supported by DCS aircraft. For instance, the F-18 can only display the map when the HSI or SA page is set to 10 miles. The map is blank at 20 and 40 nm.

This is a constant headache for third party campaign creators and I suspect that the only real solution is for ED to get serious about the Stable version being an actual stable version where the AI has been thoroughly tested and works as intended so that the missions they sell don't break. Right now stable is in no way more reliable than the the open beta; it has fewer features and the bugs are older. It's no wonder that everyone ignores "stable" in favor of beta.

Well, nevermind. Found the answer in the readme in the config/views folder. "Your local changes should go to C:\Users\<YOUR PROFILE>\Saved Games\DCS\Config\View\" Works great.

I've been trying to customize my labels by editing Labels.lua in the DCS install directory. Is there a way to implement this through a file in the saved games folder so I'm not messing with files in the install directory that may be overwritten when updates come out?

I wish you would post a video or a tacview. I've spent many hours trying to get past those Fishcans without success. Edit: was able to pass by rearming with 4 mk82 in the tunnel, 3 winders, and a sparrow. I would still really like to see it done properly.

WP2 is at the very edge of the Retreat trigger zone so flew it again and kept a close eye on the Red aircraft in relation to WP2. They never got close. Blue AI absolutely demolished them without any help from me. It's the first time I think I've seen an improvement in AI break a mission.

I opened up Mission 7 in the editor and it looks like at least one Russian aircraft has to reach a trigger zone called "Retreat" southwest of WP2 in order advance the mission. I think we may have downed them all before they got there the last time I played it. I'll have to give it another shot.

Anyone know how severe this is in today's patch? Known Issues: FPS hit with many bullet impacts over time

Ran into a couple of issues replaying this in 2.8.3.37556 single thread. Mission 6 - Labels are forced off. Mission 7 - Failed to progress after intercepting the Russian gorilla group. I can't be sure if a red aircraft escaped or not since they are apparently set to hidden.

Couldn't resist.

Happy to report that the black flashes at sunrise and sunset are gone in 2.8.3. I still get occasional random black flashes with mirrors enabled, usually around the boat, but it's rare enough that I can't reproduce it in a short track.

Multi-Threading is promising but still buggy. I honestly think Scale GUI is the best new feature. It's about time. Without scaling, 1440p + middle age = Eyestrain Headaches.

Just flew this this morning and was able to get Elvis to refuel. 1. Form up on the tanker 2. Contact tanker and send "Intent to refuel" 3. Order flight to go to tanker 4. When wingman is done send "ready precontact" The only problem that I ran into was that Elvis took all the fuel. I only got 1k before the tanker retracted the drogue and turned for home.

What's the current thinking on Windows 11 vs Windows 10 for DCS?

If you're having trouble getting ILS needles, check to make sure the AN/ARA-63 ILS power switch is on. I came back to the Tomcat after a long break and it may be faulty memory on my part but I think it used to be on by default.

I found the carrier in 12 but I cheated by using the radio. You can't actually call marshal but your built in pilot will say distance and bearing from mother when you make an inbound call, even if you're on the wrong frequency. Whenever I fly with stock wingmen, I keep track of their fuel like that too. As far as I can tell, "low state" is always the lowest fuel level in the flight.

Not going to make the next open beta I take it? Trying to decide if I'm going to refly part 1 this weekend.

Ugh. The north bandit ignores Paco and comes after me straight away. In multiple attempts, I have no trouble killing the south bandit but the north bandit's missile usually hits me as soon as my sidewinder is connecting with the south bandit. Any advice?

Yep, AI Paco really let me down here. Also, the 9M is pretty useless for face shots so that just compounds the situation. I smell a headache ahead in 15.

EMCON Case 3 actually worked a lot better for me than I thought it would. I set my self up 21 miles and (if I remember correctly) 183 degrees from the waypoint and followed the other aircraft's anti-collision lights to the carrier's lineup light in the distance when it was time to commence. You can actually see those lights in DCS and the lineup light was key without ILS for the first few miles. I was concerned that I didn't have an ILS channel in the brief or on the card but ILS came on a few miles from the boat on the default channel as intended. The hardest part was the same as all pitch-black night landings, no visual horizon makes it really hard to make precise corrections. I was kind of all over the place on the way down but I made it. It was exciting for sure. As for the probe light, check out these threads: There is a great video from a real Tomcat refueling at dusk in the first one. It shows that the real life light was pretty dim but it looks like it did more than what we have in DCS. It might have been enough to be useful in the dark of night. The second thread contains some speculation that it's pointed too far left. Here are some screenshots that I took to show the effectiveness of the probe light in the dark taken a few feet from the hangar back wall. I've included one with the Hornet's probe light on just to illustrate what I was trying to see.

Successfully finished Mission 13 and with a 3 wire no less but I think I lost a year off my life. I feel like we could really use some moonlight in that mission until 1. ED fixes their night lighting, aircraft light sources and possibly night vision and 2. Heat Blur fixes the probe light on the F-14 that points the wrong way. Even with the gamma turned up, I couldn't see the S-3 well enough to get gas. Turns out that little bit of moonlight in mission 3 helped a lot. Then I couldn't see Paco even with goggles on until he was feet from me. I barely avoided a mid air. On the up side, the J-11 exploding right in front of me and the fireball that I flew past looked really cool.

For a long time I've had EGIW show up in both my hornet and tomcat and landing grades. Just now the Speed and Angels told me that I cut power in the wires in my Night Qual landing grade. When I trap I go full mil as soon as my wheels touch and I hold it there until the aircraft stops, at least I think I do. What is the criteria that trips "cut power in wires" in this campaign. I'm trying to figure out what I can tweak to keep that from getting called.

Took control of the track but that did not alleviate the flashing on my system. It continued to flash black at a low viewing angle toward the sunrise. Flashing Black Screen2.trk

Weird. Any idea what that means or if there might be a work around on my end?