sze5003

I don't think I notice a difference with 1.5 vs 1.0 PD. Last night I flew a bit with the new Reverb. Used wmr for steam beta this time and kept dcs pd at 1.0. Last time I could not tell the difference between 1.5 and 1.0 that much. No dead pixels this time that I noticed. Will have to keep checking later. Can someone describe warping and ghosting? I have not enabled motion reprojection yet either.

Its in a steam settings file usually here. Copied from the VR guide. Make sure you have the beta version wmr for steam vr app. \Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings File: default.vrsettings In this file, the highlighted lines are commented out with // Remove the // and restart Steam and SteamVR. Optional: If you DO NOT want the indicator to show in your HMD, don’t uncomment the line for the Indicator. // “motionReprojectionIndicatorEnabled” : true, No need to removed spaces and yes the quotes need to stay in place. { “driver_Holographic” : { // Increase back buffer size so that larger superscale values do not get a resolution reduction “renderTargetScale” : 2.0 }, “driver_Holographic_Experimental” : { // “motionReprojectionMode” : “auto”, // Motion reprojection doubles framerate through motion vector extrapolation // motionvector = force application to always run at half framerate with motion vector reprojection // auto = automatically use motion reprojection when the application can not maintain native framerate // Automatic motion reprojection indicator to display the mode currently selected // green = off because application can render at full framerate // light blue = on because application is cpu bound // dark blue = on because application is gpu bound // red = off because application running at less than half framerate // “motionReprojectionIndicatorEnabled” : true, Only uncomment the motionreprojection:auto line.

There is no need for a fresh windows install. You should have just run windows update.

In windows go to windows update and check for updates. It will be there. Keep the headset plugged in. Yea I too saw my PC hang on the first reverb when I just did a reboot. I think it's honestly a windows wmr issue. Mine didn't beep but it just hung for like 3 minutes before it finally rebooted. I didn't get static in the headset.

I've always had instability issues using prime95 testing with the many motherboard auto overclock options. If overclocking it's better to do it one step at a time manually. I don't trust those built in overclocking tools. Try without an oc.

There was a new hololens driver for wmr yesterday. Does the headset work now? Start with steam vr logs in the steam install directory. I'm not sure why you would be getting blue screens. One thing I could think of is memory but you have enough. Maybe a background process interfering?

Connect the USB to a USB powered hub or get a pcie USB 3.0 card. The startek one linked above is a good one. If this does not power it up, it means the headset has a problem.

I don't have dcs in my steam games list folder as it's standalone and when I try to add it as a shortcut in steam it doesn't launch. I've always just put on my headset, open the desktop from the headset (remains open for next time you put on the headset), and then double click dcs shortcut on there. Everything required starts up after.

The first reverb I ordered had a dead pixel in the center of the display. It was neon green and sparkled out like a star on any dark background. At times you could see like a tiny line extend from it. It also got pretty warm which I felt in the front after 20-30 minutes in dcs. The serial number for it was 932 and it had the clip with it too. When you say desktop mode is that a new thing or just the desktop app you open from within the lost of apps in the cliff house?

Yea I too was very confused about which beta you had to be on. I'm glad Baldur cleared it up. Not sure of any reason to use steam vr beta unless you prefer. Before the confusion I thought if you were on wmr for steam beta (seriously what a stupid name, let alone have it be within steam itself), that you also needed to have steam be in beta. Also screw the chirping birds in cliff house! Who the f*** thought this was a good idea? Drives me insane. Picked up my new replacement reverb. Not sure if I'll get to use it tonight as I have to work late but hopefully I can open it by the weekend.

Use stable version of steam vr. Inside steam store search for windows mixed reality. It's an app. Download it and once it's installed right click it in steam. Got to properties and opt in for the beta version. You may need to restart steam. But once you do your percentages should be equalized with 100% and the correct resolution. If you launch dcs from the desktop app from within the reverb, it should automatically start steam vr.

That's because you must be using steam vr beta not windows wmr for steam beta (app you download from steam). If you use steam vr stable and beta (wmr for steam vr) app then 100% should give you the equivalent of 180% you see now.

I never messed with the Oculus tool tray. I do remember when the headset was down for a few days until Oculus put out a patch. That was about the only issue I had with it. I hope windows WMR will get there too one day. But it's like the Android OS of the headset world since so many headsets have to be compatible with it. I just hope Microsoft doesn't abandon improvements for it.

Ahh ok thanks for the explanation. With my original reverb I was using wmr for steam vr stable and 100%. No wonder the resolution displayed in steam vr settings showed less than native. But I was using 1.5 PD in dcs and it performed fine. Cool. So switch to wmr for steam vr beta. Keep it 100% and put dcs PD to 1.0. Turn on motion reprojection in settings file along with the indicator. This is the clarification I needed and will give this a shot tonight with the new Reverb. I can see why people prefer Oculus software, well I knew that already lol.

The dcs VR guide says to use stable steam vr and beta windows wmr for steam (app from steam) and set the super sampling in steam to 100-150% so that you see your headsets native resolution displayed in steam. Is this what people are doing?

Try your innatek card first. It may work depending on your motherboard, etc. No idea why it didn't work for me even with the CV1. Well it did but eventually things would go haywire and I'd lose connection/tracking. Since you have a powered USB hub try that too, if you see issues with the innatek card. Only reason why I don't use my Anker powered hub is because the headset cable does not reach both the desktop which is under my desk and the hub which sits on top of my desk. If your reverb has issues with the powered hub call HP and have them send you another one out. That should not be happening. There is a thread on Reddit where a user was having black screens and tried a pcie card, still has issues and HP is sending him another. Last resort would be to buy another card like this one. That's what I use currently. https://www.amazon.com/dp/B00HJZEA2S/ref=cm_sw_r_em_apa_i_WpeQDbWE5KZ82 My second reverb arrives today. I plan on using that dcs VR site too. But I don't know if it has been updated at all.

I did have the 4 or 5 port innatek. It's in my closet now. It had issue after some months with the Cv1. Maybe because of the drivers or windows drivers. But I had to replace it with the more expensive startek one.

Yes the one I have has a sata power connector also needed to be attached to it.

Pcie card should work I've also heard people have issues with the hubs too. Unfortunately my hub is on my desk so I would need to buy another one so that the stupid split cable can work without reach issues. I have a decent pcie card. The important thing to note is if you buy a card, make sure it has its own independent bandwidth for the USB 3.0 ports. Not all cards have this, but the startek ones do.

Yea mine would always run in the background. The later windows updates may have fixed this now.

Yup it always did this for me in the Odyssey too. If it didn't, it usually meant the service had been running already in the background...which windows seems to be really good about keeping that up lol.

I also forgot to mention you can download a program from GitHub called revive to let you play your Oculus games on wmr headsets. I didn't use it with the reverb because I became outraged at the dead pixel but I did use it when I was using my Odyssey.

In windows mixed reality settings under windows I think you can turn off voice commands. You can leave Oculus installed but you may want to stop it from launching automatically by disabling one of the admin properties in the shortcut settings.

He does work for HP QA. On Reddit he is taking people's case numbers or emails and following up with them. The problem is HP support specialists are not told the same thing he posted on the HP support forums about the pro version of the headset being eligible for advanced RMA's. At this point I also don't trust that the serial numbers meaning, we got a good one or not. My first one had green dead pixel and got hot in the front and my serial was 932 and my friend's had a dead pixel as well and serial 933. If I don't see any movement on my second order anytime soon I'll contact them and see what happened. I got charged for it but the tracking number says FedEx doesn't have it.

Mine was fine running off the Mobo USB and the pcie card. I mean it does not matter if he ordered the consumer version or the pro version. He thought the consumer models also had issues.