Closed eusebiu closed 2 years ago
Thanks for reporting this! Do you have any other VR device to repro with?
I noticed this happens on MRTK2 also if I leave it running for some time with the debugger attached and then I try to reattach. When this happens, it breaks down. Edition Windows 10 Enterprise Version 20H2 Installed on 25-May-22 OS build 19042.1826 Experience Windows Feature Experience Pack 120.2212.4180.0 NVIDIA Quadro RTX 5000 with Max-Q Design 16GB.
I have a feeling this started to happen after this Windows Update (as I did not do any VR lately).
I noticed that when this started to happen, I get this message in the Console: Physics.ClosestPoint can only be used with a BoxCollider, SphereCollider, CapsuleCollider and a convex MeshCollider. UnityEngine.Collider:ClosestPoint (UnityEngine.Vector3) Microsoft.MixedReality.Toolkit.Input.ReticleMagnetism:Update () (at Library/PackageCache/com.microsoft.mrtk.input@cae224c3445a/Interactors/InteractorVisuals/ReticleMagnetism.cs:152)
I am not using ReticleMagnetism at all... or I am not aware of using it...
Thanks for reporting this! Do you have any other VR device to repro with?
Only Oculus.
I think it is related to Oculus runtime... Their log is full of Frame dropped due to encoder backup...
This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:
Describe the bug
After attaching the VS debugger on a MRTK3 project, the VR system slows down considerably. The only way to get back is to reboot the computer.
To reproduce
Steps to reproduce the behavior:
Expected behavior
VR is not stuttering.
Your setup
Target platform