Hey, do you find that this problem is unchanged if you test your Quest in an entirely different play area? If so, you may need to try performing a factory reset on your Quest to resolve the issue. Should that not work, please click here to submit a ticket so that we can look into further options. Thanks! -Kassidy
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!