MRTK looks for a GameObject named "AR Session", and then looks for the ARSession component on that node. If it doesn't find the node by name, or doesn't find the component on it, it creates a new ARSession component and adds it to the scene.
This change allows MRTK to find the extant ARSession component so it won't create a redundant one. This can have very large performance ramifications, seen on Android Galaxy.
MRTK looks for a GameObject named "AR Session", and then looks for the ARSession component on that node. If it doesn't find the node by name, or doesn't find the component on it, it creates a new ARSession component and adds it to the scene.
This change allows MRTK to find the extant ARSession component so it won't create a redundant one. This can have very large performance ramifications, seen on Android Galaxy.