Thanks for the answer. I forgot to mention one important detail. I discovered that targetedToAnyEntity() doesnt work in my case because I'm creating an instance of the PerspectiveCamera func createCamera() -> Entity { let camera = PerspectiveCamera() camera.name = "Camera" camera.look(at: [160, 80, 1], from: [160, 80, 200], relativeTo: nil) return camera } and in this case RealityKit disables automatic input routing, because now I'm responsible for defining how the world is rendered and interacted with. RealityView { content in content.add(createCamera()) However I need that camera :( Automatic input routing also stops to work if entity is to far from the default camera :(

Thanks for the clarifications.

Thanks, that's correct, but you never know when it might be "hard deprecated". I've been working on a game for two years now as a solo developer, and I think it'll take at least one or two more years for me to finish. Switching to RealityKit would mean almost a complete rewrite for me, so I'm unsure whether I should proceed with rewriting the game in RealityKit—or maybe it would be better to switch to Unity instead.

Is it still worth to develop a game in SceneKit? SceneKit is deprecated now.

I think that I found the issue. It was related to the cameraNode.camera!.zNear, which by default is set to 1.0. I changed it to cameraNode.camera!.zNear = 0.01 and it seems to work much better.