I added a gesture detector but it is not working as it should. I created a sample app called sample-model-gestures to test out my gesture detector but it is very buggy. Below is the modification I made to SceneView.kt:

inner class OnGestureListener : GestureDetector.SimpleOnGestureListener() {
    override fun onSingleTapUp(motionEvent: MotionEvent): Boolean {
        val hitTestResult = surfaceGestureDetector.pickHitResult
        onTouch(hitTestResult.node, motionEvent)
        return true
    }

    override fun onDown(e: MotionEvent): Boolean {
        return true
    }

    override fun onSingleTapConfirmed(e: MotionEvent?): Boolean {
        gestureType = GestureType.SINGLE_TAP
        return super.onSingleTapConfirmed(e)
    }

    override fun onDoubleTap(e: MotionEvent?): Boolean {
        gestureType = GestureType.DOUBLE_TAP
        return super.onDoubleTap(e)
    }

    override fun onLongPress(e: MotionEvent?) {
        super.onLongPress(e)
        gestureType = GestureType.LONG_PRESS
    }

    // https://gist.github.com/TheIcemanCometh/57d0f9ae7b70dcdcc4d9
    override fun onFling(
        e1: MotionEvent?,
        e2: MotionEvent?,
        velocityX: Float,
        velocityY: Float
    ): Boolean {
        if (e1 != null && e2 != null) {
            val diffY = abs(e1.y - e2.y)
            val diffX = abs(e1.x - e2.x)
            if (diffY > SWIPE_MAX_OFF_PATH) {
                if (diffX > SWIPE_MAX_OFF_PATH || abs(velocityY) < SWIPE_THRESHOLD_VELOCITY) {
                    return false
                }
                if (e1.y - e2.y > SWIPE_MIN_DISTANCE) {
                    gestureType = GestureType.FLING_UP
                }
                else if (e2.y - e1.y > SWIPE_MIN_DISTANCE) {
                    gestureType = GestureType.FLING_DOWN
                }
            }
            else {
                if (abs(velocityX) < SWIPE_THRESHOLD_VELOCITY) {
                    return false
                }
                if (e1.x - e2.x > SWIPE_MIN_DISTANCE) {
                    gestureType = GestureType.FLING_LEFT
                }
                else if (e2.x - e1.x > SWIPE_MIN_DISTANCE) {
                    gestureType = GestureType.FLING_RIGHT
                }
            }
        }
        return super.onFling(e1, e2, velocityX, velocityY)
    }
}

Please have a look and let me know what I could be doing wrong. Thanks!

I have been having a very strange issue in my project that occurs after resolving AR Core Cloud Anchors, where I am not entirely sure if this error is related to sceneview, but since I am unable to find the root cause of this error, I figured you might know something or have had a similar problem like this before.

So my app does not crash with any "normal" exceptions or stacktrace, but when navigating away from my AR fragment, the app will just close with the following error message that doesn't really help too much:

I/native: I0304 19:19:53.140083   16305 session_lite_c_api.cc:37] Deleting ArSession...
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6c00000018 in tid 25038 (Thread-20), pid 16305 (nn.arsamplecode)

While trying to find the cause, I could pinpoint it on callling session.resolveCloudAnchor() with an existing anchor ID. Turns out, while AR Core is still trying to resolve a cloud anchor and hasn't found it yet, it will crash when trying to navigate away from the fragment. As soon as the anchor is successfully resolved, navigating works perfectly fine again.

I created a small sample to hopefully reproduce the issue, though for that you will have to use your own Cloud Anchor API Key and an existing cloud anchor ID. In the sample, tapping on the AR plane will call the resolveCloudAnchor, and then simply navigating back will crash the app.

Since I really am out of approaches of how to fix this, I was hoping that maybe y'all have some experience with these kind of errors or potentially have an idea how I can solve this issue. Thanks alot in advance

I'm trying to get the sample model displayed in my Java code. I've got everything working in SceneForm but I'm trying to migrate to this project for the memory management improvements. What am I doing wrong here? (This is a native android component I'm bridging for use in React Native so this class is being rendered inside of a Fragment.)

Here is my code:

class RNTExerciseView extends FrameLayout {

    private SceneView sceneView;
    private ModelNode characterModel;
    private Node cameraOrbit;
    private Camera camera;

    private ObjectAnimator currentlyPlaying;

    public RNTExerciseView(@NonNull Context context, ReactContext reactContext, int reactNativeViewId) {
        super(context);

        sceneView = new SceneView(context);
        sceneView.setBackgroundColor(Color.rgb(255, 255, 255));
        sceneView.setTransparent(true);
        sceneView.setZOrderOnTop(false);
        this.addView(sceneView);

        characterModel = new ModelNode();
        sceneView.addChild(characterModel);
        characterModel.setWorldPosition(new Float3(0, 0, -5));

        characterModel.loadModelAsync(
            context,
            "https://sceneview.github.io/assets/models/MaterialSuite.glb",
            null,
            true,
            true,
            new Float3(0, 0, 0), 
            null, 
            instance -> {
                return null;
            });
    }
}

PlaneRenderMode.RENDER_ALL was set as the default mode but the doc states clearly that this mode is very expensive. A short check on the Profile verified this statement with 500ms spikes. The default mode is now set to PlaneRenderMode.RENDER_TOP_MOST.

hello, when using sceneview to display an object everything works great until you leave the activity and onDestroy gets called

i cloned the project and in sceneview.kt i commented this in the override destroy

override fun onDestroy(owner: LifecycleOwner) { super.onDestroy(owner) //renderer.destroyAllResources() //camera.destroy() //environment?.destroy() environment = null //mainLight?.destroy() mainLight = null }

after doing this everything works perfectly, if you could change this in the real git repository or find a better way to fix it that would be great, if you want me to push my version ill do that, i just dont want to accidentally break something

I tried following the sample-ar-model-viewer, except I want to only use the SceneView (3D only). However, I am unable to see the object, even when sceneViewer.addChild(modelNode) is called.

I guess I'm not supposed to use an ArModelNode but instead, ModelNode, but I can't seem to get this working. Is it possible to post a working example using just 3D?

lateinit var sceneView: SceneView
lateinit var modelNode: ArModelNode

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {

    modelNode = ArModelNode(placementMode = PlacementMode.BEST_AVAILABLE).apply {
            loadModel(
                context = requireContext(),
                coroutineScope = lifecycleScope,
                glbFileLocation = "models/spiderbot.glb",
                autoAnimate = true,
                onLoaded = { isLoading = false })
            onTrackingChanged = { _, isTracking, _ ->
                actionButton.isGone = !isTracking
            }
        }
        sceneView.addChild(modelNode)

Is there a way to detect the size (dimensions) of a loaded GLB file and calculate a scale factor so that the 3D model fits on the Android screen? Filament has a method called transformToUnitCube() which "tells the model viewer to transform the root node of the scene such that it fits into a 1x1x1 cube centered at the origin". Could we build something like that for SceneView?

private fun loadGlb(name: String) {
   val buffer = readAsset("models/${name}.glb")
   modelViewer.loadModelGlb(buffer)
   modelViewer.transformToUnitCube()
}

Source: https://medium.com/@philiprideout/getting-started-with-filament-on-android-d10b16f0ec67

I've restored plane rendering by returning back the calculation of the focus point. It is required since with the current material planes are only visible (not transparent) around the focus point.

Previously when using SceneForm, I'm able to have a white background behind all the models being rendered in the scene like this:

sceneView.setBackgroundColor(Color.rgb(255, 255, 255));
sceneView.setTransparent(true);
sceneView.setZOrderOnTop(true);

Now when I do this in SceneView, all I get is a blank white view.

This PR ads the same easy to use script for generating .filamat materials but for those of us that don't use Windows 😃

NOTEs:

• I'm not sure if we should keep the API to all. From what I've read in docs it seemed matc exported by default for OpenGL only and I think also exporting Vulkan should be helpful 🤔
• I also skipped —optimize-size since I wanted to not spare performance on my use case but let me know and I can add it back

(cherry picked from commit b7d34436a1578410b39ad46fa54d319798d4cee8)

I am trying to face problem for adding and removing stl files from a model. What I want to achieve is : Add Multiple STL models in a mesh can able to remove an STL model on selecting. please help to update the code and mention here What I want is referring to this app below: https://play.google.com/store/apps/details?id=com.performance.meshview

After getting LightNode to work, I've found that adding directional lights does not work.

If you add one directional light, it overrides the scene's mainLight as generated by lightEstimationMode= LightEstimationMode.AMBIENT_INTENSITY, if you add multiple only the last one added is used.

The simple test is to add multiple directional lights with different colours and see that only the one added last actually illuminates the scene and removes the default illumination.

Will SceneView support rendering GLB files containing KTX2 texture in the future? Or there is already a way to do so? I used one of your sample projects to do some testing (Ar Model Viewer) With KTX2 texture | Without KTX2 texture (PNG) :-------------------------:|:-------------------------: ) | With KTX2 texture | Without KTX2 texture (PNG) :-------------------------:|:-------------------------: |

I'm sharing few resource with you guys: KTX explanation by Khronos group : https://www.khronos.org/ktx/

ie , On background I need a camera view and my 3d model node will be on the screen (as a sticky one), even I changed the camera position the node will be there , camera view will only change..!

This one I have intergrated on sceneForm, but when I moved to sceneView , its not working

pls help.?

The onArFrameHitResult method is currently not called, even if the node is clicked by the user. This is really bad because many use cases include the selection of specific modelNodes for interacting with them.

It's pointed out that the bug is known but since there is no ticket (I can't find one) and this problem is the only one preventing me from migrating to this package, I thought a separate ticket is a good way to track the progress on this.

@grassydragon on discord:

If there is only one node, you can use a workaround from here: https://github.com/SceneView/sceneview-android/blob/main/samples/ar-model-viewer/src/main/java/io/github/sceneview/sample/armodelviewer/MainFragment.kt#L66 Otherwise, we need to fix picking a particular node.

What does the change do?

• Increase confidence needed to start pan gestures
• Allow users to deactivate pan gestures completely

The problem to solve here is that when the user tries to zoom it's sometimes mistaken for a pan gesture and triggers strafing in ORBIT mode. This moves the user away from the model he/she is looking at. Often the model is not visible at all anymore. Also when looking at a 3D model the option to strafe might be not needed at all and so it's possible to deactivate the gesture completely.

I copied the GestureDetector class from Filament to our code base as the Filament team threat it as sample code and is not accepting feature requests for it.