Same here. I dont understand the rational For this api to be so restricted. I will post something in the Feedback assistant as well

It seems that for now ImageTracking is unusable on visionOS except that using it to anchor definitely an object somewhere. You cannot follow the image in realtime. It is even worse when you try to track multiple images. My guess is that Apple devs were very conservative about global performance and maybe the NPU is busy analysing the scene. However, we kind of already have the same amount of workload in iOS with "smaller" chips, so I pray to have nice announcements at the WWDC 24

I had the same issue and thanks to @deeje reply, I figured out how to proceed, so here is the separate and combine part of the shader. Hope this will help !

Maybe a workaround for lack of CustomMaterial support: I saw that we can replace a TextureRource with a drawable queue. But I need an example of the shader interface as the RealityKit::surface do not exists anymore on visionOs. Maybe an Apple engineer have a sample somewhere ?

Same problem for me. I saw this message in th console, maybe related: "invalidated after getting a no-senders notification - client is gone"

Not working for me unfortunately.