Revelation

In that case, ED should delay the EA release for a year or more so that they can make sure every little detail is correct at the start of EA.

Again, the question was does it matter if it is fixed prior to EA....

Does it matter?

CV1 leaves a lot to be desired. You cannot expect magical improvement in visual quality when the headset itself has such a low resolution. I went from CV1 to Index and the difference is astounding.

With the Index, the MFDs and AMPCD in the Hornet are easily readable. I can only imagine the Reverb is even better.

Did that already, no luck. Button 9, or down on the middle hat doesn't even make the click sound when it is pushed downward.

Got mine today, but button 9 on the middle hat switch is not working.

I'd personally go with the x570 so you can take advantage of PCIe-4 SSDs/NVMEs....

7/19/2019. https://www.facebook.com/eagle.dynamics/videos/492074028001468/

Even the aircraft's anticipated release date can slip. It all depends on if it is in a state ED deems appropriate for release into EA.

You can do that with static objects.

I did not enable any FPS counter. It "felt" better. With very fast head turning I could get a tiny bit of tearing. That is with a PD of 1.8 in DCS and default of 100% in Steam VR and at 120Hz. It feels smoother than the CV1. That could just be a placebo as well at this point in time.

Have you input the correct altitude of the target? Can you post a trackfile so that we can see what you are doing and possibly offer additional assistance?

In addition try forcing your Index to run at 90Hz instead of 120. Depending on your computer 90 may be easier for your system to run than 120.

I an second all of these points. This headset is simply really impressive. Full disclosure: I have not tried the Rift S yet and at this point in time I don't think I will. This is the experience I have been waiting for in VR. The CV1 was pretty impressive, but the Index is like going from 480p to full HD. That is how big of a jump it "feels."

It can be that easy. Based on the old posting back in 2015 showing a Pulse-Doppler radar scan they chose to go the route of simulating a radar actually detecting things on the ground and rendering those returns on the MFD. This is a more authentic experience and it would make it much easier to simulate/emulate radar jamming in the future should ED decide that they have the resources to devote to such an endeavor.

Okay, one word.... Amazeballs! Every text in the cockpit is easily readable. The HUD is crystal clear. I can see ground targets as high as 20k feet. Roads, buildings, airports, etc... are easily viewed and pretty damn clear at 35k feet. (Haven't tried higher yet) I left all of my settings to what I had set for my CV1 for this first test. I am now going to start tweaking things specifically for the Index.

I got my Index today, so it is time to set things up and give it a whirl...

The Hornet has a lot of features added though it still has a ways to go. Major Hornet updates are down to once a month as the features/systems they are working take longer to code. Just download the latest Stable or Open Beta and you will be fine. Changes to modules and the core DCS World can potentially corrupt a previous track file. In fact you should always save a previously created mission in the ME after ever update. We don't know much about the Nimitz. We have seen, recently, info on the deck crew and carrier comms. The Nimitz will be a pay-for-DLC.

Both, we also have the BRU-55 for the JSOWs and GBU-38s.

Trying out the JSOWs I found a bug. After inputting the coords for 4 separate targets I reach the Max Range to drop the first munition. Upon pickle, coords for all for PPx were immediately erased. Track "JSOW_Bug.trk" is attached. JSOW_Bug.trk

If you are following their directions then you wouldn't be "about to run them over."

Maybe you need to grow up a bit. You weren't lied to. ED stated their plans and ran into a bug. You would be the first one with tiki torches marching in the streets spouting vile something-or-others had ED released the update anyways with a major bug or 2.

Well remember that Wags was at FlighSimExpo this past weekend so he most likely did not have time to work on such a video.

Updates, historically, have landed around 10am EST. They have come before and much later in the day (US Time) though 10am is the "norm."