eaglecash867

Habu, I'll try this on mine and see what it looks like. Right now my HUD is definitely usable, but I can't remember if I have seat height adjusted correctly. Not quite sure I understand what you meant by the nuts on the right side bisecting each other. Are you talking about getting the nut on the top right side of the HUD aligned with the top two screws on the whiskey compass? I think that's what I see in your pic, but just want to be sure.

No, I'm not missing the point. My point in my post is that everybody has their own idea about what "simulating the real thing" is. Don't like where you're sitting in the jet? Move your position, and save it. Its not that hard.

The standby altimeter should send baro correction info to the CADC, which should in turn change the altitude reading on the HUD.

The problem with that is, that nobody can seem to agree on how far away they should be from the IP, how much of the HUD they should be able to see, etc. Pages and pages of debate over that, with people showing each other A-10C pilot/plane pictures from oblique angles as "proof" of their opinion, and so on. If ED made an official position for the pilot, I don't think everybody would be happy with it. Its easy to adjust your position to exactly where you want it, in game, and then save that as your default viewing position. I think the main problem with where your body ends up in relation to the seat in VR is because something is off with the scaling along the longitudinal axis. Seems like the cockpit area is too long.

Yup. Electronic kneeboards work great in VR. The HP Reverb has almost eliminated the spotting issues too, along with ironically giving a major performance boost over my CV1. Don't need to crank DCS PD up above 1.0, I can run 4X MSAA now, and I no longer have the ghosting when looking to the side at buildings and other ground objects. Wagdog, you should still definitely keep a TM Warthog HOTAS on your list though. Nothing better than having all of the HOTAS functions of the A-10C in the same place as they are in the real thing.

Going above 100% SS does nothing for me except for decreasing performance. There's no harm at all in experimenting though, and seeing what works best for you.

Welcome to the dark side. :devil_2:

We'll have to see if an O+ user can verify what you're seeing with yours. With the HP Reverb, its normal not to see any increase in visual quality with an increase in DCS PD due to its high native resolution. Not sure if the O+ is the same way.

What VR headset are you using?

Its absolutely true. Having PD set to 1.0 also frees up the resources for me to run 4X MSAA, so there are no jaggies. :D I have found neither PD or SS to be all that effective at antialiasing functions.

I set DCS PD to 1.0, along with the Steam VR SS being set to 100%. Anything higher on either one has no benefit that I can detect, and the drawback is that you start to get the same ghosting and jittering that you probably were experiencing with your CV1. Native resolution on the Reverb is 2160 X 2160 per eye. Not sure DCS is capable of hitting that level in VR though, which would explain why higher PD and/or SS make no difference in how things look. Wish there was something that could be run as part of a heads up display in the Reverb that showed what the actual, per eye, rendered resolution is.

I think the colors are just fine after an in-flight adjustment of gamma correction, but opinion on that varies from one person to the next. The Reverb is a WMR headset, so it doesn't have its own software. You run it through Steam VR, and the Steam VR for WMR plug-in. Once you get both of those installed and set up, the process of going into VR is as simple as it is with the CV1. Just start DCS and pull the HMD on. Everything that needs to happen should happen automatically. Since you currently have the CV1, you can keep Oculus Home from running automatically by going into the compatibility settings of the .exe file and checking the "Run as administrator" box. After you do that, you'll still be able to run your CV1, you just have to manually start Oculus Home. This will prevent the software for the two HMDs from interfering with each other, which has been known to cause weird performance and control issues. You may see a lot of talk about setting SS in Steam VR to around 188%, but I haven't found that setting it to anything higher than 100% has any benefit to the visual quality in DCS. My theory on that is that DCS isn't capable of rendering VR in a resolution higher than the native resolution of the Reverb, so all higher PD and SS settings get you is dramatic decreases in performance.

Well, there's only one way to know for sure. :thumbup:

Very cool! Simple solutions like that are always the best. :D

I can't really offer any tips that are guaranteed to help in your individual situation, but I can tell you that the tracking on my Reverb works just fine. The difference may be that all of the components I use when I fly DCS are built to roll away into an out-of-the-way area when they're not being used. Because of that, I'm able to just set everything up in the middle of my living room, so I don't have any walls that are really close to where I'm sitting.

Completely agree. Its a sim that gives us a reasonable amount of fidelity, and it only cost 60 bucks.

He came out of that OK though. He just modified his drum kit so he could use both feet. :thumbup:

I know it sounds counter-intuitive, but the best thing you can do to improve VR performance is to put the CV1 on reserve and get a Reverb. When I was using my CV1 for DCS, on the same rig, I went from a 1080ti to a 2080ti, and had no real noticeable performance gain. Once I had the 2080ti for a while, I got the HP Reverb, and the performance is smooth as silk now. With the much higher native resolution of the Reverb, you'll no longer need to use PD above 1.0. Setting PD higher and higher is what really kills VR performance in DCS. Better visuals, better performance, half the cost of a new GPU. Win, win, win! :D Also, especially in the A-10C, something that hasn't been mentioned is the "Resolution of cockpit displays" setting. That has a big impact on performance when you have an image being displayed on the MPCDs from the TGP and/or Mavericks. I have mine set to 256, and I can see everything I need to see with the Reverb. Setting visibility to medium had undesired effects. Even on a CV1, I was seeing ground objects suddenly appearing, well within visual range. Setting that to high makes it so that doesn't happen. Going higher than that? I haven't seen any reason to. I have my water set to low. But, I mostly fly the A-10C. I don't spend much time over water in it, because I'm not sure if my seat cushion can be used as a flotation device in the event of a water landing. :)

Wasn't there a girl who went blind from sitting too close to the television? I think I heard she ended up marrying a guy who made a face and it stayed that way. :D

You should be just fine with that system, but maybe double your memory like mariner suggested. As far as the choice between the Rift S and Reverb goes, ironically, the Reverb will give you better performance as many of us were pleasantly surprised to find out. Since the Reverb has a higher native resolution, it doesn't require any increased PD in DCS, nor does it need any Steam VR super sampling to give you a nice, clear picture. Having to turn either of those two things up above 100% is a major performance killer. On the same system, my Reverb runs smoother than my Rift CV1, and gives me a much better picture. As I found out just recently, I can also run 4X MSAA now with very few problems with performance. 4X MSAA on the Rift, with a PD of 2.0, turns it into a slideshow. Not so on the Reverb with a PD of 1.0 and 100% SS. The Rift S would probably do better performance-wise that my CV1, but its a significantly lower resolution than the Reverb, so it would require some help in the form of a PD above 1.0 in DCS, which hurts performance.

Pretty much every time my DCS would update, I would have to go back and do the shaders mod dance again, and I don't fly on-line either. Haven't needed the shaders mod since I got my Reverb. The Reverb allowed me to get rid of the performance killing PD of 2.0 that I was running with my Rift.

My 2080ti does this just fine with the Reverb. I didn't think it would, but I tried it, and it works just fine. Very tiny bit of ghosting here and there, but its rare. I run 4X MSAA all the time now in DCS, and just got my gamma correction dialed in so everything is nice and vivid.

Yes, I know. You were getting personal, and there's no need to do that. You are confusing IAS with TAS. Full stop.

Again, straying off the topic. The shape of the Earth also has nothing to do with IAS vs. TAS. :megalol:

That would be correct. Nikola is confusing IAS with TAS. :)