Thanks for the response! I figure that myself. It turns that the I would request .current version of PHAsset in PHImageRequestOptions. I use .original before, but I guess the converted spatial photo should be using .current because the original photo is a .jpeg, which cannot be spatial photo wrapper format (heic did).

Another possible aspect about this issue is that I use PHCachingImageManager()/PHImageManager.default() to retrieve/request this photo. And this photo was previously a 2D photo. Is it possible that this manager caches this photo somewhere (OS level) and I may not yet request the correct converted 3D asset? If so, how to force refreshing the cache then?

Hi thanks for the response, this is the link, this is the one I airdrop (with all options toggled) to my mac. And I can see it shows "spatial" on my iPhone 15 https://drive.google.com/file/d/1ggzejg-mszCM_dpxANU5U80chlcLqATb/view?usp=drive_link

hiiiii I am using your method to findout leftindex and rightindex here. But this function failed at Check for any groups. It's working for native Spatial Photos, but not for generated photos. The only difference between me and kevin_wang is, hes using imagePicker to fetch imageItem but me using PHImageManager.default().requestImageDataAndOrientation to request imageSource. Would that make any difference?

Thanks! So for UbiquitousKVStore, theoretically if I called synchronize() every time I shouldn't worry about CloudKV data right? What about custom container, CloudKit - CoreData, do I need to manually synchronize it? Say context.save() would sync to the cloud immediately rather than iCloudKV's "lazy strategy" right?

Thanks for your response! It's definitely working. I thought I should set "FileName" as String parameter in that case. Also I got another question, from code level, why it has to be a ModelComponent to access materials? I mean as an Entity it's not necessary to be collidable or to be a rigidbody right? Or there were other stuff I am missing?

done, please check FB16308928

Thanks for the reply! I actually figure out what happens here. As the debugger said: 'Presentations are not permitted within volumetric window scenes.' When I ask for PH permissions, I also open an immersiveSpace, therefore I have two scenes both open. I know that volumetric view won't display system pop out sheet (simply it cannot), and nor does an immersiveSpace. Volumetric window scenes also includes ImmersiveSpace for sure.

I believe that when two scenes open, visionOS randomly (or some mechanism in black box) picks a "main view" as a "window carrier" to pop out PH picker. I just don't know how to set the .plain Window as main scene when two scenes open. So I choose to openImmersiveSpace after permission granted, problem solved. But still, can you elaborates more on the mechanism here? About how visionOS system selects the carrier.

I feel like it's more of the issue of AnimationLibraryComponent, I switch the onNotification to onTap trigger on BehaviorComponent, it behaves just like onNotification trigger, not working. Then I found that there is actually missing AnimationLibrary component on my target entity (the one with BehaviorComponent, let's call it entityA). I found that when I add AnimationLibraryComponent on it, the timeline animations in the scene don't add themselves into the AnimationLibraryComponent.

Wonder if Behavior Component isn't completely configured, then why the notification action inside the timeline can be fired?

Thanks! Gonna get back to you if I have any luck.

The weird thing is, when the ball moves towards the block(wall) directly with linearVelocity's direction almost equaling to the wall's normal's direction. The ball then stopped immediately like it sticks to the wall. Seems like the momentum has completely transferred to the wall. (But I locked the movement of the wall so the wall won't move)

I tried to replace Qiu with code-generated ModelEntity, I would say...its probably work? As the simulation result is quite confusing. All I need to do is to let the invisible block not "consume" any of the momentum there. All the speed damping process should only be determined by Qiu's property.

this behaves like a small ball "tries to" transfer its impulse onto the block lol