Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Controllers and trackers spawning order #6

Open
Eirenliel opened this issue Sep 29, 2021 · 1 comment
Open

Controllers and trackers spawning order #6

Eirenliel opened this issue Sep 29, 2021 · 1 comment
Labels
Priority: Normal The default priority Type: Bug Something isn't working

Comments

@Eirenliel
Copy link
Member

Apps like VRChat require controllers to be added before FBT trackers. We need to insure at all times that

  • Trackers spawning is slightly delayed after SteamVR starts
  • If controllers are handled by SlimeVR, they have to be spawpned first
@TheButlah TheButlah added the Status: Unlabeled A maintainer has not yet labeled this label Oct 5, 2022
@GapVR
Copy link

GapVR commented Feb 24, 2023

Problem: VRChat world gimmicks/game controls do not work, Vive tracker puck seen on right hand.
Workaround: Turn on controllers before starting the SlimeVR Server.

Posting this here since my problem with VRChat is likely related to this issue:

Using Vive 1.0 Wand Controllers with SteamVR on Windows 10.

Had an issue with VRChat not recognizing my controller input for Udon Input Events^ for World gimmicks/game controls/World specific menus. The cause was found to be me turning the controllers on after the SlimeVR Server was started. It also placed a Vive Tracker puck (which is visible in VRC when large menus are opened, but not in the SteamVR void) on my right hand (likely because that is switched on first).

The pair of controllers (I haven't tested multiple pairs yet) turned on before the SlimeVR Server is registered as the only pair of controllers recognized by VRC and any controllers swapped in after exhibits the problem above.

^ Udon Input Events are device specific and independent of SteamVR control bindings.

Meister1593 added a commit to Meister1593/SlimeVR-OpenVR-Driver that referenced this issue Mar 22, 2023
@ButterscotchV ButterscotchV added Type: Bug Something isn't working Priority: Normal The default priority and removed Status: Unlabeled A maintainer has not yet labeled this labels May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Normal The default priority Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants