)
In there the guy for IOS just instantiates a ARSession and ARSessionOrigin and by adding a ARRaycastManager (update i added from the comments since he used an older arfoundation), his code works.
Most ARFoundation videos and tuts mention that an ARPlaneManager should be attached to ARSessionOrigin in order to create the planes (this is also mandatory its seems for using ARFoundation on Android).
How does IOS ARFoundation work without it in this example?
What is even more strange is that as soon as i add a ARPlaneManager to ARSessionOrigin the example does not work right anymore for IOS. The Placement indicator gets stuck always at the height of the last plane and does not work right. Even if i provide a plane prefab.
Do we have to make something special when adding the ARPlaneManager component? Is it needed for IOS? Does it work on IOS?
I wonder why none has stumbled upon this? Maybe because i work on a tight space and ARKit picks up something.
Anyway i got it working on IOS with ARPlaneManager replacing the TrackableType from TrackableType.Planes to TrackableType.PlaneWithinPolygon when i do a raycast
raycastManager.Raycast(screenCenter, hits, TrackableType.Planes)
vs
raycastManager.Raycast(screenCenter, hits, TrackableType.PlaneWithinPolygon)
So what doesARFoundation default to on IOS when no PlaneManager is used? I still don’t understand why recasting has a different behaviour on iOS when there is a ARPlaneManager is present or not.
