WOPR

Try holding power on for a little bit longer.

I agree with your experience. I tried the Tobii 4C for a short while, but I exchanged it for a TrackIR. The Tobii 4C works exactly as advertised, but the integration with DCS when I tried wasn't as mature as TrackIR and a couple of limitations were too much for me. First, the fact that it tracks your eyes means scanning your screen also moved the camera unless you turn off the feature. For me this feature is undesirable, and probably is for anyone with a large monitor. Second, I couldn't set it up to let me look directly aft. I also tried using some 3rd party software and just couldn't make it work the way I wanted it to. With products like this, the hardware is really only about 1/2 the product. If the software isn't designed a way that gives you the absolute correct functionality or doesn't allow you to fully customize the functionality satisfactorily then the hardware will never live up to it's potential. I'm not saying don't buy the product, or that it is junk. However, you should consider these limitations before buying. You might still prefer the Tobii 4C over having goofy looking kit on your head all the time.

Thanks.

Can someone explain what "Quicksteer function enabled" from the update news means? I can't find information on anything related to "quicksteer" in the pocket guide or NATOPS manual.

I noticed this earlier, but then the target faded. Some of this could be the target fade timer. The contacts on the ground sounds like something else though.

I've had this work, also "push and hold" has worked, but nothing seems to worked consistently for me yet.

I'll be sure to try out this switch. I think the main thing is the bleed air switch. When I had trouble, I bleed air warnings on the HUD repeater, but didn't realize what they were at the time.

I appreciate the curve setting tip, but the afterburner deactivation point is what I'm really trying to understand. Burners don't activate until I hold 100% throttle for a short while, but the cut off point is around that half-way point on my throttle. I've also just noticed that the cut off point seems to vary with altitude.

When I tried the external wings for the first time, fuel was consumed from internal tanks faster than the external wing tanks. Is this supposed to happen, or are there a some cockpit switches I neglected to use? UPDATE/Pro-Tip: Making sure your bleed air valves are not closed seems to solve the problem.

I've been trying to adjust throttle curves because I noticed I have to cut my throttle to 40% to 50% max before afterburner cuts out. Then as long as I don't go back to afterburner throttle control is normal for mil power. The question: Is there supposed to be hysteresis on the throttle for afterburner control?

Cold & DarkTutorial Plays Chinese Sound Track for OBOGS Step In the cold & dark tutorial, the Chinese (I think) sound track played for the step that told me to turn on OBOGS.

Seems to be ok in multiplayer, but it definitely wasn't doing anything in a single player misison. This bug may belong to the journal of unreproducible results.

True. I'm not sure how to check to see what the MQ-1B is lasing though.

For me, MAP: Persian Gulf, and the MQ-1B (Predator) was lasing.

I can confirm this report. I just checked in single player to be sure, but I have also seen this in multi-player.

I'm in a single player mission, haven't cross checked multiplayer, but I suspect this is contributing to SAMs being way scarier when I'm in the AV8B vs. the A10C. Chaff is just flat out not dispensing when I use the default keyboard binding, 8, or when i used my mapped, and verified HOTAS button. All dispense doesn't dispense chaff either. I can't see it dispense and the chaff stores counter doesn't decrement. Please fix ASAP.

I've had bombs detonate on the pylon when the fusing was set to IN. The solution was to set the fusing to D1.

I'm not able to tune the radios to 30.0 MHz using the UFC. I can tune to 30.1 MHz, but no lower. The RADIO SET CONTROL panel will let me dial it all the way down to 30.000 MHz.

I discovered today that V/UHF RADIO SET CONTROL can be used for somethings, so I thought I would share since it is not in the guide yet. To use this radio (Panel 2 in the guide) you have set the switch on the ACNIP panel to MAN from UFC (panel 3 in the guide, just below the VRSC panel). The switch appears to override COMM 1. The left knob controls functionality. TR = transmit/receive on the channel shown. TR+G = transmit/receive on the channel show + listen to guard channel (emergency channel). ADF = automatic direction finding (doesn't appear to be implemented yet or I haven't figured out what dial to look at). The right knob is the channel selector. PRE = pre-set channels. MAN = manual tune. I was able to tune the VOR at Al Minhad AB (PG map) and listen to the Morse code, but otherwise couldn't make use of it.

The AIM-120 AMRAAM is the follow on to the AIM-54 Phoenix missile. So while the F-14 won't get the AMRAAM, it's still gets a very long range engagement air-to-air missile. There's a nice Wikipedia article on it, and a little bit extra on the 14's targeting capabilities. Wikipedia Link

This a great intro to the Hornet cockpit. Thanks for doing this.

I did some digging. If I change the reference marker to VORTAC it works with TACAN. I think the issue is that DCS or modules don't simulate VOR usage.

Bump. I realize this is an old thread but it seems like it's applicable. VORs in general should be able to be used by an aircraft only has TACAN. See the link. Link to TACAN to VOR mapping Al Minhad AB (Persian Gulf map) has a VOR DME station on 115.2 MHz/99X near and inlne with the threshold of runway 270, however, I'm not able to pick it up with the TACAN in either the AV8B or A10C (while in flight). It would be real nice to be able to use all TACAN capabilities on all maps without mission designers having to add anything.

Thanks for pointing this out.

It's a little hard to time a screen shot on this. Basically both beacon lights reflect heavily off the cockpit console in daylight. It's almost as if the light is ignoring the fact that the fuselage is in the way. I've only been playing the PG map since it was available, so I have no idea if this is only true on the PG map.