SteamVR_UpdatePoses deprecation removes the controllers
See original GitHub issueThere is no way to see the controllers with the current version of the SteamVR plugin. Even adding the Update Poses script to the Camera component in the [CameraRig]
doesn’t do anything because the script is automatically removed now with this message:
SteamVR_UpdatePoses has been deprecated - REMOVING UnityEngine.Debug:Log(Object) SteamVR_UpdatePoses:Awake() (at Assets/SteamVR/Scripts/SteamVR_UpdatePoses.cs:14) UnityEditor.HostView:OnGUI()
Issue Analytics
- State:
- Created 6 years ago
- Comments:28 (1 by maintainers)
Top Results From Across the Web
Staking Controller Deprecation Plan + Staking UI Leads ...
It firstly removed controller configuration from the nominator setup flow, then iteratively removed or decreased the screen estate of controller ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Try removing the following in SteamVR/Scripts/SteamVR_Render.cs in OnCameraPreCull:
This was added to fix a specific issue someone was having, but does not appear to work as expected.
This should only affect Unity version 5.5.x through 5.6.x.
For the following errors:
I believe this is printed for each of the base station models as they do not have animated components. This is expected and not an error. The script prints out this warning because createComponents is set to true, but no components are found. The ‘example’ scene sets up a render model for each found tracked object, which includes base stations and cameras which may not have animated components.
This is due to a change to the runtime some time back. To avoid spinning up all of SteamVR, the render model script will call OpenVR.Init with VRApplication_Utility and then OpenVR.Shutdown when it’s finished loading render model data. This only happens when SteamVR isn’t already running. The problem is that vrserver used to stick around for 2 seconds after the last connection, which covered bridging multiple calls. More recently, vrserver was updated to shut down more responsively, however, it broke this use case. I’ll update vrserver to be a bit smarter to avoid this going forward.
I am using 2018.3 but it does not work. Any help?