Regarding restitution Even in the last video here: https://stepinto.vision/example-code/collisions-physics-physics-material/ bounce of the ball is very unnatural - stops after 3-4 bounces. That is because I never set the restitution to a max value. The wood base in that example has a restitution of 1, but the highest value I used on the ball was 0.7. Energy Loss: Despite restitution = 1.0 (perfect elasticity), the ball loses ~20-30% energy per bounce You could set the restitution to 1.0 on both the balls AND the surface(s) they are bouncing on. This won't necessarily be realistic. The balls will essentially bounce infinitely. You'll have to slightly adjust the restitution on one or both of the entity types to make them feel a bit more natural. Of course, a lot will also depend on your mass and friction values.

Boosting this one. Hopefully an Apple engineer can tell us if there is a workaround. I've run into this too. In seems like visionOS places the keyboard relative to the host scene (a volume in my case) instead of near the attachment hosting the TextField.

Just jumping in to confirm the issue that @eurobob reported. @Vision Pro Engineer suggested adding a minimalDistance, which works for me. There is something else that could be causing issues. As we know, an Entity can only have one instance of a component type assigned at a time. Add a GestureComponent with Gesture B will overwrite a GestureComponent with Gesture A. I don't see a clear way to add more than one Gesture to a GestureComponent. The docs for this one are essentially, so no help there. Is it possible to use this component with more than one gesture? struct Lab: View { var body: some View { RealityView { content in // Load an entity and set it up for input let subject = ModelEntity( mesh: .generateBox(size: 0.2, cornerRadius: 0.01), materials: [SimpleMaterial(color: .stepGreen, isMetallic: false)] ) subject.name = "Subject" subject.components.set(InputTargetComponent()) subject.components.set(HoverEffectComponent()) subject.components .set(CollisionComponent(shapes: [.generateBox(width: 0.2, height: 0.2, depth: 0.2)], isStatic: false)) // This works as long as this is the only gesture we use let gesture = DragGesture(minimumDistance: 0.001) .onChanged({ [weak subject] _ in print("Drag Gesture onChanged for \(subject!.name)") }) .onEnded({ [weak subject] _ in print("Drag Gesture onEnd for \(subject!.name)") }) let gestureComponent = GestureComponent(gesture) subject.components.set(gestureComponent) let tapGesture = TapGesture() .onEnded({ [weak subject] _ in print("Tap Gesture Works for \(String(describing: subject))") }) let gestureComponent2 = GestureComponent(tapGesture) subject.components.set(gestureComponent2) content.add(subject) } } } If I comment out the second gesture component, then the drag gesture works correctly

Have you tried using EnvironmentLightingConfigurationComponent? https://developer.apple.com/documentation/realitykit/environmentlightingconfigurationcomponent Apple talked using this with portal crossing at WWDC 2024 https://developer.apple.com/videos/play/wwdc2024/10103?time=1473

Hey, I saw you comment on Step Into Vision too. I'm showing the presentation as a result of a tap gesture in my app. I'm not sure if just setting presentation.isPresented = true here is enough. You are essentially telling something to present before the component has been added. I have no idea if that should work. If you look again at the code from my devlog, I use the GestureComponent to call isPresented based on a user tap. I'm also using this in a volume. You're working in an immersive space. When I tried your code, I saw this error in the Xcode console. "Presentations are not currently supported in Immersive contexts." I thought these were supported, but maybe something has change in Beta 3.

We can use scrollInputBehavior with the .look option From WWDC Session What’s new in visionOS var body: some View { ScrollView { HikeDetails() } .scrollInputBehavior(.enabled, for: .look) }

We can load a Three JS scene in a WebView, but the WebView itself will always be a 2D plane. It would work more like a window looking into the 3D space. The Three JS scene can't fill the volume. The only workaround I know is to download a model as a USDZ. If you needed to let your users place models in their shared space, this could be an option. Three JS as features to export as USDZ. But this exported file would not be a live Three JS scene anymore, just a USDZ file that users could open with QuickLook

@DTS Engineer Can you please be specific? I don't see the answer to my question in either of those articles. How do tell visionOS not to apply a tint color to the background or content of my view? The WWDC session mentions opting out of this when displaying photos, but I don't see how to do that. How do I tell visionOS: "always render this image as it appears without ever trying to tint it."?

I tried this just after WWDC and it works reasonably well. There is a Safari Flag to enable this for Then, look for the option in the menu to the left of the URL – Joseph

I can't reproduce this on my end. I just tried a few of my projects and examples and they are working fine. If I add a print line to the make closure of RealityView, I only see it print once. When I inspect the entity graph I see what I expect to see. I'm using visionOS 26 Beta 5 and the latest Xcode. Some other things to think about. You can use a feature in Xcode to capture the entity hierarchy. When you do this, do you see duplicate entities in the same hierarchy or duplicate hierarchies? https://www.gabrieluribe.me/blog/debugging-realitykit-apps-games-visionos Is there anything higher up in your SwiftUI stack that could be causing your RealityView to be created more than once? If you can post some example code showing the issue I may be able to provide more useful help

I ran into something like this in Beta 1 back in June. At first I thought it was something related to RealityKitContent as that is where Xcode seemed to be stuck. It ended up not having anything to do with RealityKit. One of my example code files demonstrated how to use every ornament anchor. This worked well on previous versions, but Xcode 26 could not compile it. Can you look at your SwiftUI code and see if there is anything with lots of ornaments, toolbars, that sort of thing? You may want to start commenting out sections of the view hierarchy and see if you can get it to build. Once it builds, start re-activating views until you can cause the issue again. That may help you find the view that Xcode is getting stuck on.

I made a standalone project based on your code check this out. The good news that the entity is not being duplicated. Let's look at the cod first. struct ImmersiveView: View { @State var launchEntity = Entity() var body: some View { RealityView { content in print("RealityView Content Loaded!") // Called Once launchEntity = createLaunchEntity() content.add(launchEntity) } } func createLaunchEntity() -> Entity { //... let entity: Entity = Entity() entity.name = "Launch Entity" let launchviewComponent = ViewAttachmentComponent( rootView: LaunchView() ) entity.components.set(launchviewComponent) print("createLaunchEntity was called") // Called Once return entity } } struct LaunchView: View { var body: some View { VStack { Text("Launch View") } .padding() .onAppear() { print("Launch view appears!") // Called Twice } } } When I load this immersive space I see 4 lines in the console RealityView Content Loaded! createLaunchEntity was called Launch view appears! Launch view appears! What happened RealityView content was called once createLaunchEntity The onAppear closure in the LaunchView was called twice. That made me wonder if ViewAttachmentComponent is calling LaunchView more than once and yes, that appears to be the case. When I create the attachment using the attachments closure on RealityView, onAppear is only called once. var body: some View { RealityView { content, attachments in print("RealityView Content Loaded!") // Called Once content.add(launchEntity) if let attachment = attachments.entity(for: "Test") { launchEntity = attachment content.add(launchEntity) } } update: { content, attachments in } attachments: { Attachment(id: "Test", { LaunchView() }) } } So the good news is that we don't see duplicate entities in the graph. The bad news is that ViewAttachmentComponent is calling the SwiftUI more than once. I suggest you file a bug with Feedback Assistant. In the meantime, you could using RealityView to create attachments. If your view is just presenting data, then I suppose you could just ignore this.

There is a hidden element we can "look at" with the mouse cursor. Place you mouse somewhere in this area This will show a tiny little button you can tap. It can be hard to see, but it is there. Tapping that will open control center. It sometimes takes a few seconds to load.

I think that is just the app reordering mode. It doesn't apply to environments today, but maybe they plan to let users rearrange our environments like we can with app on the first tab.

@Vision Pro Engineer Thanks, Feedback filed FB19948223