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)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
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
How do the Index controllers communicate, anyway? Is it also Bluetooth? Because they work flawlessly.
Shutting down the base stations seems way more reliable than back in December, when I tried an earlier version of 20H1, so there's at least that.
Dear God in heaven, look into this, Valve!
If I want to turn them off, I keep hitting Refresh All until it sees all of them, then immediately shut down SteamVR.
So far it's been more reliable, but I'm not entirely sure. That said, I'm intentionally posting about it, so that it breaks, like last time.
That said, time to the Lighthouses reacting to wake commands does seem shorter.
Come on, Valve. The new Windows 10 version is on Release Preview already.
A really good example with Nvidia and Windows changes is the fullscreen optimizations fiasco and G-Sync. When 1803 came out with WDDM 2.4, enabling true exclusive fullscreen in D3D9 games breaks G-Sync completely. It just doesn't work. Nvidia never got around to fixing this problem neither before 1803's release nor after. It gets better. On 1903 and newer, not only does this scenario break G-Sync completely, but it also results in massive artifacting if you don't cap your FPS. Only solution is to either turn FSO back on or disable G-Sync for that game.
It's just frustrating to be at the bottom rung of the ladder in this whole setup where these different companies fail to communicate with each other, and it all falls down on us. Why isn't Valve looking at this Bluetooth problem? What's going to happen in a month when 2004 starts rolling out on customers PCs and SteamVR cannot properly manage lighthouse power states? The answer is obvious, we will continue to be screwed over and have to wait for the solution to come from either Microsoft or Valve. I'm just so tired of this situation happening when there's 0 excuse for it in the first place.