key_stroked

Is this going to be fixed in the next patch?

I thought we would have had some by now. The Persian Gulf map has been out two years.

I decided to create a fast mission tonight, chose CAP as my task, and the game gives me a bunch of Rockeye cluster bombs....no AA missiles. I decided to create a basic fast mission without using the advanced part, and once again I'm given the CAP task with the exact same cluster bomb loadout. Doesn't seem to work well.

Which specific FOV is this button supposed to manipulate? Rather than affect the FOV of Mavericks or sensors, it appears to actually re-cage the reticle in its default position. Is this intended? The only other uses I've found are undesignating targets and holding it down for tight nosewheel taxiing.

To me, the colors from your RL picture look exactly like the colors from the early VDI (the leftmost picture in the OP). The color tones we have now in DCS don't seem to match that.

It's not embarrassment, it's called learning. Leave the thread and share the information for others who might run into the same issue you did.

Specifically this video -> I like the more digital look of the VDI in that video compared to the CRT type screen we have now. I know the cockpit in that vid was an early and unfinished version and what we have now is considered more realistic....but as far as aesthetics go, I prefer the more squarish, "cleaner" VDI with the brighter lines and text. I know it's unlikely, but could the earlier version be made as an optional "skin" in the specials section of the DCS options menu?

Cool, thanks.

It would be great to be able to bind volume knobs to rotaries on my HOTAS, or even the brightness knobs for the HSD, HUD, and VDI.

This is from the latest patch (2.5.6.50979). I took the Instant Action "Carrier Quals CVN-73" mission and ran it during the day. All deck crew textures show up normally. But if I run the mission at night, all the blue shirt deck crew have their brightness turned up way too high.

I got the same thing today...except for user mods: - Navy Equipment 1.3 - VPC-Airfield Equipment 0.9.4 beta I have never had this message pop up for these mods until after installing the last patch (2.5.6.50979)

I've used SEC when practicing air starts, as per some air start checklists I found on the ED user files section of their website.

I'll be honest. My patience is gone. Not with Heatblur, but with ED. They don't test patches, and they keep breaking fundamental systems that 3rd parties rely on for their own products (the lighting system as an example). I'm glad you guys are fixing your stuff, but I can only imagine what next week's patch is going to break. Done playing DCS (and unfortunately your F-14) and done installing patches on patch day until things change. Hopefully next week we actually get to use DCS without huge game breaking issues. P.S. I wish Heatblur wasn't tied ball 'n chain to ED and their patching process, because this straight up sucks as a customer.

I asked about this in November of last year, and I was told this -- https://forums.eagle.ru/showpost.php?p=4119689&postcount=2

It can't. ACLS stands for auto carrier landing system. The I stands for Instrument. You still have to fly the plane yourself using ILCS.

What happened to the hotfix for the cockpit lighting? The patch status is now showing June 10th for the next update. https://forums.eagle.ru/showthread.php?t=273255 We were supposed to get it Friday, but now we're not getting it? HUDs and other essential cockpit lights are completely unreadable. Why are we being made to wait until Wednesday?

Heatblur has always been A1 since the launch of the Tomcat. I originally posted this asking here if it was a Heatblur issue, because all I fly is the Tomcat. I don't fly ED's modules, so I didn't know their stuff was also effected and it's on them to fix it. Keep doing what you're doing. Let's all hope ED can start doing some meaningful beta testing to catch this stuff before pushing the patch out.

Np! Thanks for looking into it.

Nevermind...that one seems to work.

Bad link.

How does stuff like this get by the testing team?

Might wanna give people more time than 6 minutes to check forums for new posts. Re: your photo, it definitely looks brighter, but even though the picture is super grainy, I can still make out numbers on some of the gauges, like the altimeter. After today's patch, the lighting has gotten worse. Now I can't even see the labels for my ACM buttons in the daytime. And just as a comparison, this is what the RIO position used to look like before the lighting got all screwed up. This is how it looks as of today. The red flood is set to dim, the lowest it can go before turning it off. For those in the thread trying to argue this is realistic....I can only shake my head at you. I don't care how realistic this is, it looks awful. I can't read gauges. If you're fine with how the lighting looks above, that's cool. But Heatblur doesn't agree with you, and hopefully it gets fixed sooner than later.

I've never heard my AI wingman say bingo fuel. They just fly until they run out and crash with no communication. ED has dragged their feet on fixing AI. It's pretty tiresome.

If I'm in single player, my TACAN range will update normally on the backup compass (Bearing Distance Heading Indicator). The hundreds, tens, and ones place all update as shown (153nm in the screenshot). https://imgur.com/8uAJVZO In multiplayer online, only the hundreds and tens places update. The ones place remains a zero, despite the HSI showing the correct distance. In the second screenshot, I'm at 7.8nm from the boat, but the backup distance shows 000. https://imgur.com/hx64N56 I extended out to 12.8nm, and the backup then showed 010. https://imgur.com/xcmtUnd I've triple checked the TACAN is on, set to TR, set to the correct frequency, and is set to pilot. If I set the TACAN source to NFO and tell Jester to tune TACAN tac freq to the boat, I get the same issue. The only difference between the single player and online sessions was that the single player plane was a hot start, and the multiplayer plane was cold started. Is there something I'm missing?

The way I always understood it was that the Sparrow can't guide itself. The missile uses targeting supplied by the aircraft's radar. If the aircraft loses lock, the missile loses its tracking but continues "listening" for another lock if the aircraft radar locks onto something else. To my knowledge, the Sparrow doesn't have any radar onboard the missile, which is why it's classified as Semi-active. IronMike made it sound like the missile behaves like an AIM-120 would, which does have onboard radar.