Search Issue Tracker

Duplicate

Votes

3

Found in

2017.4.1f1

Issue ID

1024725

Regression

Yes

[Android][VR] OpenGL Native plugin errors thrown on devices with Adreno GPU when using Tesselation shader

XR SDK

-

How to reproduce:
1. Open attached user project
2. Build & Run Player on Android (default VR SDK is Oculus, but it reproduces on other SDK's as well)
3. Observe the logcat

Expected result: No errors are thrown when using Tesselation shader
Actual result: "OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_OPERATION: Operation illegal in current state" and "OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_VALUE: Numeric argument out of range" are thrown in logcat

Reproducible with - 2018.2.0b1, 2018.1.0f1, 2017.4.1f1, 2017.3.0a1

Notes:
1. Reproduces with Daydream, GearVR, Cardboard
2. Reproduced with both Single-Pass and Multi-Pass rendering methods

DUT:
Reproducible with:
Google Pixel 2, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 540, Build:google/walleye/walleye:8.0.0/OPD1.170816.010/4311506:user/release-keys
Samsung SM G950U
, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 540, Build:samsung/dreamqltesq/dreamqltesq:7.0/NRD90M/G950USQU1AQC8:user/release-keys
Xiaomi Redmi Note 4, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 506, Build:xiaomi/mido/mido:7.0/NRD90M/V8.5.4.0.NCFMIED:user/release-keys

Not reproducible with:
Samsung SM G950F, OS:8.0.0, CPU:arm64-v8a, GPU:Mali-G71, Build:samsung/dreamltexx/dreamlte:8.0.0/R16NW/G950FXXU1CRB7:user/release-keys
Samsung SM G930F, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:samsung/heroltexx/herolte:7.0/NRD90M/G930FXXS1DQHF:user/release-keys
Samsung SM G903F
, OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-T720, Build:samsung/s5neoltexx/s5neolte:6.0.1/MMB29K/G903FXXU1BQC1:user/release-keys
Xiaomi MI PAD*, OS:4.4.4, CPU:armeabi-v7a, GPU:NVIDIA Tegra, Build:Xiaomi/mocha/mocha:4.4.4/KTU84P/V9.2.3.0.KXFCNEK:user/release-keys

  1. Resolution Note (2018.3.X):

    Fixed in 2017.4.8f1 by pull request #70543.

Comments (3)

  1. Brain-_-Fail

    Aug 28, 2018 11:58

    Same is the case with Unity 2018.1.3f1.Something with this issue causes tremendous lag in AR applications using Vuforia when a trackable is found.

Add comment

Log in to post comment