Maribel_Hearn

"the compatibility between your mother board ASUS Prime B250 Plus and the Wigig Intel for HTC Vive is not certified". That sounds like a boilerplate response to me. Is anyone aware of any motherboards that are "certified" for Intel WiGig?

Mode 1 2 and 3 are the different channels. (In response to AndreMan)

Another thing you can try is switching the VIVE Wireless to a different channel. Using the VIVE Wireless app, switch between channel 1 2 and 3 to see if it improves anything. 60GHz should be pretty interference free, but its possible something specific to your location may be causing interference one a specific channel at specific time intervals. Sorry if I appear to have overlooked parts of your post - My post is more aimed at anyone having issues with the wireless. I don't know anything else besides these things to help with wireless issues. Have you tried pluggin in wired to see if you get the same frame time spikes? You won't pixelate at high frame times in wired mode, but if the frame spikes are still happening, you need to diagnose that issue first, which would then most likely resolve the pixelation. Pixelation occurs at high frame times regardless of wireless signal strength/bandwidth, so if there is something else in the system causing that, you'll see pixelation in wireless.

Did you try holding down the logo/button on the top of the wireless adapter for a few seconds?

Here is something that may help some people. If you are on a GeForce GPU, open your NVIDIA Control Panel. Select "Manage 3D Settings" in the left pane. Find "Virtual Realite Pre-Rendered Frames" and ensure it is set to "Use the 3D Application setting." This may smooth our your frame times I've found that the wireless adapter adds a couple ms of frame time on the CPU side, and if frame times get high, the pixelation will occur, regardless of CPU and GPU usage. Pixelation can be triggered by doing anything that raises frame time really high, say, above 20ms. The high frame time isn't caused by the wireless adapter itself, usually, but it responds to the high frame time by pixelating the image, I assume in an attempt to reduce the overhead and get the frame times a bit lower. Here is a checklist to go through as well to ensure maximum performance. 1: Set SteamVR super-sampling to 100% to ensure lowest possible frame times. 2: Close out all background applications that have notable CPU usage. 3: Check for thermal throttling on your CPU, GPU, VRM, and wireless adapter. Checking CPU and GPU temperatures will be easy, wireless adapter temperatures are a bit more challenging (There is a log file that shows the temperatures,) and VRM temperatures will be the most difficult. If your VRM is overheating, they will dial back the power they send to your CPU, which will lead to instability or low clock speeds. 4: Use a frame-time monitoring application like FPSVR to track CPU and GPU frame time in realtime while in VR, to help you pinpoint issues. 5: If issues continue, switch to wired and see if you get the same frame-time spikes that are triggering the pixelation while on wireless.

For the people asking about PCI-E lanes. Standard desktop Intel CPUs only offer 16 PCI-E lanes directly connected to the CPU. The Intel chipset has many more PCI-E lanes to enable the use of expansion cards such as network cards, audio cards, storage cards, and of course, the wireless adapter's PCI-E card. Chipset PCI-E lanes perform a bit slower than CPU PCI-E lanes, but for most use cases, this performance difference does not matter. Intel High End Desktop CPUs offer additional CPU PCI-E lanes. These would be CPUs like the socket 2011 i9-9920X.

Can we get some clarification on what exactly is causing pixelation, audio stuttering, and absurdly low framerates? How is the video stream compressed, and where? Is it done by the PCI-E card? Is it done on the CPU? Where is the bottleneck? Is the bottleneck the HMD mounted wireless adapter not having enough horsepower to decompress the video stream? Why does supersampling cause the image to become compressed and pixelated?

I'm going to be grasping at straws here, so bear with me. I'm also going to assume it is always the same of the three trackers giving you issue? The trackers use 2.4GHz wireless, the same as standard Wi-Fi. This makes them succeptible to wireless congestion and interference. If you live in an environment with lots of Wi-Fi networks, there may just be too much for all three to work properly at the same time. You might try disabling 2.4GHz on your own wireless router, separate the dongles further to ensure stronger signal strength, Also ensure that the USB port/hub you are plugging the dongles into has enough bandwidth to handle all three at the same time. I used to use a USB 3.0 hub with my three dongles for VRChat, and eventually diagnosed a bandwidth issue with my hub that would occasionally result in a tracking 'freakout.' Plugging the dongles directly into my PC's front ports solved that issue. You might also try re-pairing the trackers to different dongles one at a time. This will allow you to determine if the tracking freakouts are related to a problem with the dongle, or the tracker itself. You can also try turning on just one of the three trackers and see if the problem tracker continues to behave the same with the other two trackers turned off. I'm assuming you are using these for VRChat, which won't let you do anything with just one tracker, but you should be able to see what the tracker is doing in the Steam overlay menu at least.

An update to my previous post where I said the firmware update did not improve pixelation when staring at high-detail scenes... The firmware update also seems to have had no effect on random temporary/permanent drops to gray screen. I still drop to gray screen randomly when diving into/out of menus, despite not losing line of sight to the antenna, and sometimes these drops are pemanent until I unplug and re-plug the wireless adapter from the battery.

I am not. CPU usage sits pretty low, as I am playing VRChat, which doesn't use a lot of threads. (i7 8700k at 5.0GHz, GTX 1080) The pixelation/audio stuttering only occurs when I stare at very complex scenes, with lots of repeating lines or detailed textures. You can see my detailed write up here: https://community.viveport.com/t5/Technical-Support/VIVE-Wireless-Adapter-and-Supersampling/m-p/23776#M9109 But this issues still occurs in some situations with super-sampling at 1.0, for example staring at complex grass textures, or a wireframe render of a scene with character avatars.

I have tested the update in situations that commonly cause trouble for my wireless adapter. No change in performance. The image still pixelates heavily and framerate drops from 90 to 25 in complex scenes, with audio becoming choppy and the pass through camera crashing. Time will tell if the update improves general stability of the connection and reduces momentary/permanent drops to gray screen.

It appears that the recent VIVE Wireless update has resolved, for the most part, the camera issue. I can now enable the camera and play for extended periods, at least, until something else crashes the wireless, like a sudden change of scenery caused by a teleport to another room.

If you haven't disabled the camera is SteamVR, do that now.

Its true that the USB cable is pretty flimsy, but it has yet to cause me any trouble. Your "headset not detected" error may be cause by the camera in SteamVR. Try disabling it to see if it fixes the issue.

Try disabling the camera in SteamVR. The Camera is totally broken with wireless for many users right now, myself included.