Skip to main content
justinwasilenko
Up and Coming
May 28, 2020

Random Crash Occurring on PrimaryTrigger down.

I am trying to get a update out and since updating to 'Unity v2018.4.23f1, Oculus Utilities v1.49.0, OVRPlugin v1.49.0, SDK v1.1.34.0.' I keep getting a random crash. Here is the LogCat log:

05-28 01:19:56.551   725  1325 W TrackingService: Failed call to onButtonDown with error: Status(-129): '-2147483646: '
05-28 01:19:56.551   725  1325 W TrackingService: Failed call to onButtonDown with error: Status(-129): '-2147483646: '
05-28 01:19:56.565   725  1325 W TrackingService: Failed call to onButtonDown with error: Status(-129): '-2147483646: '
05-28 01:19:56.577   725  1325 W TrackingService: Failed call to onButtonDown with error: Status(-129): '-2147483646: '
05-28 01:19:56.612   725  1325 W TrackingService: Failed call to onButtonDown with error: Status(-129): '-2147483646: '
05-28 01:19:56.715  1054  1153 W InputDispatcher: channel '731af9d com.endspace.quest/com.unity3d.player.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
05-28 01:19:56.715  1054  1153 E InputDispatcher: channel '731af9d com.endspace.quest/com.unity3d.player.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-28 01:19:56.717   725   759 I TrackingService: Unregistering client 'pid 2973' by binder death
05-28 01:19:56.717   725   759 I TrackingService: TrackingServiceHost Unregistering client: pid 2973
05-28 01:19:56.717  2128  2143 D RuntimeIPCService: binderDied: com.endspace.quest
05-28 01:19:56.718   696   696 I Zygote  : Process 2973 exited due to signal (11)
05-28 01:19:56.718  1054  1487 I WindowManager: WIN DEATH: Window{731af9d u0 com.endspace.quest/com.unity3d.player.UnityPlayerActivity}

    5 replies

    MikeF
    Inspiring
    May 28, 2020
    Can you post the code responsible for the trigger down call? 
    justinwasilenkoAuthor
    Up and Coming
    May 28, 2020

    MikeF said:

    Can you post the code responsible for the trigger down call? 


    if (OVRInput.Get(OVRInput.Button.PrimaryIndexTrigger) || OVRInput.Get(OVRInput.Button.SecondaryIndexTrigger))
    {
        playerFire.Fire();
    }
    MikeF
    Inspiring
    May 28, 2020
    no problems there by the looks of it so id start backtracking on your unity and oculus updates if possible. It could be a problem with oculus, unity or a mix of both but updating both at the same time makes it hard to track down.
    Also, a bit of a longshot but have you tried setting the ovr manager input to controllers only instead of the default hands and controllers?
    justinwasilenkoAuthor
    Up and Coming
    May 28, 2020

    MikeF said:

    no problems there by the looks of it so id start backtracking on your unity and oculus updates if possible. It could be a problem with oculus, unity or a mix of both but updating both at the same time makes it hard to track down.
    Also, a bit of a longshot but have you tried setting the ovr manager input to controllers only instead of the default hands and controllers?


    Hey MikeF, I had already set it to Controllers Only. I am not sure if the Unity / Oculus version is the root cause, because in the Quest Store reviews there have been a few reports of the game crashing while pulling the Primary Trigger.

    So it's happening with the live version of the game as well, but it never happened during testing before the games release in August. 
    justinwasilenkoAuthor
    Up and Coming
    July 7, 2020
    I have discovered the problem finally. It was a result of using OVRHaptics to vibrate the controllers instead of OVRInput.SetControllerVibration on the Quest which resulted in this crash.
    Terms & ConditionsAccessibility statement