#USERTREADMILL shows no input on test and SkyrimVR won't take input - Oculus Quest on Virtual Desktop #70
Comments
|
Are you on SteamVR beta? What HMD are you using? |
|
Oculus Quest through Virtual Desktop. I had it on SteamVR Beta, but I've since opted out of beta and it still hasn't worked. |
|
I don't know how the Quest tracking data is transferred into SteamVR, I think it takes another driver, which may interfere with this driver... |
|
The tracking data seems to be fine because I can create a model and see
tracking data on the graph. I believe Virtual Desktop emulates an Oculus
Rift S (or whatever driver the Oculus software now uses for Steam VR).
For all intents and purposes, you can pretend I own a Rift and it's just
not working even though I can see and record tracking data. Any ideas?
…On Thu, Apr 2, 2020 at 12:13 AM pottedmeat7 ***@***.***> wrote:
I don't know how the Quest tracking data is transferred into SteamVR, I
think it takes another driver, which may interfere with this driver...
They only way I know a quest would work, is with SteamVR lighthouses and a
HTC tracker. Then you disable HMD tracking.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5JQ3ZQBWQAQHFS7TYWJK3RKQGILANCNFSM4LY6QEIA>
.
|
|
I tested again and can confirm that, while after I check the ENABLE box I can see and select the active controller device OVR_WIP in the legacy settings, my Steam VR overlay on my PC desktop is only showing my HMD and 2 touch controllers. There's no 3rd controller lit. |
|
When you look at the HMD data model with enabled checked. Do you see any green or red lines? |
|
You're right. I don't see Y Vel green line for the HMD, so it might be
tracking differently than you had set the system up for. I tried setting
the headset to "other" and still didn't work.
…On Thu, Apr 2, 2020 at 9:14 PM pottedmeat7 ***@***.***> wrote:
When you look at the HMD data model with enabled checked. Do you see any
green or red lines?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5JQ3YE7EHJNW6KEHDSIYTRKU2ABANCNFSM4LY6QEIA>
.
|
|
Sounds like the same problem here #62 |
|
I really wish you owned a Quest. No idea why it later started working. Do
you still have a Rift and can test?
…On Sat, Apr 4, 2020 at 4:06 PM pottedmeat7 ***@***.***> wrote:
Sounds like the same problem here #62
<#62>
I had this issue with Rift not supplying the vVelocity data and it was
always 0. But later it seemed to start working after an update by SteamVR
or Oculus SDK...
The Other setting just tries to determine the velocity by change in
position. If it doesn't work then that data is also not available.
Im not sure if there is anything I could do, unless I really research how
those drivers work, I don't have a Quest.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5JQ35NBW6AJMIITKF5NQTRK6HK3ANCNFSM4LY6QEIA>
.
|
|
I tested the new version you released that calls one HMD Steam VR and the
other Other. Blue and Red Pitch and Yaw work, but Y_Vel is still being
stubborn and not working. I will ask ggoddin the dev of VD and see if he
has any insight.
…On Sat, Apr 4, 2020 at 9:58 PM i.Silver ***@***.***> wrote:
I really wish you owned a Quest. No idea why it later started working.
Do you still have a Rift and can test?
On Sat, Apr 4, 2020 at 4:06 PM pottedmeat7 ***@***.***>
wrote:
> Sounds like the same problem here #62
> <#62>
> I had this issue with Rift not supplying the vVelocity data and it was
> always 0. But later it seemed to start working after an update by SteamVR
> or Oculus SDK...
> The Other setting just tries to determine the velocity by change in
> position. If it doesn't work then that data is also not available.
> Im not sure if there is anything I could do, unless I really research how
> those drivers work, I don't have a Quest.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#70 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AH5JQ35NBW6AJMIITKF5NQTRK6HK3ANCNFSM4LY6QEIA>
> .
>
|
I performed all the configuration steps, ovr_wip shows as 000. I set the bindings to your custom profile, left hand return. When I go to test controller no matter what I do the test won't light up the USERTREADMILL controller buttons at all, and Skyrim VR is not seeing any movement. Would love to chat you up on discord to see if I can get it working (will make a small donation if you can help me get this working on SkyrimVR so I can finally enjoy the game).
The text was updated successfully, but these errors were encountered: