eaglecash867

I haven't found a need to push SS beyond 100% or to push PD in DCS beyond 1.0. Pushing either one much above that causes your performance to drop dramatically, and I had no discernible difference in visual quality. Definitely use MSAA X2 to get rid of jaggies. Pushing PD or SS up to get rid of that isn't as effective as MSAA on the Reverb.

Nah. If you would have kept it, they would have probably downgraded your warranty like they did with mine. They probably just don't update your warranty status anymore because you returned the headset. Heh...either that or they just like you better. :D

Its called a sense of motion, not motion sickness. Something flying a pancake with TIR will never give you. :harhar:

My PC never gets shut down. It also serves as my home audio and video entertainment server. :)

That could very well be the case. I imagine that since the Reverb runs on a Microsoft program, its a lot like some of their OS's over the years, in that it requires frequent reboots because of the random BSOD. :D I remember now that when I first got the Reverb, it seemed to have croaked shortly after I started using it, but after putting it away overnight, it came back to life the next day. :doh:

I would try just unplugging the USB portion and letting it discharge, then see what you get. I've been unplugging mine at the connector on the HMD, mostly because I'm not crazy about the idea of repeatedly plugging/unplugging a DP connector from my $1400.00 GPU.

From my recent experience with my Reverb suddenly dying, but then spontaneously coming back to life a couple of days later, I think its a matter of unplugging the Reverb completely and giving it some time for everything to discharge, pretty much the same way you do it when you have to reset a router. That theory seemed to be confirmed by the HP commercial division support rep I talked to last night. He specifically said that sometimes you have to give the headset a little time unplugged in order for things to fully discharge and reset when you experience an error like that. I was getting a USB error on mine, which miraculously cured itself during the time I had it put away pending some free time to call HP.

I upgraded from a 1080ti to a 2080ti on the same rig, with same CPU, and my results were pretty disappointing. I had no noticeable performance gain, and no added ability to turn up graphics settings. Strangely enough, what did end up giving me huge performance gains for VR was my recent acquisition of an HP Reverb Pro. When you have an HMD that has a native resolution that good, you don't have to use performance killers like higher PD and SS.

Yup. Not the same headsets. Just got off the phone with HP. Had to jump through a few flaming hoops to get to the right division, but their commercial division is fantastic. They started walking me through troubleshooting, and the friggin thing came up and started working as soon as I plugged it in. So, I have a case number now, as well as a direct number for their commercial division. They told me that if the problem resurfaces to call them directly and they'll help me get things figured out as far as what needs to be replaced. As far as the warranty issue goes, while I was looking at the ID plate on the inside of the headset, I saw printed on the ID plate that the warranty is 1 year. So, it looks like the 3 year warranty I originally saw on the web-site must have been an error of some kind. Its all good now. They're taking great care of me. My trust in them has been restored! :D

I imagine that since you already returned yours to HP, they're no longer worried about having to honor a warranty that they apparently are now regretting having offered in the first place. Mine did say it expired in June of 2022, but now it says "June 2020-11 months remaining" Not looking forward to having to deal with it, since almost every tech support experience these days requires a UN interpreter. I guess I'll be back on the CV1 for a while, and hope for great things with the Acer ConceptD Ojo. HP is going to have to do something spectacular to regain my trust after the whole warranty thing.

I completely agree. Good to see someone else that sees it that way. :D

Nobody is missing any "point". Most people here are just essentially saying "you do you", and that's what people should go with. Endless speculation and egghead debates about theoreticals is all fine, but at the end of the day, it accomplishes nothing and funds nothing. As the saying goes-the best laid battle plan never survives first contact with the enemy. :)

It has finally happened to me, my Reverb has officially crapped out. I started getting the intermittent switching back and forth between the HMD and the default audio output, then a couple of black screens. Then came random USB disconnect sounds. Now, the only thing that happens when I plug it in is WMR recognizing that it has been connected with the little circle of dots, then I get a USB error telling me to connect the headset to a USB 3.1 port. Haven't had a single problem with this thing until yesterday. On top of all that, my Reverb Pro warranty, which was a 3 year warranty has suddenly changed into a 1 year warranty for the same unit. I'm pretty sure that is illegal for them to change the terms of a warranty that you already agreed to. Extremely disappointed in HP. They'd better make this right. I'm thinking about just demanding a full refund, since the warranty thing is nothing short of dirty pool. :mad:

If you're using a previous generation headset, yes, that might be true. No problems with spotting and identifying aircraft with the Reverb though. :)

The current upper end graphics cards do just fine with the HP Reverb. In fact, the performance is actually significantly better with the Reverb than with lower resolution HMDs because you no longer need a bunch of extra processing power for running SS and PD above native.

Not sure about the Reverb with an external hub, but I remember that my CV1 had issues with it, so I got the Inateck PCIe card and have been a happy camper ever since. I use my external hub as an easily accessible place to plug in my HOTAS.

Immersion is no gimmick. The depth perception provided by VR, as well as the spatial awareness are everything when it comes to instinctively knowing which way to point your jet when you're doing everything from dogfighting to evading enemy guns and missiles. I have the HP Reverb, and I have no performance issues. I can evade ground fire and instantly come around on the thing that shot at me and kill it as if the jet is an extension of my own hands. There! There's a statement of functioning more effectively in VR! :D Go for it, Mr. Burns! The amount of usage you are planning (which is pretty much in line with most of us I think) makes VR an excellent choice. Might want to wait until version 2 of the Reverb comes out, but I have a version 1 and haven't had any of the issues with it that HP is working on resolving. VR is also going to be the least intrusive on your other living space.

I saw almost no performance gain going from a 1080ti to a 2080ti. The 2080ti did seem to provide a little more depth perception somehow, but that is definitely not a quantitative measurement. The biggest performance boost I noticed was when I went from a Rift CV1 to a Reverb Pro. No longer needing PD above 1.0 in DCS gave major gains in performance, all with a much clearer picture. As far as a 2080ti is concerned though, at least for DCS, its just a big $1200-$1400 hole to dump money into.

Typ. We've all done stuff like that, and then kicked ourselves afterward. It definitely comes with the territory with flight simming and all the tinkering we do. Not trying to blame anyone for anything, since I've had lots of times where I broke something because I misunderstood how it was put together. :D

Then all you have to do is look at the thread cleverly disguised as the "HP Reverb Pro" thread. :music_whistling:

My post was directed at the OP to make sure that HE knows what he's supposed to do. Your little boy twisted the stick in the wrong place, which is what it looks to me the OP did, and that's why it broke. Maybe I didn't see it in your post, but was your little boy in the process of changing the stick grip? There are also tool marks on the collar, metal shavings all over the place, and a pair of vice grips in one of the photos. To me, it looks like something wasn't done right, which is why I said "If you have to use tools, you're doing something wrong". :thumbup:

+1 on the Vu-Jade. (Vu-Jade: The unmistakable feeling that you've never been here before.)

If the A-10 stick sheared off above the collar like what I see in the photos, you were twisting it in the wrong place. The collar itself is what you are supposed to turn counter-clockwise, and it doesn't require that much force. You hold the stick steady with your weak hand, just to keep it from falling over, and then rotate the metal collar counter-clockwise with your strong hand. Once the collar is loose, gently pull the stick straight up (with a little, gentle wiggling) to disengage its connector. When you install the new stick, gently and carefully align the connectors and let the stick settle into the connector under its own weight (sometimes a little light pressure and wiggling may be required, but don't force it in, you might bend pins). Rotate the collar clockwise, being careful not to get it cross-threaded. If you are unable to turn the collar without the use of tools, it is getting cross-threaded, back off and try again. Many times it helps to first rotate the collar counter-clockwise until you feel the slight bump of the threads engaging. That should keep it from getting cross-threaded. Just remember, if you have to use pliers for any of this operation, you're doing something wrong. YouTube is a great resource for learning how all kinds of things are done, so if you're still having issues, go there and watch some videos on changing a TM stick grip. I know the TM sticks are notoriously weak in that spot, but even the strongest tubing in the world is going to cause something to get damaged if you're essentially trying to rotate a keyed connector within the mating connector. Something WILL break.

Yup, but it was the Reverb that had enough of a "HOLY S***!!!" factor to it to make it worth implementing native WMR support. :D

I know there is a lot of worry about Oculus being owned by Facebook, but in my trials with the Reverb, I have come to the conclusion that letting Microsoft handle the software end of things is even worse. I really believed in Oculus, but they kinda let me down with the marginal increase in resolution announced for the Rift S. The Reverb and the WMR crap has been a bumpy road, but after all the screwing around, I'm happy with the result.