Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
thanks for this info!
I was running 1x 1440p, 2x 1080p and 1x TV (1080p).
When the Vive first showed up i didn't have an extra displayport cable so I had to unplug my TV to use the HDMI slot (Bringing the total to 4 devices including the Vive). Worked great.
Just got the displayport cable and adding the Vive caused me a 306. Rebooted, Reinstalled Vive Drivers, Re installed nVidia drivers, rolled back nVidia drivers etc etc.
Finally found your comment and just disabled my TV in the control panel and everything works flawlessly.
Thanks man!
Be sure to have Monitor and HMD both plugged into the Video Card...... not one plugged into the motherboard graphics.
For laptops, set Prefered Graphics Processor to Nvidia High Performance....... in Nvidia Control Panel \ Manage 3D Settings...... under SteamVR in the programs list.
Delete and reinstall steam vr and Bingo !
Tried everyting other cable bla bla bla this is the things who work for me
At one point, I did opt out of the beta for SteamVR, going back to 1.1.4... but the error remained.
I even uninstalled and reinstalled SteamVR, and left it in the 1.1.4 (non-beta) version and STILL the error remained!
I then opted IN to the beta again, and sure enough, still had the error... but when I opted OUT of the beta a second time, ONLY THEN did the error finally go away and SteamVR started successfully!
So, it was like just installing and staying in 1.1.4 by itself wasn't good enough. I had to opt IN, and then back OUT to fix it. No idea why, but at least it's working now.