Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

LWRP, Android, Oculus, get OPENGL NATIVE PLUG-IN ERROR

Discussion in 'Shaders' started by linojon, Sep 22, 2018.

  1. linojon

    linojon

    Joined:
    Aug 25, 2014
    Posts:
    69
    Hello, given the following steps
    * created a new unity project,
    * imported the Oculus Utilties, target Android and Oculus SDK (Go),
    * open the GearVController example scene
    * setup for LWRP
    * player settings include OpenGLES3 api, .NET 4.x/Standard 2.0, IL2CPP, ARMv7
    * XR settings: VR enabled, Oculus, Single pass
    * Build and run

    The logcat has the follow errors (dozens if not hundreds of times)

    09-22 12:21:17.951 E/Unity (17300): OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_OPERATION: Operation illegal in current state
    09-22 12:21:17.951 E/Unity (17300):
    09-22 12:21:17.951 E/Unity (17300): (Filename: /Users/builduser/buildslave/unity/build/Runtime/GfxDevice/opengles/GfxDeviceGLES.cpp Line: 340)

    I've tried this in 2018.2.9f1 and 2019.3.0b2
    Is this a unity bug, or a setting i should change, and/or safe to just ignore it?
     
  2. wilkens

    wilkens

    Joined:
    Feb 3, 2014
    Posts:
    4
    Same here in my VR project
     
  3. stenfeio

    stenfeio

    Joined:
    Jan 18, 2015
    Posts:
    11
    @linojon, ever figure out what the issue causing the error is? I'm getting this when I'm loading prefabs from AssetBundles.
     
  4. 13Flo

    13Flo

    Joined:
    Jun 9, 2015
    Posts:
    89
    Same errors here with the exact same config as @linojon (except Unity 2018.3.6).
    Any update on this guys?
     
  5. SahilSinghAVR

    SahilSinghAVR

    Joined:
    Jun 14, 2019
    Posts:
    1
    Experiencing this in 2019.1.9f1, any body has any idea why does this show up
     
  6. rtorresbonetff

    rtorresbonetff

    Joined:
    Jan 3, 2019
    Posts:
    4
    We also have this and it ruins the framerate
     
  7. MSFX

    MSFX

    Joined:
    Sep 3, 2009
    Posts:
    111
    also getting this in 2018.3 Quest project, would love to know why?