Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
This makes writing or responding to chat messages within VRC very tedious, even more than it was already.
Moreover I've noticed that once the double input issue starts, it tends to be controller dependent (might only be the left or right controller that does it) AND it depends on both controller lasers pointing at the keyboard, the issue resets itself once the "other" laser is moved off the keyboard.
the way i type in vr has not changed. other vr keyboards like XS overlay and OVRtoolkit work perfectly fine. this has now been an issue for nearly 7 months. it first began as part of the SteamVR 2.0 update in october 2023. behavior changed slightly with one update between then and now that reduced double inputs, but increased missed keystrokes.
if you press a key with one controller, and then press a second key with the other controller, before fully releasing the first trigger, the first input will be skipped and ignored.
typed in steamVR: it's posibe o mis nearl hl of all keytoks typing this wy uikly
typed in OVR toolkit: it's possible to miss nearly half of all keystrokes typing this way quickly.
this behavior, again, was added in october 2023 and has not yet been properly addressed.
originally, the behavior would double-verify, as follows with an example of the word "to":
action sequence referenced below: left controller presses 't'. right conroller presses "o'. left controller releases 't'. right controller releases 'o'.
oct.2023 behavior: the moment 'o' is pressed, it interrupts the left input, adding 't' as if we had released the trigger, when we havent. then when left trigger is released it registers that finalized input and a second 't' is added. then 'o' is added when releasing the right trigger.
result: "tto"
unknown 2024 update behavior: when right trigger pressing 'o' interrupts the left trigger pressing 't' like in the example above, it now ignores both the interrupt 'false input' AND the actual trigger release that follows. right trigger is allowed to complete its input.
result: "o"
with the exception of the garbled mess example, i typed this entire post in OVR toolkit.