CMDRZOD
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Blogs
Events
Store
Downloads
Posts posted by CMDRZOD
-
-
Have you tried my fix I described on the last page? I had some issues last night even with my fix applied. 2 or 3 disconnects in 3 hours of play in Flight Simulator.
-
Just an update. This fix I posted has almost completely solved my disconnects. I've played about 40 hours of VR since my original post. In that time I've had maybe 3-4 disconnects. FAR better than before, where I would regularly get disconnects every 20 -30 min or even worse. I recommend periodically checking the device manager, after a couple disconnects I found that the devices on the card were set to save power again! Once I disabled power saving again the disconnects are very rare. In 40 hours I've had maybe 4 disconnects, and I attribute most of them to signal loss due to the placement of my PCI-E card antenna. Hope this helps. Happy gaming!
-
My Specs and config:
Asus Rampage V Extreme X99 motherboard
i7 6950x 10 core 4.4Ghz OC
32GB 3200Mhz 14-14-28 1T RAM
RTX3090 (Just got this in January, was 1080Ti since 2018-19)
Windows 10 Pro x64 20H2 Build 19042.985
Monitor: 65HU9000 4k TV (2014) HDMI 2.0
Intel 750 1.2TB SSD PCI-E 4x
Aquantia AQC107 10GB Ethernet Adapter PCI-E 4x
Like I said, I've had the random disconnect issue for a very, very long time. The fix above has solved the issue for me for about 10 hours of playtime so far. I applied this a few days ago.
In my BIOS settings I've got my PCI-E set to Gen 3. Also I have ASPM PCI-E power saving disabled, in Windows power management as well the BIOS I believe. Besides this issue this PC works flawlessly. I currently have the latest Nvidia driver installed. I have been mostly free of the Nvidia issue that causes frame drops with newer graphics cards. Hope this helps others who run into issues.
-
I've had this issue for a very long time. Random disconnects. I tried all the fixes listed here. The controller timeout fix didn't work for me. The setting USB devices to never power off didn't help either. At least not the normal USB devices and hubs listed in device manager.
This is what seems to have finally solved this for me:
Open device manager. Click view and then devices by connection. Find the PCI-E port that your card is attached to. My Intel PCI-E card is attached to Intel PCI Express Root Port #8
I set every device under this PCI-E Port to never power down to save power. This is the whole Intel Wireless VR Card, its software component listed here as well as the USB Root Hub. After disabling power saving on all of the devices that are part of the wireless PCI-E card I have not had a drop since. Screenshot below:
-
2
-
2
-
-
Just found this in a log file from the system info program:
[2020-05-10 13:11:32.053 -7 0x4A84 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2020-05-10 13:11:35.082 -7 0x4A84 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-05-10 13:11:35.099 -7 0x4A84 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-05-10 13:11:39.261 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.264 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.296 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.465 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ERROR(0), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
Seems to be something to do with the Intel SDK software. Would be nice for HTC to address this issue. It plagues many users.
-
Same here. Been dealing with this issue since purchasing the wireless VR. Found this in a log file in the system info program:
[2020-05-10 13:11:32.053 -7 0x4A84 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2020-05-10 13:11:35.082 -7 0x4A84 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-05-10 13:11:35.099 -7 0x4A84 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-05-10 13:11:39.261 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.264 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.296 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.465 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ERROR(0), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
So it's possible to figure out the cause. Seems to be something to do with the intel software.
-
I'm still getting this error regularly. I was checking the system information tool & log program and found this in one log file:
[2020-05-10 13:11:32.053 -7 0x4A84 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2020-05-10 13:11:35.082 -7 0x4A84 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-05-10 13:11:35.099 -7 0x4A84 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-05-10 13:11:39.261 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.264 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.296 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.465 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ERROR(0), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)Seems somewhat clear what the issue is. Would be nice to hear that HTC is working on the issue. I've had these errors when starting VR since I bought the wireless unit. Sometimes I must reboot 2-3 times to clear this error.
-
I started getting this error when I updated to Win 10 1903. I rolled back to 1809 and was okay for a while. Now when I try to play VR this error has been occurring again. I'm still on 1809 but I think some Windows updates have brought this error back.
When this error does occur, I try to reboot my PC. My PC will not reboot using the start menu, it will hang at a black screen and then shutdown after about 30 sec. I have my PC set to be able to wake from USB so I can shake the mouse to start the PC, but this will not work. I will manually have to press the power button to start the PC.
After this I will boot and Wireless VR will work fine. I will shutdown the PC after the session and next boot the cycle is very likely to repeat itself.
Specs
Win 10 x64 1809
i76950x
32 GB DDR4 3200Mhz
Rampage V Extreme Motherboard, with Wireless card in PCIE_X8_2 Slot as shown in manual.
This never happened before the software update that was done months ago. Maybe it has something to do with these errors as well.
-
I rolled back to 1809 and I can confirm my Wireless there works and connects without issue. In 1903 it will take me a few restarts to clear the 10001.9 error. Now I have no issue connects instantly and works on first try every boot.
-
If you need to turn off V-sync in the control panel, then you've got another issue. You need to enable direct mode in SteamVR settings. Any vsync control in Nvidia settings should not affect your headset. Direct mode also increases performance.
-
I also now have this issue. It just started when I updated to the Windows 10 1903 build. I might go back to 1809 I never had an issue when using that build.
-
Your CPU is below minimum requirements. The Wireless VR is very heavy on CPU and it sounds like your potato will not run it well.
-
Same here. Got the set on Black Friday. My controllers never indicate full charge. Haven't tried the replug trick yet, but they don't take long to charge anyway so I just unplug them after about an hour.
Would be nice if this worked correctly like the OG controllers did.
-
My specs:
i7 6950x OC 4.4Ghz 10 core
32GB DDR4 3200Mhz 14-14-14-30
2x 1080Ti Aorus Waterblock Extreme OC 2050+ Core 12528Mhz GDDR5
Rampage V Extreme X99 Motherboard
Intel 750 1.2TB PCIE NVME SSD (OS)
4TBx4 RAID 0 SSHD (GAMES)
This PC is a beast. I've never had it run at very high CPU use until now. I strongly recommend modern 8 core or better to use the wireless system. Screenshot of Task Manager while I was in Fallout 4 VR with Vive Pro wireless:
I have been running with hyperthreading disabled. Will try enabling to see if that alleviates CPU usage at all.
Vive wireless adapter disconnects after a few minutes.
in VIVE & VIVE Pro
Posted
One thing I found is that Windows will often re-enable power saving on the card. Even on the same boot it sometimes becomes enabled again. I just check it before I start VR.