Skip to main content
MikeF
Inspiring
September 27, 2018

Game breaking issues with home update 1.3.1.0.684290 & unity integration

as of the update to home 1.3.1 getting this error nonstop 
OverflowException: Number overflow.
OVRHapticsClip..ctor () (at Assets/Oculus/VR/Scripts/OVRHapticsClip.cs:27)
OVRHaptics+OVRHapticsOutput..ctor (UInt32 controller) (at Assets/Oculus/VR/Scripts/OVRHaptics.cs:137)
OVRHaptics..cctor () (at Assets/Oculus/VR/Scripts/OVRHaptics.cs:25)
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for OVRHaptics
OVRManager.LateUpdate () (at Assets/Oculus/VR/Scripts/OVRManager.cs:1531)

tried running on 2017.3.1p4 & 2018.1.0b8 and same error in fresh projects with the latest complete integration pack on the asset store. 

This is absolutely crucial that i have a workaround or fix asap, please advise @imperativity


    This topic has been closed for replies.

    11 replies

    MikeFAuthor
    Inspiring
    September 27, 2018
    Note: to reproduce import integration into fresh project, open avatar/samples/controllers/controllers.scene, press play, observe console
    MikeSwanson
    Up and Coming
    September 27, 2018
    I have the same issue. As of Oculus Home 1.31.0.684290, our Unity 2018.1.8f1 project (using the 1.24.2 Utilities) throws this exception constantly:

    [Exception] ArgumentNullException: Value cannot be null.
    Parameter name: dest

    OVRHaptics+OVRHapticsOutput.Process()    Assets/OVR/Scripts/OVRHaptics.cs:237
    235:   int dstOffset = acquiredSamplesCount * OVRHaptics.Config.SampleSizeInBytes;
    236:   int srcOffset = 0;
    -->237:   Marshal.Copy(m_paddingClip.Samples, srcOffset, m_nativeBuffer.GetPointer(dstOffset), numBytes);
    239:   acquiredSamplesCount += desiredPadding;

    OVRHaptics.Process()    Assets/OVR/Scripts/OVRHaptics.cs:362
    360:       for (int i = 0; i < m_outputs.Length; i++)
    361:       {
    -->362:           m_outputs.Process();
    363:       }
    364:   }

    OVRManager.LateUpdate()    Assets/OVR/Scripts/OVRManager.cs:1386
    1384:   private void LateUpdate()
    1385:   {
    -->1386:       OVRHaptics.Process();
    1387:   }

    MikeFAuthor
    Inspiring
    September 27, 2018
    Also intermittently getting the issue mentioned by MikeSwanson 
    MikeFAuthor
    Inspiring
    September 27, 2018
    @imperativity Thanks, always appreciated!
    any idea if this will require an SDK update or be fixed automatically with a new home update?
    MikeSwanson
    Up and Coming
    September 27, 2018
    Thanks, @imperativity...especially that you found time to respond during OC5. :smile:
    oksanatvori
    New Participant
    October 1, 2018
    The same problem at Unity v2018.2.10f1, OVRPlugin v1.28.0 and OVRPlugin v1.29.0
    The workaround is to skip haptics input processing until OVRPlugin.HapticsDesc initialized.
    MikeFAuthor
    Inspiring
    October 1, 2018

    oksana.tvori said:

    The same problem at Unity v2018.2.10f1, OVRPlugin v1.28.0 and OVRPlugin v1.29.0
    The workaround is to skip haptics input processing until OVRPlugin.HapticsDesc initialized.


    Could you show how you're doing this? It seems to re-init on every frame via late update, then as soon as controllers are visible it starts throwing the errors
    oksanatvori
    New Participant
    October 1, 2018
    @MikeF, yes config reloading is called every frame. Just mark OVRHaptics.Config as initialized once it no longer receives garbage data in OVRPlugin.GetControllerHapticsDesc(). 
    MikeFAuthor
    Inspiring
    October 1, 2018
    understood, thanks oksana.tvori
    MikeFAuthor
    Inspiring
    October 1, 2018
    fix should be landing tomorrow from oculus for anyone else having this issue
    Show more replies
    Terms & ConditionsAccessibility statement