ViveSoftware / ViveInputUtility-Unity

A toolkit that helps developing/prototyping VR apps.
http://u3d.as/uF7
Other
353 stars 82 forks source link

HTC Controllers are spawning on 0,0,0 on version 1.8 #28

Closed sergio-nnz closed 6 years ago

sergio-nnz commented 6 years ago

I'am using Steam 1.2.3 and Unity 2017.1 The issue is every time I start the scene the controllers spawn on the scene origin. before Only when I press the system button, go to the steam dashboard and go then press the system button again to back to my scene the trackers work again. after

sergio-nnz commented 6 years ago

Don't if it helps but VRModule.HasInputFocus() also initializes as false.

dariol commented 6 years ago

Hi, please try again with the very latest SteamVR runtime (from 2 days ago) - I was not able to repro with Unity 2017.3 and 2018.1beta

CriticalMammal commented 6 years ago

I seem to be running into the same exact issue. I'm updated to the latest SteamVR update (Feb 13th) and running on Unity 2017.3.1. I think this may actually be an issue with the SteamVR update itself though. There are others who were having issues with controllers suddenly not tracking with the newer update, and the suggested temporary solution is using the "openvr-inputemulator-temporary" beta branch of steamVR. This didn't solve it for me though. Actually it made it worse, the controllers don't appear at all and the steam dashboard trick to get them tracking again doesn't work on that branch.

JeffBail commented 6 years ago

I'm having the same issue with Unity 2017.3.0f3 and SteamVR 1518226924. Jumping into the SteamVR menu and then back out again seems to fix it and the controller models begin tracking. Please note that the date isn't a great way to identify your Steam VR version as the official announcement (http://store.steampowered.com/news/externalpost/steam_community_announcements/2363697377468531896) is dated 2/13 and the Help, About box in Steam VR shows 2/9.

lawwong commented 6 years ago

29

Sorry guys, it was a typo. 060892490f18f041c24896edc617bceeeb3fa37a Please apply the change, should fix it