So, I did everything correctly, other device seems to work fine but when I trasnfer the apk to my Oppo F11 Pro, the AR camera display only pink and green with a black and white background.
What's wrong here ?
if I download application from app store, it's fine too. I think I might be missing out something during the build.
| Attachment | Size |
|---|---|
 Bug mentioned photo.jpeg | 52.75 KB |
Where this code should be placed?
/*=============================================================================== Copyright 2019 PTC Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ===============================================================================*/ #ifndef VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED #define VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED struct v2f { float4 pos : SV_POSITION; float2 uv : TEXCOORD0; float2 uv2 : TEXCOORD1; }; sampler2D _MainTex; float4 _MainTex_ST; sampler2D _UVTex1; float4 _UVTex1_ST; v2f vuforiaConvertRGBVert(appdata_base v) { v2f o; o.pos = UnityObjectToClipPos(v.vertex); #if VUFORIA_YUVNV12 o.uv = TRANSFORM_TEX(v.texcoord, _MainTex); o.uv2 = TRANSFORM_TEX(v.texcoord, _UVTex1); #else o.uv = TRANSFORM_TEX(mul(v.texcoord, 1), _MainTex); o.uv2 = TRANSFORM_TEX(mul(v.texcoord, 0.5), _UVTex1); #endif return o; } half4 vuforiaConvertRGBFrag(v2f i) : COLOR { half4 c; half y = tex2D(_MainTex, i.uv).r; half2 uv = tex2D(_UVTex1, i.uv2).rg; #if VUFORIA_YUVNV12 half4 v4yuv1 = half4(y, uv, 1.0); c.r = dot(half4(1.1640625, 0.000000000, 1.5957031250, -0.87060546875), v4yuv1); c.g = dot(half4(1.1640625, -0.390625000, -0.8134765625, 0.52929687500), v4yuv1); c.b = dot(half4(1.1640625, 2.017578125, 0.0000000000, -1.08154296875), v4yuv1); c.a = 1.0; #else half4 v4yuv1 = half4(y, uv, 1.0); half r = dot(half4(1, 2.03211, 0.000000000, -1.08154296875), v4yuv1); half g = dot(half4(1, 0.000000000, 1.13983, -0.67060546875), v4yuv1); half b = dot(half4(1, -0.39465, -0.58060, 0.52929687500), v4yuv1); if (r < 0) r = 0; if (g < 0) g = 0; if (b < 0) b = 0; if (r > 255) r = 255; if (g > 255) g = 255; if (b > 255) b = 255; c.r = r; c.g = g; c.b = b; c.a = 1.0; #endif return c; } #endif //VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED
Having the exact same problem - using a moto e6 plus. All the interactions still work and I installed it on my sisters phone (Huawei) and it worked fine so it has to be a hardware problem. Does anyone have a workaround yet??
| Attachment | Size |
|---|---|
| Screenshot_20200726-193233.png | 1.57 MB |
Well, seems like the problem is in VideoBackground shader (Packages/Vuforia Engine AR/Vuforia/Shaders). To be more particularly with YUVNV21 in VB_YUVNV12_YUVNV21.
Spend couple hours to search info about, found a way to remove image split on 4 images on the screen and used the formulas to calculate conversion from YUVNV21 to RGB, but it doesnt work properly for now(seems like it recognize green color as a blue).
Still, it looks better than pink and green.
Highlighted with green the region, corresponds for removing 4 images(Not sure, but seems like _MainTex corresponds to your AR target image, _UVTex1 - to background camera view, so multiplying it by 1/2 reduces the number of images to 1).
Highlighted with yellow region corresponds to color conversion from YUVNV21 to RGB. Playing with values at higlighted pink region you can find the values, that corresponds to proper display of all colors from camera to your screen. The main problem is 4th value of vector, coz its alpha channel and i didint find specification for conversion, that contains 4 dimensional vector.
So, if you will find proper values - feel free to share, guys)
P.S. IDK, why vuforia couldnt fix this problem for years, maybe its really device connected problem, but you always can create special file for list of problem devices, so people in future will not have such problem.
/*=============================================================================== Copyright 2019 PTC Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ===============================================================================*/ #ifndef VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED #define VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED struct v2f { float4 pos : SV_POSITION; float2 uv : TEXCOORD0; float2 uv2 : TEXCOORD1; }; sampler2D _MainTex; float4 _MainTex_ST; sampler2D _UVTex1; float4 _UVTex1_ST; v2f vuforiaConvertRGBVert(appdata_base v) { v2f o; o.pos = UnityObjectToClipPos(v.vertex); #if VUFORIA_YUVNV12 o.uv = TRANSFORM_TEX(v.texcoord, _MainTex); o.uv2 = TRANSFORM_TEX(v.texcoord, _UVTex1); #else o.uv = TRANSFORM_TEX(mul(v.texcoord, 1), _MainTex); o.uv2 = TRANSFORM_TEX(mul(v.texcoord, 0.5), _UVTex1); #endif return o; } half4 vuforiaConvertRGBFrag(v2f i) : COLOR { half4 c; half y = tex2D(_MainTex, i.uv).r; half2 uv = tex2D(_UVTex1, i.uv2).rg; #if VUFORIA_YUVNV12 half4 v4yuv1 = half4(y, uv, 1.0); c.r = dot(half4(1.1640625, 0.000000000, 1.5957031250, -0.87060546875), v4yuv1); c.g = dot(half4(1.1640625, -0.390625000, -0.8134765625, 0.52929687500), v4yuv1); c.b = dot(half4(1.1640625, 2.017578125, 0.0000000000, -1.08154296875), v4yuv1); c.a = 1.0; #else half4 v4yuv1 = half4(y, uv, 1.0); half r = dot(half4(1, 2.03211, 0.000000000, -1.08154296875), v4yuv1); half g = dot(half4(1, 0.000000000, 1.13983, -0.67060546875), v4yuv1); half b = dot(half4(1, -0.39465, -0.58060, 0.52929687500), v4yuv1); if (r < 0) r = 0; if (g < 0) g = 0; if (b < 0) b = 0; if (r > 255) r = 255; if (g > 255) g = 255; if (b > 255) b = 255; c.r = r; c.g = g; c.b = b; c.a = 1.0; #endif return c; } #endif //VUFORIA_VB_YUVNV12_YUVNV21_INCLUDED
I'm also have the same problem here but a check on "Include ARCore Library" in VuforiaConfiuration seems to fixed it. But this lead to another problem which is the app keep crashing. Is anybody encountered anything similar? Or anyone encountered solutions for this?
Hello, I am Joe
I have same problem.
My device is Oppo F11 Pro.
| Attachment | Size |
|---|---|
| Recall_132227533663639560.png | 2.43 MB |
Hello. Have same problem here. it started after i import google vr. Delete it even open new project but still this happens. In other phones no problem but my Sony Xperia XA1 ultra this happens. Itry open Google Play Stro apps but even there it happens. Anyone know solution?
Pics here.
https://ibb.co/MVskZzt
https://ibb.co/52Gdym8
https://ibb.co/pW4PVzj
unity 2019.1.9f1
vuforia 8.3.8
Hi,
Based on the imageTarget I assume you are using Unity to developer your application. Unity handles all the rendering based on the Graphics engine you select in the build settings.
I would advise to change it from Auto to Open GL ES 2 or 3 and try it out. However if this will not solve the issue and the same application, with the same build configuration is working on other devices , the error that you are facing would be device related.
Thank you.
Vuforia Engine Support
I believe it should be in "Library/PackageCache/com.ptc.vuforia.engine@8.5.9/Vuforia/Shaders/VuforiaVB_YUVNV12_YUVNV21.cginc", but it did not address the issue for me. You may need to adjust that directory based on your Vuforia version.
This bug is fixed in Vuforia 10.2.5 and Unity 2021.1.16f1 on my Kindle Fire 10" 2019. For anyone who CAN upgrade, you should try that out.
I am stuck on Vuforia 8.5.9 and Unity 2019.2.21f1 however and can't upgrade, and I have not found a fix.