key_stroked

Not being able to program it with weight on wheels is a bug.

I'm getting it in Nevada with 20+ C temps at around 8,000 feet with no visible moisture or significant weather. Never seen it before this patch.

No it shouldn't. You shouldn't sacrifice functionality for the sake of "what the real jet looks like". My 2D computer monitor doesn't accurately depict what real life looks like. Line needs to be drawn between usability and realism.

Another "the HUD is too dark" thread The HUD is too dark, and I'm not basing this off real life pictures. I'm basing it on the fact that in the sim, I cannot see stuff in front of me unless I lean to the side so I'm not looking at it through the HUD, especially at dusk or at night. I don't really care how dark or not it is in real life. I care mostly if I can use the HUD to see stuff when it's dark outside, and right now I can't. Maybe the developers can consider adjusting the tint so the HUD is usable at later hours in the sim? Some comparison screenshots: Looking at a 737 flying over the Vegas strip at dusk. (Looking through HUD) (Looking without the HUD) On the runway at Nellis during night time. (Looking through HUD) (Looking without the HUD)

Can confirm TACAN is bugged. I was practicing approaches into KTNX (Tonopah test range) on Nevada last night, and I was tuned to the Tonopah TACAN (TPH). Twice the range stopped updating and the location of the TACAN was "frozen" on the HSI. Switching to another TACAN frequency and back is the only way I can force it to update and display accurate range and bearing info.

Bueller?

http://www.designation-systems.net/usmilav/jetds/an-aw2ay.html#_AWB

Has ED seen this thread? I see lots of threads being tagged with "Reported" or "No Bug".

One example is the final turn to enter the groove for the carrier. You don't want the VVI and E bracket to be off hud. You need to see both to maintain proper AoA and speed.

I'd still be interested in hearing from the ED team on this.

Sorely needed.

1. They felt that players wouldn't be able to see the HUD symbology during the day if the HUD wasn't tinted. It's not a realistic tint...but that's what they did. 2. The F-18 doesn't use VOR. It uses TACAN. ADF is a completely separate thing. 3. What exactly doesn't work?

He probably means the F10 map. It's known that aircraft heading is 7-8 degrees off from the F10 map heading.

No.

Where does all that info come from?

According to - http://navyaviation.tpub.com/14313/css/Lau-115-Series-Guided-Missile-Launcher-98.htm - the 115C is heavier and has a jettison adapter.

That makes more sense. Afaik the version we got is a 2005 era F-18C.

Ok..even if it actually is the heading indicator, there is no course line/arrow or deviation dots showing near the VVI. All I see are the ILS needles. And even if what you say is true, then how would you explain this video? It's also a super hornet, but there is no heading indicator on the HUD compass tape when the boat's TACAN CSEL course line is showing both in the HUD and the HSI: I took a screenshot of the video right before he finishes his last turn into the groove. Here's the original resolution: Here's a zoomed in version with labels of what I think the symbols actually are.

Looks like the ILS needles to me near the VVI, not the course arrow and deviation dots. And the top looks like the heading carrot for the heading tape. That isn't the thick line that shows direction to a TACAN source or a waypoint. And as someone else said, it's not even the same jet. You're trying to prove a point using pictures of a completely different jet, and the picture doesn't even show the symbology that everyone else is referring to.

Including screenshots to show the behavior of tanker TACAN. As a reference, the carrier TACAN, which is set to 55X, works correctly. T/R and X are both selected and the HSI/HUD gives bearing and range info. But tanker TACAN will work even if one of the two conditions (A/A and Y) is not met. The tanker was set to 22Y in the mission for these screenshots. In this screenshot, I set the Y but I did not select A/A, and I still got a bearing to the tanker (but no range). Here I correctly set A/A but I left it on X, and I still got a bearing (but no range). When selecting both A/A and Y, I get both range and bearing. Afaik, I should not get any bearing info if I don't have both A/A and Y selected at the same time.

I'm running the Open Beta of 2.5, and before yesterday's patch (https://forums.eagle.ru/showpost.php?p=3519335&postcount=13) I was playing the Operation Piercing Fury DLC campaign on the A-10C module just fine. I just tried to continue it tonight, and I get this: I checked the FAQ, which says the following: I'm not running any shader mod. My installation is 100% vanilla. I don't run a 3rd party firewall. I don't use antivirus on this machine. Nothing changed between the day before yesterday and today except installing the patch. How do I fix this?

Is this normal behavior?

Works for me.

Cool thanks!

Any info on this?