Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
http://www.yourcablestore.com/USB-Cable-Length-Limitations-And-How-To-Break-Them_ep_42-1.html
Rift uses a lot of data and power. The best way to run one is on a USB 3.0 PCI-E card with a dedicated bus for each port. This will allow full power and bandwidth, before running into any possible cable limitations. You'll also want active 3.0 extension cables for the sensors. The headset won't matter too much, as long as you don't go much over 10 feet extra, so non active HDMI and usb 3.0 cables should be fine here.
My personal setup has a 4 port USB 3.0 PCI-E card (each port with a dedicated bus), 15 ft USB 3.0 active extensions for all the sensors, 10 ft USB 3.0 non-active extension and 10 ft HDMI extension for the headset. This allows me to get fairly large play spaces, pushing outside of what Oculus deems the max play space dimensions. I have stacked on more extentions, when experimenting with even larger play spaces, but it was hit or miss. Usually a lot of unplugging and reconnecting, resetting the application, rinse and repeat. I'd recommend only using one extension per device, and probably not going much over 15-20 feet in length.