eaglecash867

Heh. HP was all set to ship me a replacement ahead of my sending my defective unit, until they found out I had the Pro version. They then connected me with the professional/business side of the house, and they agreed to send me a replacement cable after we did some troubleshooting via e-mail. Took a month to get the new cable because they didn't have any in stock. They were definitely inconsistent with how they were handling issues.

Hi Conura, The default view in the A-10C is too far back, IMHO, and it causes problems with being able to see the whole HUD. You can compensate for that by manually adjusting where "center" is using this post. Don't forget to use the "save" command at the bottom of the list after you get your default view where you want it. https://forums.eagle.ru/showpost.php?p=3830595&postcount=2

Yes, it works just fine for editing simple files like the vrsettings config file. It worked just fine for that a decade ago too...and the decade before that. Its all a matter of personal preference, and nobody said anybody "needed" anything. :thumbup:

:thumbup:

Yeah, and you could drive your car with your feet if you wanted to. But that doesn't make it a good idea. :megalol:

Awesome! Glad to see that us VR lobbyists could help you get it going. :smilewink:

I have only had it revert once, and that was because of the major changes to SteamVR for WMR that happened a few weeks ago. Once you verify that your change has been saved, make sure to shut everything down related to your Reverb. Next, you may or may not need to unplug your Reverb (I never leave mine plugged in at the connector on the headset itself), and then shut down SteamVR, SteamVR for WMR (if running), and WMR itself. When you plug your headset back in, it should automatically run WMR, and then you can start DCS to have it automatically load SteamVR and SteamVR for WMR again. You have to do the shut-down/restart steps after making any changes to your VRsettings file because SteamVR for WMR only runs that file when it starts up.

There are definitely two different schools of thought here. The majority of us are trying to help others get the best possible VR performance out of their unique setups. A majority of us have posted screen shots of our own settings that we are getting good results with so others can compare apples to apples. And then we have the vocal minority, that dismisses everything the majority is saying, and really offers no helpful advice or even a direction to go for other people. Some here have gotten satisfactory performance while running incredibly high settings and super sampling rates. My experience has been different, but with so many variables involved, I don't have a concrete reason to doubt anyone else's personal experiences or preferences. I simply accept that they're seeing what they're seeing, and leave it at that. I have my Reverb working great now for my liking, and if I want to experiment by trying the advice of others, it is my own choice to do so. If their settings don't do anything for me, I simply set things back to where they were when I was happy with the results. Its really not a big deal. :)

If your counter is showing 70-90fps, then motion reprojection isn't turned on. When its turned on, the FPS counter should show a pretty stable 45 or 30 FPS (half of whatever refresh rate you have selected for your Reverb). Can you post your vrsettings file from Steam VR for WMR here so we can take a look at it?

+1 :thumbup:

Don't forget "key influencers". The "professionals" keep telling us we don't understand how things work, yet we have our headsets working quite well. :pilotfly:

1. The Reverb does have a smaller sweet spot. I've found that getting it positioned on my face properly is a little difficult, but once I get it positioned, the small sweet spot isn't as much of a problem. 2. Make sure you have removed the protective film from the lenses. That was one of the things that got me when I first got mine. :doh: :D

Yup. No manual button mapping needed, except if you want to correct the physical positions of the rocker switches in the corners. They'll be backward with the default setup. Connect each one to a USB port, and they'll go right to work in DCS without much fuss.

Yup. Right out of the box, it will actuate the corresponding display button, except for the rocker switches at the corners. They are reversed from where they are in the on-screen MFDs in the A-10C. As I recall (since I haven't used my Cougars in a while), they're placarded correctly, just positioned on opposite sides. So, it depends on whether you're going to be looking at the placards, or if you want the physical locations to match.

Cable length is the same between the two versions, 4 meters. The Pro just comes with an extra, shorter cable that is 0.6 meters in length. Room scale with any HMD that uses DisplayPort as an interface is going to be difficult. 4 meters is actually about the maximum for cable length with Display Port, unless you use a signal booster, and there's no guarantee that a booster would help. That's the only thing I don't like about the Reverb. The cable length limitations of Display Port. I don't do any room-scale VR gaming, but I liked being able to extend the cable on my old Rift for watching 3D movies in VR so I could sit on my couch and enjoy it.

If I was looking to argue with people about the virtues of VR versus TIR, I'd be showing up in TIR threads insisting that I "won" something. As you say, each their own, which is why I happily stay in the VR threads and don't feel a need to go to unrelated areas of the forum just to say "my way is better". My way is better for me. :D

:confused:

+1 "Objectively" in this case means an opinion, based on incomplete information from a system that is not capable of registering the frame interpolation done by motion reprojection. But this "core group of VR flyers...happy with low FPS" get our subjective viewpoint by doing the silly thing of actually looking out the window, and not being fooled by an FPS counter and its limitations in seeing interpolated frames.

Just out of curiosity, what does it say on the ID plate inside the headset? The reason I ask is that my US Reverb once showed a 3 year warranty on my specific serial number, and then one day it changed to a 1 year warranty. I was about to call HP and make a fuss over that, but when I looked at the ID plate on the headset, it said "1 year limited warranty". They must have had an error on the US web-site and corrected the error.

No difference that matters between the consumer and pro versions. I have the pro version, and I'm not even using its leather facepad anymore, because it was too thin and my eyes were so close to the lenses that I was seeing blue halos from the lens edges. The claim used to be a better warranty (3 years vs. 1 year), but they both have the same warranty (1 year). Your hardware will do just fine with the Reverb. You won't need as much SS in SteamVR to get a nice, clear, smooth experience, so you'll probably actually see a slight boost in performance.

That's odd. The DCS menu gamma slider is what I've always used. Looks like you're getting things figured out though. I was so frustrated with my Reverb at first, I almost sent it back. Just turned out to be a few things I had to do differently than what I was doing with my Rift.

Have you tried having a look at this thread?: https://forums.eagle.ru/showthread.php?t=244117 I haven't tried the advice there yet myself, but apparently it has helped a lot of people with the crossed eyes problem. Might be worth a shot. :)

Hi Sirrah, Are you seeing that flickering in the sky and clouds as you're moving your head? Do the clouds appear to suddenly disappear and reappear, or is it something different? One other possibility might be your in-game gamma setting. I had trouble with that for a while, until I finally made the "discovery" (heh...something I should have already known, but didn't) that I could hit the escape button and bring up the graphics settings menu while paused in flight. You can't adjust everything on that menu while in flight, but the gamma slider works. It made a huge difference in the color quality to set it that way. Try playing around with the in-game gamma slider while in flight and see if you can get a result that looks good to you.

I remember finding the Steam article he seems to be referencing over and over again. One important detail that he missed, however, is that they stated the "on by default" asynchronous reprojection feature only applies to non-WMR headsets. I'm not going to go find it for him though, because my Reverb shows the same results seen by all of us here (except him for some reason) when I edit that key line in the vrsettings file for SteamVR For WMR. I rarely stare at FPS counters, but with the line commented out, I get FPS in the 60s to 70s, but when I rapidly move my head from side to side, the image in the cockpit is smeared and not smooth. Take the // out of the equation, FPS goes to a solid 45, and that same head movement yields smooth motion of the cockpit image. Its very strange how the one person out of all of us here who insists that the rest of us are suffering from some sort of delusion seems to also be the only one here who can't seem to get this feature to work. I'm pretty sure I know the key step that he's missing in his setup, but I'm not going to bother with that. There's a clear lack of attention to detail in certain individuals that just can't be overcome, and quite frankly, its exhausting. I'll just go back to enjoying the hell out of the A-10C and F-16C in VR. :D

+1 :D "Goodbye VR" sounds a lot like "I don't wanna play anymore! I'm taking my football and going home!"