Hi all,
I’m having a play with ARCore and while the HelloAR demo builds and runs okay (using the recommended Google recommended player settings), an OpenGL exception is triggered every frame: OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_ENUM.
I’ve tried swapping to / from GLES 3.0 in the texture compression but this seems to make no difference. Anyone else? Ideas what may be triggering this?
This is running on a Galaxy S8.
Assertion failed: AndroidPlayer(samsung_SM-G950F@192.168.0.94 ) OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_ENUM: enum argument out of range
(Filename: ./Runtime/GfxDevice/opengles/GfxDeviceGLES.cpp Line: 368)
1 Like
I am also having that exact same problem.
Neticos
September 3, 2017, 10:43pm
3
CarinaMclane:
Hi all,
I’m having a play with ARCore and while the HelloAR demo builds and runs okay (using the recommended Google recommended player settings), an OpenGL exception is triggered every frame: OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_ENUM.
I’ve tried swapping to / from GLES 3.0 in the texture compression but this seems to make no difference. Anyone else? Ideas what may be triggering this?
This is running on a Galaxy S8.
Check if you use other camera, maybe you have 2 camera on scene
Could you please file a bug report with a minimal reproduction case and reply in here with the case #?
The reproduction case is just looking at something with the camera.
For some reason, my own project seems to produce a more rich log error than the one in HelloARCore.
Please find the below log, it can contain more valuable information:
02-11 11:10:28.444: E/Unity(11501): Could not locate a valid front buffer.1, UInt32&, Double&) 02-11 11:10:28.444: E/Unity(11501): UnityEngine.XR.Tango.TangoDevice:TryGetLatestPointCloud(PointCloudData&) (at /Users/builduser/buildslave/unity/build/Runtime/AR/Tango/ScriptBindings/Tango.bindings.cs:196) 02-11 11:10:28.444: E/Unity(11501): GoogleAR.UnityNative.Device:TryGetLatestPointCloud(PointCloudData&) 02-11 11:10:28.444: E/Unity(11501): GoogleARCoreInternal.PointCloudManager:GetLatestPointCloud() (at PATH\Assets\GoogleARCore\SDK\Scripts\Managers\PointCloudManager.cs:56) 02-11 11:10:28.444: E/Unity(11501): GoogleARCore.Frame:get_PointCloud() (at PATH\Assets\GoogleARCore\SDK\Scripts\Frame.cs:98) 02-11 11:10:28.444: E/Unity(11501): GoogleARCore.HelloAR.PointcloudVisualizer:Update() (at PATH\Assets\Scripts\ARCore\PointcloudVisualizer.cs:61) 02-11 11:10:28.444: E/Unity(11501): [./Runtime/AR/Tango/TangoBufferManager.h line 132] 02-11 11:10:28.444: E/Unity(11501): (Filename: /Users/builduser/buildslave/unity/build/Runtime/AR/Tango/ScriptBindings/Tango.bindings.cs Li 02-11 11:10:28.493: E/Unity(11501): Could not locate a valid front buffer. 02-11 11:10:28.493: E/Unity(11501): UnityEngine.XR.Tango.TangoDevice:TryGetLatestPointCloudInternal(List1, UInt32&, Double&)
At the end the OPENGL NATIVE PLUG-IN ERROR keeps repeating endlessly.
Just one camera on the scene, and also can reproduce on the Galaxy S8.
1 Like
I’m not at my desk currently, but yes, the reproduction case (for me with S8) is literally just building the HelloAR sample scene following instructions.
There was already an issue reported (found it after asking here), on the google-ar/arcore-unity-sdk github. I seconded it and they noted they could reproduce and would follow up with Unity. I can report as issue Unity-side as well, but maybe a bit of a duplication?
Link: OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_ENUM: enum argument out of range · Issue #3 · google-ar/arcore-unity-sdk · GitHub
Note, though, that I don’t think the OPENGL error is the same as the “Could not locate valid front buffer” - while the latter happens intermittently, the OPENGL error happens every frame for me, and irrespective of if the front buffer error has occurred.
1 Like
Could you please file reports via the bug reporter anyway? We need those for internal processing.
2 Likes