Neos-Metaverse / NeosPublic

A public issue/wiki only repository for the NeosVR project
193 stars 9 forks source link

Controllers are not working in tVR mode with Driver4VR #2852

Open gb2111 opened 3 years ago

gb2111 commented 3 years ago

Describe the bug?

Driver4VR has the feature of playing Virtual Reality games on TV or Monitor. https://www.youtube.com/watch?v=GsHcLAm_pVk

While trying to play Neos the controllers are not detected. When using other headset and for example Kinect for hand and head tracking it works. I tried working with different settings but it doesn't work.

Relevant issues

No

To Reproduce

  1. Install Driver4VR https://store.steampowered.com/app/1366950/Driver4VR/
  2. Start SteamVR with no headset connected. When Driver4VR start you need enable tVR mode like in video above
  3. Enable Virtual Trackers (also like instructed on the video)

In SteamVR they will be visible but once you start Neos they are gone. When using other headset like RiftCat or iVRy the controllers work fine. Any help would be appreciated.

Expected behavior

The controllers are working in tVR mode.

Log Files

No response

Screenshots

No response

How often does it happen?

Always

Does the bug persist after restarting Neos?

Yes

Neos Version Number

2021.8.18.1077

What Platforms does this occur on?

Windows

Link to Reproduction Item/World

No response

Did this work before?

No

If it worked before, on which build?

No response

Additional context

No response

Reporters

No response

shadowpanther commented 3 years ago

Could you clarify several things:

Frooxius commented 3 years ago

Can you please share a log from starting up with this configuration? Neos likely doesn't detect the right controller type, because they report themselves as something different, so we might need to add them to the list to be detected properly.

gb2111 commented 3 years ago

Hi. I am uploading the log. Please note that the controllers work when I use them in VR mode (with app like RiftCat or iVRy) but don't work with my own HMD driver. Player.log Thanks.

gb2111 commented 3 years ago

Sorry, I forgot ot answer other questions:

Frooxius commented 3 years ago

@gb2111: Thanks for the log, but I need the actual Neos log unfortunately, instead of the Unity one.

gb2111 commented 3 years ago

@Frooxius can you please clarify where is exactly the log I should provide ? Thanks

shadowpanther commented 3 years ago

can you please clarify where is exactly the log I should provide ?

In the Neos's install folder (Browse local files from Steam), subfolder Logs.

gb2111 commented 3 years ago

I am attaching logs GREGMSI - 2021.10.17.1326 - 2021-10-19 09_57_28.log .

gb2111 commented 2 years ago

@shadowpanther Did you have a chance to take a look? Thanks.

masq31 commented 2 years ago

I've also experienced this issue in driver4vr. The issue seems independent of tVR. It appears to be related to controller inputs handled between NEOS and driver4vr.

The current workaround observed is to use the launcher with the toggle "Force Legacy Steam VR Input Handling" or with the command "-LegacySteamVRInput"

When the game is launched with this setting, the driver4vr virtual hand trackers configured will work as intended.