Skip to main content
jimorcherton
New Participant
March 8, 2022

Lot's of Errors in the Console when trying to run Unity game.

Hello everyone. I'm hoping someone may have some things I can try here because I'm desperate. I tried to get haptics to work with a few tutorials and there doesn't seem to be anything wrong with my code. I've modified the OVRgrabber.cs to include the following.

 

It started to work and then something either was modified or maybe altered to get this error below.

 

OVRHapticsClip hapticsclip = new OVRHapticsClip(audioClip);

if (m_controller == OVRInput.Controller.LTouch)

OVRHaptics.LeftChannel.Preempt(hapticsclip);

else

OVRHaptics.RightChannel.Preempt(hapticsclip);

 

Everything seemed to be working fine but when I looked at the console I got this.  Hundreds of errors appearing and I've tried everything to try to rectify this. I've replace OVRhaptics and the OVRmanager to the older version without success.  I've opened the samples that Oculus includes with the integration kit and these all have this error too.  There doesn't seem to be any performance problems which is odd. I can't however seem to get haptics to come back after this error started popping up.

 

Please help! I'm desperate. I'm running the latest integration kits with 2019.4.36f1

 

 

 

3 replies

jimorchertonAuthor
New Participant
March 9, 2022

Anything would help guys.

GameSe7en
New Participant
March 10, 2022

I'm not versed in the current haptics support, but I'd start by either adding a Log statment or attaching a debugger to the offending line and seeing what that null reference is to.

 

A quick scan of the code you've shared suggests that preempt will clear the pendingClip list and add only your clip to the head of the list.

The failing line seems connected to "padding" (i.e. if(m_paddingEnabled))

That member seems to be typically false for UNITY_ANDROID.

When I ran my app under the editor window and stopped in the init call for m_paddingClip, m_paddingEnabled is set to false for me.  As a result, my execution always stepped over the "m_paddingEnabled" block between llines 242-259.

I'm not certain what the paddingClip is intended to perform as it just looks to be a default initialized HapticsClip with settings driven by the overall Haptics config.

Sorry I can't help more, but I thought I'd share my observations.

jimorchertonAuthor
New Participant
March 10, 2022
GemSe7en.  You are a god but not the god!!
 That fixed it!
 
 Many Many thanks!
    Terms & ConditionsAccessibility statement