Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

Sceneform plugin:1.15.0 with Android Studio 3.6 not working at all #1078

Open
ayush-android opened this issue May 5, 2020 · 5 comments
Open

Comments

@ayush-android
Copy link

Android Studio 3.6.3
Build #AI-192.7142.36.36.6392135, built on April 14, 2020

Android gradle plugin 3.6.3
SceneForm plugin 1.15.0

The plugin installed correctly. But I have faced these errors when using it:

  1. Import Sceneform Asset is not working at all. It is giving Error: java.lang.RuntimeException.
    However I used the alternate way to create .sfa and .sfb files.

  2. The Viewer is not showing anything. When I am trying to open the .sfb file in Viewer, it is showing blank screen. I have attached the screenshot for the same.

Is there any way to see the .sfb file?

Thanks

image

@wangtsung
Copy link

Use Android Studio 3.5 and use this plugin you can see it

@ayush-android
Copy link
Author

Is there any chance to fix this in version 1.16.0 ?

@Consti10
Copy link

Consti10 commented May 6, 2020

From my experience with Sceneform in the last 1 year I would say:
No, they are probably not going to fix it.
If you want Android Studio 3.6.3 use the new open source version.
If you want Sceneform plugin:1.15.0: Use 3.6.5 or lower

@tellypresence
Copy link

tellypresence commented May 7, 2020

Duplicate of #989

If you need to use the legacy fbx to sfb workflow, best workaround is as suggested
above: use 3.5 solely for using the sceneForm plugin; set up a dummy Android Studio
project just for converting assets. Copy/move the sfb files to res/raw in your actual
project which you can freely open in Android Studio 3.6/4.0/4.1 etc; the sfb is entirely self-contained so you don't need the .sfa etc in your project, nor at runtime (and you don't need the auto-created-by-sceneform-plugin 3D asset entries in build.gradle either)

@ayush-android
Copy link
Author

Thanks @Consti10 and @tellypresence for the workarounds. But its really frustrating to use two Android Studio with a window system of 8gm RAM because Android Studio utilize too much RAM.
As this issue is same as #989 then they should fix this as almost three months has been completed to filed that issue.
I understand the workarounds and thats completely ok to use them but really this type of things does not suit on such big companies product.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants