different composer entities with different behavior.

Question

airinterface OP

Created Feb ’24

Replies 2

Boosts 0

Participants 1

in Diorama project,

                let entity = try await Entity(named: "DioramaAssembled", in: RealityKitContent.RealityKitContentBundle)
                viewModel.rootEntity = entity
                content.add(entity)
                viewModel.updateScale()
                
                // Offset the scene so it doesn't appear underneath the user or conflict with the main window.
                entity.position = SIMD3<Float>(0, 0, -2)

Object doesn't move around with Camera - with the simulator workthrough wasd key I can work around the object.

But with different composer file, that I created

                   let entity = try await Entity(named: "ImmersiveScene", in: realityKitContentBundle) {
                   viewModel.rootEntity = entity
                   content.add(entity)
                   viewModel.updateScale()

with wasd key in the simulator, model moves with it.

What confirugation that I'm missing with ImmersiveScene Entity?

Boost

Answer 1

airinterface OP

Feb ’24

I figure out the root cause, but still struggle to understand why. Aside from this, I was running debugging

        Task.detached { @MainActor in
           

        Task {
            try await session.run([worldTracking])

            for await update in worldTracking.anchorUpdates {
                switch update.event {
                case .added, .updated:
                    print("Anchor position updated.")
                case .removed:
                    print("Anchor position now unknown.")
                }
            }
        }

if I stop this, I can move around. I thought above code is just printing out log, But is there any conflict? or any update that it does due to this?

0

Answer 2

airinterface OP

Feb ’24

Actually, it was same behavior within the Composer Pro. And object size needed to get scaled down to see it was actually sticking to the anchor.

0