eaglecash867

I get a solid 45 FPS (SteamVR for WMR motion reprojection turned on) with only occasional stuttering/ghosting over large cities at low altitude. My settings are here: https://imageshack.com/a/A7xo/1 . The three main DCS settings that affect performance are PD, shadows, and MSAA. But, with the Reverb's higher resolution, you don't need to set PD any higher than 1.0, unlike lower-resolution headsets that require higher PD just to look half-way decent, and actually have worse performance. My Reverb G1 Pro actually performs better in DCS than my Rift CV1 did (the Rift I had to run at 2.0 PD, with 2X MSAA, along with the shaders mod). The higher SS/PD settings that lower-resolution headsets need is a major performance killer, and the Reverb doesn't need artificial help from either of those two things. Since the G2 is the same resolution, I think we can expect it to work just as well as the G1. With a 2070 Super, you'll probably have to run lower MSAA than what I run, but you should be good.

There are beta testers, us. That's why its called DCS 2.5.6 Beta. I have 2.5.5 "Stable" installed as well, so I just go back to that when there's a show-stopping bug. In these threads, we can report bugs, ED changes the subject line by adding [REPORTED], and hopefully they fix it. I think they made Betas available to all of us because with so many of us, we find bugs faster than a small, exclusive group. Looks like that concept is working. :smilewink:

When I had my i7-5960X, I went from a 980ti to a 1080ti, and the performance difference in DCS was like night and day. You may get similar results going to a ti card in VR.

Yup. Got a confirmation e-mail from Connection Business Solutions saying my order has been received and it also gave me an order number.

Pour your PBR into a vacuum-insulated cooler bottle. It keeps it cold, won't spill more than a few drops if you knock it over, and the best part is that the built-in straw makes it so you can drink your beer without having to push the HMD out of the way. Win, win, win! :D

Nope. You don't need the Steam version of DCS. SteamVR is just the interface the Reverb uses for displaying VR from DCS. It doesn't have its own, stand-alone software to run it like your CV1 does. So, when you get your Reverb, you'll need Steam VR, along with another Steam program called WMR For SteamVR. That second program is the sort of "happy box" (heh...that's an official avionics term) that makes WMR headsets like the Reverb run with SteamVR. I know it sounds a little convoluted, but once you get those programs installed on your system, getting DCS to come up in VR is as simple as plugging the Reverb in, waiting for WMR to recognize it and startup, and then starting DCS just like you normally do. So, the process of running it is actually almost as simple as the Oculus software is.

In addition to the memory issue already mentioned, the "vibration" when looking out to the side sounds like it could be that ASW on your Rift S is turned off. If it was running well with your 1080ti, try setting all of your graphics settings back to where they were with that and see if that gives you the same results you had with the 1080ti. But, as I said, the picture looking like its "vibrating" when looking to the sides and down sounds like ASW is turned off. Before you fly, try moving your head laterally and see if the cockpit image "smears". You can also turn on the in-game FPS counter and see if it is locked at 40 FPS. If the FPS counter constantly fluctuates with numbers anywhere between 40 and 80, ASW isn't turned on.

It would help if you post system specs, along with the type of VR HMD you're using. That way somebody with a similar setup can help you with your issues. :)

Yup. At 100% SS you'll be just fine, and then you can tweak up from there as your system and settings allow.

To address your earlier question about the 1080ti versus 2080ti, I have to say that I didn't see a detectable performance difference between the 2 cards with everything else being the same. That being said, I did see a noticeable improvement in the image quality when I went from the 1080ti to 2080ti when I was still using my CV1 in DCS (which might be linked to better performance, but I generally don't look at FPS counters because if it doesn't look good to me, the FPS counter doesn't matter). Its difficult to explain and quantify it, but everything just appeared to have more depth to it. As for colors, that is also difficult to quantify. On paper, the colors are better in the CV1 due to the display type, but the difference in clarity may end up making that unnoticeable for you, like it did with me. Add to that the significantly reduced god rays and significantly reduced SDE, and the color quality becomes even less of an issue. Don't make the mistake I did when using your Reverb for the first time and leave your DCS PD set where it is for your CV1. You'll most likely feel a moment of outrage as you see how horrible the performance is if you make that same mistake. Turn the DCS PD down to 1.0, make sure SteamVR SS is set at 100%, and make sure you have Motion Reprojection turned on in SteamVR For WMR. Start there, and you'll be blown away by the clarity and performance. After that, you can start slowly tweaking your SteamVR SS upward (leave DCS PD at 1.0) until you get a good balance between quality and performance. On my machine, I was actually able to turn DCS MSAA up to 4X, while leaving pretty much everything else set the same (still have Steam VR SS set to 100%) and I'm very happy with the result. I was also able to break away from using the shaders mod which was an absolute necessity with the CV1 running at DCS PD of 2.0. Here's a link to my imageshack album that has all of the settings I'm currently using. Take the Steam VR screenshots with a grain of salt though, since they're old and Steam VR gets changed and updated quite regularly. https://imageshack.com/a/A7xo/1 Keep in mind that the Reverb G2 is due out in just a couple of months, and the hardware is supposed to be much improved over the Reverb G1, so you might want to hold onto the CV1 a little longer. But, when the G2 finally gets released, I would expect that all of the information I gave about the G1 will apply to the new model as well.

No, what he said is not untrue. SS and/or PD are the real performance killers with DCS, and the Reverb can be run at SteamVR SS of 100%, and DCS PD of 1.0, and look leaps and bounds better than the CV1. The performance is also leaps and bounds better, until you start running SS/PD up from 100%/1.0, then at a certain point you will start seeing worse performance than the CV1 which has to be run at at least 2.0 to look anywhere close to what the Reverb can do at its native resolution. Stop telling people that things are "untrue" when you haven't done the comparison and work yourself!

True. The RWR is only capable of estimating range based on signal strength, so the other pilots definitely seem to have a supernatural ability. What I have done to kill other ground targets is pretty much in-line with what Taz said, even with mobile targets. You set waypoints during mission planning which gets you close, then you can hang at distance and altitude to slew your TGP to each of those waypoints and firm up the accuracy by locking and identifying the targets, ranging with the laser, and creating mark points. After that you can start hitting them one by one. The Persian Gulf Strike mission is an excellent mission for practicing the procedures for doing that if you have the Persian Gulf map. It gives you lots of mobile and stationary targets, and they're all in a relatively confined area on an island, which makes it easier to get comfortable with picking out real targets from other ground objects without being too overwhelmed by the sheer size of your search area.

Mudspike? That's a ground radar being picked up by the other pilot's RWR. Is your RWR turned on? Can you see the emitter he's talking about on it? In general though, if a pilot in your flight calls out "Mudspike", you will want to stay as far away from that area as you can unless your mission is to take out a radar or SAM site. Mudspike is bad. ;) If you want to find the mudspike though, put the emitter at the 12 o'clock position on your RWR and just fly toward it. When he lights you up and shoots at you, you'll physically see the missile launch, and there's your target. Killing it before it kills you, on the other hand. That's another story.

Congrats Don! :D You'll see a definite improvement in clarity, but if you really want to feel good about the decision, try this: Fly with the Reverb for a few sessions, then go back to the Rift S for one. That's when you REALLY get a sense of the improvement. Your free cookie is in shipping now. You should get it in 3-5 business days.

Nobody said that. It was simply being stated that 100% was all that was needed for vastly improved image quality over what Don's Rift S is capable of. Of course he can go beyond 100%. Maybe he'll see an improvement that justifies possible performance loss, maybe he won't. That is all subjective. But for a comparison that actually addresses his concern about performance, 100% will get him much better visuals than the Rift S, along with better performance, running at the native resolution of the Reverb. That is not subjective, and addresses his concerns. Personally, I prefer to run higher MSAA as opposed to higher SS, but that's just me. :D

Yup. There generally isn't a cockpit speaker in a military fighter or attack aircraft. All the sound you're hearing is going to be coming to the helmet. If you turn that all the way down in the setup options, not even the RWR is going to be audible. Now, if its working correctly, you should still be able to hear it if you turn the master volume down in the cockpit of the jet itself. Warning audio is generally unswitched audio, and is played at a set volume level based of the type certification of the aircraft. It can't physically be changed by the pilot, and can't legally be changed by maintenance personnel.

I think you're going to end up being pleasantly surprised by the performance, and may even see a performance gain since you won't need any SS and won't have to push DCS PD beyond 1.0. When I went from my CV1 to the Reverb, after getting SteamVR set up properly, I found that I no longer needed the trusty shader's mod, and I was able to turn my MSAA up to 4X. The only thing I turned down in my DCS settings was to go from PD of 2.0, to 1.0, and it didn't need to be any higher than that for awesome image quality. Just speculating of course, but I'm thinking that HP is going to be running all of their pre-orders through that single on-line source. The release of the Gen 1 was such a logistical fuster-cluck, that I think they're trying to get a handle on that with a single point of contact. I think they severely underestimated the response they would get from the VR gaming world. Look like they've learned from it. I hope so anyway. :)

I'm definitely with you on the eye relief thing. Although HP doesn't specifically mention eye relief being one of the goals of the facepad design, they do say that its a more supportive material with a larger contact patch for greater comfort. I'm thinking that will also translate into the HMD not sinking as much into your face so you'll get better eye relief as a result. The larger sweet spot I think is due to both the physical IPD adjustment and the better optics. I know that my sweet spot gets pretty damn small if I don't have my Reverb in exactly the right lateral position. My IPD is outside the maximum range, but I'm still making it work, barely. Barely is good enough, but it'll be nice to not have such tight tolerances.

In addition to the advice already given, sometimes the Steam VR window pops up in the middle of your monitor screen. You can't see it in VR, but many times it will be there on your monitor, right on top of the menu buttons you're trying to click on. Just make sure that you minimize the Steam VR window so its not hovering over your menu buttons on your monitor.

Nothing wrong with that. The changes they made to the G2 are confirmation that HP is listening to its customers about what they got wrong the first time. They are addressing pretty much every gripe that people had, including the hand controllers. Come to the dark side, Don. :D

The method I use with the A-10C cockpit is to compare the size of my HOTAS Warthog stick to the size of the stick in the game. I like to think of the DCS IPD as your brain having to know how far apart your eyes are to give you proper scale and depth perception of the world around you. So, IMHO, its not quite completely unrelated to your physical IPD. Just a hypothesis though, and all that really matters is what setting you put it at to make an in-game object appear the same size as a real-world object such as your stick.

I only rarely get the stuttering on mine with my current settings, but only when I'm down low near a fairly large city with both the TGP and MAV displaying images on my MFCDs. I'm with you on the 60Hz issue too. When I tried switching over to that, it was like being trapped in a room with a bad fluorescent tube. The flickering was terrible!

This is normal. Either TGP or MAV will cause a performance drop, and having both displaying video at the same time does it even more. It depends on how much is going on (ground object-wise) outside near your jet, and how much is going on in the FOV of your MAV or TGP. If you decrease your cockpit displays resolution to 256, that helps quite a bit, but doesn't solve it completely if you're in an area with lots of buildings and other ground objects.

You can also see if reprojection has been turned off by sitting in the cockpit and just quickly moving your head side-to-side, laterally. If you see smearing of the image, its been turned off again. Come to think of it, reprojection being turned off can also cause the symptoms that Vullcan was seeing, with things in the cockpit looking like Jello.

It has always worked for me, and each of the aircraft in my collection have my position preference stored.