Those of you with ASUS motherboards may want to make sure to uninstall whatever version of the ASUS AI Suite software if you haven't already. It causes major problems with a number of core system functions and/or applications including Oculus Home.
Installing an Oculus-compatible or recommended PCI-X USB 3 card such as the Fresco Logic EX1100 can help but there is a further bottleneck. These cards can use up to 2 PCI lanes and it seems the USB 3.x bandwidth can exceed that of what PCI buses can support in the current designs. You can finetune some of this in most MB BIOSes to some extent but that depends on how complex your PC configuration is (i.e, how many USB devices do you have installed in total (these can be significant).
What I'm trying to say is that even though the PCI-X USB extension boards may have 5-7 USB ports, in terms of total bandwidth you can only have one of those utilized by the CV1 headset's usb connector. Plugging in anything else may eventually cause "HDMI disconnects."
So I had to split the Oculus Sensor feed back to the "ASRMedia Blue USB 3.0" port--after disabled charging support and other frills in the BIOS and downgraded the Windows 10 64-bit drivers to the March 7, 2016 "Beta" version obtainable from the Asus Website. The driver notes specifically mention "Oculus optimizations" so it's easy to identify. "ASRMedia" is just another ASUS moniker, BTW. I have also seen reports of some ASUS MB users mitigated the problem by uninstalling all ASUS "ASRMedia" OEM drivers from the system and just using the generic Windows 10 HID drivers instead but that solution did not work for me.
USB-related crashes vs. ED-related crashes can be easily identified because the latter usually preceded by the white hourglass icon popping up a second or two before the game crashes. This can be a result of the memory leak or other exception such as server- or client-side latency. The HDMI disconnect-type of USB-bandwidth drops typically occur while approaching a planet, asteroid-field or other visually rich venue when resource utilization spikes. Annoying indeed...
Installing an Oculus-compatible or recommended PCI-X USB 3 card such as the Fresco Logic EX1100 can help but there is a further bottleneck. These cards can use up to 2 PCI lanes and it seems the USB 3.x bandwidth can exceed that of what PCI buses can support in the current designs. You can finetune some of this in most MB BIOSes to some extent but that depends on how complex your PC configuration is (i.e, how many USB devices do you have installed in total (these can be significant).
What I'm trying to say is that even though the PCI-X USB extension boards may have 5-7 USB ports, in terms of total bandwidth you can only have one of those utilized by the CV1 headset's usb connector. Plugging in anything else may eventually cause "HDMI disconnects."
So I had to split the Oculus Sensor feed back to the "ASRMedia Blue USB 3.0" port--after disabled charging support and other frills in the BIOS and downgraded the Windows 10 64-bit drivers to the March 7, 2016 "Beta" version obtainable from the Asus Website. The driver notes specifically mention "Oculus optimizations" so it's easy to identify. "ASRMedia" is just another ASUS moniker, BTW. I have also seen reports of some ASUS MB users mitigated the problem by uninstalling all ASUS "ASRMedia" OEM drivers from the system and just using the generic Windows 10 HID drivers instead but that solution did not work for me.
USB-related crashes vs. ED-related crashes can be easily identified because the latter usually preceded by the white hourglass icon popping up a second or two before the game crashes. This can be a result of the memory leak or other exception such as server- or client-side latency. The HDMI disconnect-type of USB-bandwidth drops typically occur while approaching a planet, asteroid-field or other visually rich venue when resource utilization spikes. Annoying indeed...
