I've been constantly arguing about this problem. It's not just me, it's a problem that all Quest Pro users around the world are experiencing.
The current Meta Quest Pro controller problems are as follows.
(1) Controller tracking problem
(2) a fever problem
First of all.
There is no problem with controller tracking at first like what I posted in the picture. Suddenly, tracking is misaligned. Of course, I have my own CPU and I understand because I have a unique feature. However, tracking is so severe that it is difficult to use, and even though I put both hands in the same position as shown in the picture, the controller does not recognize it properly, so it tracks in the wrong direction by itself.
Of course, this malfunction is causing extreme battery consumption, and if you use it as it is, the Quest Pro controller battery life will be extremely reduced. No, it won't last a year. Rather, it consumes more than the body.
I definitely charged 100% and used 1 hour and 10 minutes, and the controller is already at 80%. If you go this way, the probability of discharge is very high.
Second, the fever problem is very serious.
The phrase that the fever has occurred frequently appears and it is forcibly terminated after 5 minutes. The counselor calls this a safety phenomenon, but I would like to say that the problem is more serious because it is directly linked to the problem of use, not safety.
Warning appears frequently, and even if the power is turned off and turned off, it seems to be a problem due to the body temperature of the human palm, so I measured the temperature of the controller immediately after it occurred, and it is very normal at 26 degrees.
By any chance, has the condition of using the Quest Pro controller changed to the condition of using it in the Arctic, Antarctic, or US heavy snow?
I'm looking at this issue to the point of seriousness, and I've insisted on this issue countless times, and I've changed the product countless times because I thought it was a simple quest pro problem. And even though I copied and pasted the manual, such as turning it off and on as Meta claims, I've followed it. But it didn't work out in the end.
Even if I want to seriously discuss this with the developers, the developers are not giving me any response. So should I tell the Meta boss via Twitter that this problem has occurred and the developers are hiding it?
The developers should take this very seriously and know that from this V62 onwards, the problem will be very serious, and it should be improved as soon as possible. If you don't improve, the Meta Quest Pro 1 itself is a failure and a product you can't use.
