eaglecash867

Just unplugging the Rift doesn't prevent Oculus Home from running when you start DCS with another HMD plugged in. It still tries to run, regardless of a Rift being plugged in. You could stop the service every time you use your computer, but why do that when preventing it from ever running in the first place without your telling it to is so much easier? Oculus Homeless just took away the graphical environment in Oculus Home, so you were left with just a white grid and your menu. Some say that it gave a performance increase in all of your games, but I never saw it.

It still works. I use it pretty regularly when I go into DCS with my Reverb and it doesn't automatically try to open Oculus Home. On the other hand, I can still plug in the old CV1 and play some of the games that use the Touch controllers. Just have to double-click on the Oculus Home icon, and it goes right to work.

Just keep the WMR controllers in the Reverb box and don't use them, and don't forget ALT-ENTER once you get DCS started, so your mouse pointer doesn't accidentally stray outside the DCS window.

You can go into the compatibility settings for Oculus Home and set it to "Run as administrator". That will keep it from running automatically, and if you ever want to go back to the CV1 for some of the Oculus-only titles you probably have, all you need to do is manually start Oculus Home and then put on your CV1. Its the simplest solution, without giving up the convenience of still having Oculus Home available when you want it.

In a real cockpit, you're usually doing most things by touch anyway, so having buttons in your virtual pit is more true-to-life.

Just a quick correction to the horizontal resolution comparison between the Rift S and the Pimax 5K+. The Rift S is 2560 total between both eyes, so its actually 1280 X 1440 per eye. The Pimax 5K+ is 2560 X 1440 per eye. Its really difficult to keep up with that, since manufacturers often tend to church up their horizontal resolution by combining the res of both displays.

The Reverb allows you to easily remove the built-in headphones. Beyond that, whatever your alternative sound solution is should work, independently of the Reverb. I use a pair of Sennheiser wireless headphones which are connected to the Yamaha receiver I run my PCs sound through. It works great. :D

I have tried an external powered hub, and it wasn't sufficient for running an HMD along with my HOTAS. I have a 5 port USB 3.0, internal PCIe card that has a direct connection to my 1200W power supply. No VR HMD problems since installing that. Your power supply may be high wattage, but that doesn't necessarily mean your motherboard USB ports are going to provide enough juice to run everything. They're really not intended for anything other than the typical USB peripherals, like external hard drives and printers. Plug a HOTAS and LCD display HMD into them and you're riding on the edge of a failure condition. The internal card is a cheap, solid solution.

Those two things pretty much cover the major things that need to be adjusted. As for the 188% SS thing, just ignore that. I haven't found anything over 100% SS to have any noticeable benefit to clarity, but getting significantly over 100% starts to cause all kinds of performance issues like ghosting. The thing with SDE between the SO+ and the Reverb isn't really all that odd. The SO+ had an SDE filter, which deliberately "blurred" things a little bit so you wouldn't see the SDE. It was a lot like turning the sharpness down on an old TV. You'd end up with a picture that wasn't as grainy, but you also lost a lot of the fine details (as much "fine detail" as an old TV could produce, anyway).

Yup. A track is worth a thousand words.

I can tell you that a through the lens pic with a phone isn't going to be an accurate depiction of anything. My IPD is definitely higher than the average, and I don't have big issues with the sweet spot. I had to modify my Reverb with a piece of weatherstripping foam, however, because the lenses are too close to my eyes for some reason. That did give me a smaller sweet spot, an overall image that was a half-step out of focus, and a blue "halo" around both eyes. Getting my eyes just a fraction of an inch further away from the lenses with the foam cured all of those ills. Not ideal, but the amazing increase in resolution over my old CV1 makes it worth inventing a few redneck adaptations. :)

If you go to the executable for Oculus, right click, and click on "compatibility settings", you can set Oculus to "Run As Administrator". That will make it so you will have to manually start the Oculus software, so it won't automatically run anymore.

What do you have your SS and PD set to?

That sounds like motion reprojection isn't actually turned on.

For me, the most visible effect of using motion reprojection is when looking around in the cockpit. Without it enabled, when you move your head quickly in the cockpit, things look smeared. When its turned on though, it can cause ghosting of objects outside the cockpit if you're running PD or SS too high. I have experimented with PD and SS with the Reverb, and I don't see any difference between 100% and 160%, except the difference in performance. That leads me to believe that the Reverb can display more than what DCS is capable of producing in the VR environment. Just wish there was a way of confirming what resolution is actually being displayed in VR. My guess is that the VR environment in DCS just isn't capable of attaining an actual resolution of 2160 X 2160, let alone anything higher than that.

Dial your Steam VR SS back to 100% (anything beyond that doesn't have any noticeable improvement in clarity), and make sure DCS PD is set to 1.0. Motion reprojection works great with those settings.

Nope. I have the Pro. :) As for the foam from VR cover, my weather stripping only cost 4 bucks. ;)

Lawn dart? :D

The only problem with having software-enabled limits to head movement is that you would end up getting vertigo as soon as your virtual head stopped, but your actual head continued in the same direction. That disconnect really messes with your equilibrium. You could always figure out a way to set up a physical barrier that you bump your head on. Might want to go to Ebay or Gibson and Barnes and get an HGU if you're going to do that though. It'll hurt less that way. :D

Looks like you have whatever facial issue it is that I have. For some reason, where the Reverb naturally settles into my face, it gets the lenses too close to my eyes and I end up seeing this distorted blue halo which is the most visible at the bottom. I tried adjusting the straps too, and it only helped a little bit. My solution ended up being adhesive-backed foam weather stripping. It was a cheap solution that was really easy to apply. Try loading up DCS in the Reverb and then slowly pull the Reverb straight away from your eyes. If your problem is the same as mine was, you'll see the distortion at the bottom go away, and will probably see the whole image get even clearer than it already was by a small amount.

No, you won't be limited in your choice of headsets if you don't go with the Steam version. I have a Reverb Pro which uses Steam VR and the Steam VR WMR Plugin, but I have the standalone versions of the Open Beta and Stable that I got directly from this web-site. Steam VR doesn't care if your game came from Steam, it will run it just fine. :thumbup:

With the Reverb, I'm getting better performance than I had with my CV1. All of that turning up of PD in DCS is a much greater performance killer than the native number of pixels. The Reverb can be run at 1.0PD in DCS, and 100% SS in SteamVR, with crystal clarity. I have seen no reason to turn those things up beyond that, and its smooth as glass without even using the shader mod. :)

The rad alt goes to an out-of-range condition when the aircraft is rolled, it doesn't go to 0 feet. When you roll back to a bank angle where the rad alt can see the ground again, and the rad alt indication goes valid again, that is when the GCAS gets triggered. If you were below the 90 foot AGL minimum that triggers the GCAS, this behavior would be correct. However, this happens at all kinds of different altitudes. I've been at 2000 AGL and had it trigger in level flight, when I roll out of a turn. That behavior isn't correct. The bug is still present in the latest OB. Sure wish they would fix it, because its probably the most annoying of the bugs.

A fast flicker almost sounds like maybe its switching into 60Hz mode. Not sure if you've tried this already, but try setting your WMR Experience Options to 90Hz. The default is Automatic, so maybe its switching back and forth? I tried forcing it to 60Hz once and got a fast flicker that instantly made my eyes hurt. Anyway, just something to try. :)

You don't even have to do that. I just plug my headset in, double-click the DCS icon on my desktop, and then put the headset on. Everything else happens automatically, and DCS comes up in the Reverb.