Constantine
Constantine
I hope someone will manage to fix it soon. Having the same issue here. I'll be lucky if I have 30s load, instead of 5 minutes 
SteamVR_Action_Vibration: *secondsFromNow* seems to have no effect, haptics always start immediately
Same issue. Seems like this argument doesnt do anything. Had to make a workaround with async/await
SteamVR_Action_Vibration: *secondsFromNow* seems to have no effect, haptics always start immediately
Considering, issue still opened after 2 years, it will never be fixed. So we must make workaround with async/await or coroutines ``` using System.Collections; using System.Collections.Generic; using UnityEngine; using Valve.VR;...
Same issue. After changing any script and reloading scene, controllers are not tracked and any action doesn't work. Tried all suggestions in this topic, none of them helped. EDIT: After...
Fixed by this commit in fork https://github.com/eawoo/AutoLOD/commit/ebc15750f43db7308c5234b37f2841544f1294bc I'm making more fixes in my fork. It includes the fixes from eawoo's fork https://github.com/StCost/AutoLOD/commit/ebc15750f43db7308c5234b37f2841544f1294bc
I might suspect it could be because of issue fixed here: https://github.com/eawoo/AutoLOD/commit/08da8b5e88e6904a4741df13651cff701d820733 I recommend to rebase to fork with fixes https://github.com/eawoo/AutoLOD Or mine fork, I'll add couple more fixes eventually....
I'll add more fixes to my fork https://github.com/StCost/AutoLOD