Strikeeagle345

you are correct.

the fixed file has been uploaded in the F-14 bug section. page 2 or 3.

probably both.

TACAN is working fine here as well.

ED probably changes something and HB was unaware. So when they sent over their working build, it was broken when integrated into the new DCS build.

I understand what you are saying, however, you are not flying the E-Bracket at that point since you are on speed. You are watching you VV and decent rate approaching the groove.

*you then use throttle to move the VV up and down to correct your altitude / rate of decent. :thumbup: E-bracket doesnt move as you have trimmed for AoA.

Tomcat tracks don't work anyway. Would be a waste to upload one.

100%, if your speed changes, so does your trim. :thumbup:

Good on Virpil. Smart move, beat your competition to the punch because they want to lolly gag.

I just built a new system, specs below. The MSI MPG's are a nice series. I have the Gaming Pro Carbon, 32 gb of Gskill trident RGB RAM. I purchased a Corsair H115i Pro, and with the 9700K overclocked to 5 ghz, my temps barely hit 60*C. Its extremely fast and boosted my DCS performance WAY UP. Next on the to do list is a better GPU. Also, the MSI board has an easy overclock one touch button, going with a water cooler like that, you wont burn up your CPU. motherboard https://www.newegg.com/Product/Product.aspx?Item=N82E16813144212 RAM https://www.newegg.com/Product/Product.aspx?Item=N82E16820232748 Cooler https://www.newegg.com/Product/Product.aspx?Item=N82E16835181138

it's not supposed to move. Also, when on the Carrier (or during Carrier Ops), you do not use the Taxi / Landing light.

there are two versions of it, one press will give you true airspeed, the other will give you indicated, the thirsd press will turn it off.

I believe you can in the settings under gameplay, but I could be mistaken.

Getting a new GPU will help, but keep in mind, DCS is very CPU dependent. So you will only get so much out of that GPU before you CPU becomes the bottle neck, and your GPU is waiting on your older CPU to feed it.

:megalol:

you can tell jester to select things for jettison.

its pretty much complete. It really only missing the TARPS pod and some minor Jester functionality (which a real RIO fixes).

https://www.dafont.com/usn-stencil.font

Make sure you did an alignment and set the INS knob to NAV. This is what is causing your issue.

You are thinking of 204? The images you are seeing just have poor color settings or something.

real one was dark blue.:thumbup:

The XMP profile is what did it. Your ram was running way slower than 3200.

yes, its a WMR thing for some reason.