mono1337

@AlteredRealitiesVRArcade No wonder VR has a rough start... Nobody should have to tinker that way to get acceptable performance. Especially since you have to do it on a per game basis as no solution seems to work for all... Depressing! Anyways... After some more experimentation, I have finally totally ruled out my WiGig card as the culprit in my system's poor performance. -I tried to put the card in all other available PCIe slots : No difference -I removed it and put back the cable : No differences -I started SubNautica in Pancake mode, changed the resolution from 4K fullscreen to 800x600 windowed, closed it and started back in VR mode back : Acceptable performance. Apparently the game was outputting both to screen and HMD(I mean, not just mirroring the HMD display but actually calculating a different camera)? -Re-checked the usual benchmarks (VRMark, 3DMark) and confirmed that my system's output is in line with what should be expected of the installed hardware(I think an hardware issue with either CPU, GPU or RAM would have affected those results). So, what gives??? I still think my system performance is crap in actual VR when it should be a lot better. A wired Vive pro and I still get some reprojection in friggin Beat Saber at SS 2.00 global (default setting in Steam VR properties and confirmed in fpsVR in app)?. I honnestly don't know how to isolate the issue, but at least I have been able to rule out that the CPU is the bottleneck: My GPU is maxed out when I get crappy FPS while the CPU still is at 50-60% max. I strongly suspect a software/drivers issue, because in VR Home, and Google Earth VR, performance is perfect(wired or otherwise), and seems to be totally unaffected by the global SS setting. There might be some software paths used by games (Unity, Unreal, Steam VR repro) that upset my config in some way? Not sure how to isolate and correct the issue.

Yep, that looks consistant with the kind of perf I had before on my 4790K / 1080. Now, with my 2080 ti, I get even worse... I'll try to capture some data, but at 100.0 SS it should be more than just playable but buttery smooth... :-/

Unfortunately, that's where the card sits at the moment, I tried to change the speed in the BIOS(from x2 to x4), but both settings have the same effect. I chose this motherboard specifically because it's equipped with a dual x16 PCIe bridge that allows 2 way sli at x16x16 or four way sli at 8x8x8x8x. I thought it would be a good idea to have as much PCI lane as I could, but now, I wonder if I should have got any other gamer oriented card. It would be great if we could take stock of all the configs of people that were able to make Wireless Vive work, out of the box or after manipulations. As soon as I have the time, I'll try the following : -Test if the Vive Pro operates as expected when wired. -Move the WiGig controller card on each available slots. -Install my old GTX 1080 and see what happens. But it's rather heartbreaking to have to do all this because my previous setup was working just fine, I wanted to upgrade to have even better visuals out of the box, without having to endlessly tweak my setup... Stand alone is the way of the future, as a controlled environment seems to be a lot more manageable, if we look at what Sony achieved with the PSVR with inferior hardware (they still have better lenses without halo effect and their oled is way better at masking the screen door effect albeit at a much lower res). Ah well, just venting now... Sorry for the rant... Stuck at work and eager to go home to try and make it work...

The K series, in addition to the integrated graphics, which is obviously not the point in a gaming rig, is more overclocker friendly and offers already the highest clock speed out of the box. For gaming, single core w/ a high frequency is still king. Grandted it doesn't make a LOT of financial sense, but to be honest, in building that rig, I wanted the best money could get me... Unfortunately, in this case, it appears this was a very unwise decision, and didn't yield the expected result as my gaming focus is VR... Doh'

Hello there... Here to share my experience, and hopefully help solve this issue for me and everyone else. Vive Pro w/ Wireless (Duh) Clean Windows 10 Install ASUS WS Z390 PRO Intel i9 9900K RTX 2080 Ti 32 GB Corsair 3000 MHZ Ram Steam VR beta or not (no changes) I built this rig this week-end, and it replaces an older 4790K/1080 setup that was working OK w/ wireless. This new PC munches trough benchmarks and works as expected in pancake mode, but offer very poor performance in Wireless VR. It works, and is useable in certain titles (Beat saber for instance), but even with very low SS (1.0 and down) there is still reprojection and missed frames happening, except in Steam Home VR, where I can just crank the SS to 5.0 with no adverse effect whatsoever(but no visual indication of any change either so it may be a special case and be immune to config changes, I don't know). Other titles, namely Fallout 4 VR, is just laggy, jittery, and nausea inducing. Worst offender seems to be Subnautica though, which I now have to play at 0.2 SS to get 90 FPS... I have not yet tested to connect the Vive pro to this machine with the original cables (but I might just to rule out any possible other issue). I have a clear line of sight between the WiGig emitter and my Vive pro, the signal is maxed and I have seldom witnessed a signal lost grey/blueish screen. Just pixellation galore and severe glitches with lateral movement and stuff. After reading on the subject, I suspect the issue is a mix of flaky software and a WiGig PCIe adapter that is particularly finnicky about the slot you put it in. My motherboard only has one PCIe x4 slot, that can be set to work at either x2 or x4 speed but that shares some lanes with something else on the mobo, maybe an USB3.1 connection, not sure... Anyways, both config have the same effect. Someone that knows those things better than I do tell me if it's worthwhile to try and put the WiGig adapter in a x16 slot. One can work at x16 and is the recommended choice for 2 way SLI, and the other one not blocked by the GPU is a x8 speed max.