-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Got a black screen with Viro3DSceneNavigator. #305
Comments
I build the iOS version without errors, 3DObject is visible and draggable. Any known issue for Viro3DSceneNavigator on Android ? |
Hi @Charlynux, we do not have any known issues but we will look into this. Thanks for reporting. Just to clarify, the issue you are seeing is only for Viro3DSceneNavigator on Android? Also, can you tell us what device you are using when you see this error? |
You're right the issue is only for Viro3DSceneNavigator on Android. I tested it on two devices :
If you need more informations, just ask. |
Hi @Charlynux, thanks for helping us resolve this bug. When you start the app, Viro should print out the GPU type your device is using. Can you let me know what it says? It should look something like this: GPU vendor [Qualcomm], renderer [Adreno (TM) 530] Raj |
Hello, Here is what I get : Wiko U Feel Lite Huawei Honor 7 Hope it can help you. |
@dam00n same here I see only black screen instead of camera view any solution? OS: Android 10 |
Hello,
I work on a React Native app and we would like to integrate some 3D views.
My first scenes with Text, 360Image or 3DObject works well with a ViroVRSceneNavigator.
But I would like to use Viro3DSceneNavigator instead.
When I switch the scene navigator, I just got a black screen.
Looking at the Android logs I found this :
At the moment, I work with Android, but will need iOS as well.
My dependencies versions :
I found an issue which the same warnings in ViroCore. viromedia/virocore#9
But can't figure if there some relation between the two problems.
Is there a way to find more informations for debugging ?
The text was updated successfully, but these errors were encountered: