AR Foundation Scale of ARSessionOrigin Challenges and Best Practice

I have found that having ARSessionOrigin scale of 10 to compensate for object size of 1m tends to effect the plane, anchor, point cloud, stability and error (esp on Android) so needs to be reduced to ARSessionOrigin of 1.

I have noticed that with AR Foundation ARSessionOrigin scale of 1 that objects have to be reduced in size by 10 to be useful (1m objects need to become 0.1m objects). This has challenges as I have built my AR at ARSessionOrigin scale of 10. E.g. gravity, physics, particles at this smaller scale.

All my objects have to be to be re-scaled down by 10 so I am interested in discovering:

• Why does AR Foundation does not use a scale of 1m to ARSessionOrgin of 1. Why 0.1m
• Guidelines for scaling down objects.
  
• Local gravity for smaller rigid bodies.
• How to scale particles down without loosing anything.
• How to scale force, impulse and explosions down without loosing anything.

 

Here you are. And one more.

 

Does this also apply in situations where objects are placed on a LiDAR meshed environment?

For example, i have objects placed in the meshed environment and i want to scale 1 objects while keeping the rest intact.

 

@KirillKuzyk has experience with LiDAR when Meshing in his Unity Asset.