05-07-2018 08:54 AM
05-09-2018 11:10 PM
05-10-2018 07:23 AM
imperativity said:
Hi,
I checked with our integrations team and was provided with the following guidance to share with you regarding this issue:
"That is a fine solution.
If it does cause performance issues, you can also reduce the Default Solver
Iterations and Default Solver Velocity Iterations to make each physics fixed
update cheaper. Another solution is to set the fixed update size to 22.222ms
(45Hz) or 33.333ms (30Hz) so there is a consistent number of rendered frames
between each fixed update. If you do this, be sure to set OVRCameraRig.useFixedUpdateForTracking
= true to make Touch tracking synchronize with physics instead of rendering."