ZaCkOX Posted March 18, 2018 Share Posted March 18, 2018 The trackpad problem is there, tried on a much older Vive. I am pretty sure you will see the problem if you attempt to re-create it yourself. Could be the hardware to the controller but I believe it probably is connected to the code. You will experience the problem as long as the library that uses the trackpad is connected to this: [unmanagedFunctionPointer(CallingConvention.StdCall)] internal delegate bool _GetControllerState(uint unControllerDeviceIndex, ref VRControllerState_t pControllerState, uint unControllerStateSize); [MarshalAs(UnmanagedType.FunctionPtr)] internal _GetControllerState GetControllerState; To find out if it isn't a code problem, someone would have to follow _GetControllerState, which I cannot. I don't know where the code is nor if I am able to look into it. When I highlight over it, I get: Valve.VR.IVRSystem._GetControllerState(uint unControllerDeviceIndex, ref VRControllerState_t pControllerState, uint unControllerStateSize) Of course I can't find that. But the return of VRControllerState_t is incorrect or the hardware is telling the code it's incorrect. The reason I suppose it is the code is from my belief in experience. After more testing I noticed it is possible to even get vector2 values such like 0.2f to 0.9f while the GetTouch() function return is still positive and nothing is touching it. My belief is the event of a getuntouch is missed and the functions return the belief of being touched when not. Workarounds? I am going to try GetPress() instead. If that becomes the same problem, well then that means the code is wrapped around the same similar design. There is not much I can do from this point because none of it I created or have access to address it. If it is a code problem, it can be fixed much more easily. Hardware... well that's a different story of course. I still believe it is the code though. I trust my gut on it being the code. I been programming for over 10 years and I can imagine how some of that code might be written causing this problem. Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now