Recent Discussions
Adding Meta Quest 3
So i had to reset my Meta Quest 3 and delete the registration. Now i will add the Quest 3 in my user account but i cant. I need the rma Code or any bill. How is possible without? I connect the quest3 with meta horizon successfully. thanks for helping. The quest3 is now 3 years old and out of support.
Actualizacion v.83 desastre total
Hola a todos desde que se ha actualizado a la versión v.83 mis meta quest 3 me es imposible jugar en pcvr porque se congela la.imagen .Al iniciar el visor me sale un mensaje en la parte superior como que algo está mal que lo intente más tarde. Cada actualización que lanza meta inutiliza más y más un visor nada barato y no hay un soporte técnico que esté ahí para los usuarios os estáis coronando meta estoy muy decepcionado espero que arreglen todos los fallos que están provocando y que sufrimos los usuarios. Al.final tendré que deshacerme de estas gafas
Unity builds crash on startup since ~Jan. 19
Hello, I thought this would have been fixed by now but since one of the latest updates, our Unity builds are crashing on startup (builds that did not have this issue last week). It's a desktop/VR app and the desktop part starts up no issues ; but, as soon as we start the app with HMD mounted, it crashes whenever VR is "started" (the loading screen has no problem but it crashes once VR components are enabled). Builds use Unity 2019.4.41f2 Software uses legacy VR plugins with VRTK store asset Crash logs and dumps for unity editor are both mentioning "libovravatar" which is why I'm suspecting meta Crash dmp has this in it : FILE_IN_CAB: crash.dmp CONTEXT: (.ecxr) rax=0000018a525d8dbc rbx=0000018a525d8dbc rcx=0000018a525d8dbc [...] libovravatar!ovrAvatarSpecification_GetAvatarSpecificationUri+0x73b63: 00007ffc`dac6ea33 4c03e0 add r12,rax Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffd76700a15 (VCRUNTIME140!memcpy_avx_ermsb_amd+0x00000000000000d5) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000018cdf4de98a Attempt to read from address 0000018cdf4de98a We can't test our product at all. Help please !
Link Cable Discussion - Meta Quest Link Official Cable vs Offbrand Cable
I’m starting this discussion because I’ve seen multiple people trying to get the same performance from an off-brand cable that does not provide fibre optic connectivity versus the Meta Quest official link cable that does. There is a absolute reason as to why the Official cable is worth more than a video game right now. I guarantee if you use the meta quest 3 ( I do right now), you will benefit from the official cable more than the off brand. The official cable also uses USB-C to USB-C and not USB to USB-C which indicates better bitrate capabilities. I do have a beefy computer so results may vary based on your individual computer specs but my computer utilized the official cable much better. (7900xtx graphics card) Try out the official cable if you think that your experience is limited because you didn’t buy the actual cable meta recommends. Meta does not provide a USB to USB-C official cable and you can wonder why now. Hope this post helps anyone that has enough money to upgrade and wants better performance in the VR world.
Quest 2 Link (cable) Easily Disconnecting
I realize this sounds like a cable issue but I tested with multiple cables and the same thing happens. Things were working fine until the last update (the update that fixed the last update). Meta Link does boot up, but it then*very easily* crashes (disconnects). Yea I realize it could still be a hardware issue but I'm hoping not, i can't afford a new one. Is anyone else noticing this?meta horizon link still not working
just tried to link headset with internet connected now get a static crackle through the headset and still no conection to meta horizon what ever you did in your last updates has slowed conection speed of vr headset in game ie from desktop to VR it used to be istant now it takes approx 15 seconds who ever is doing the updates is making things worse
Unity debugging VR applications fails to start.
I'm a Quest3 application developer on Unity. I'm developing my application using Unity. I streamed my Quest to the computer using Meta Horizon Link + streaming cable, and then clicked "Run with Unity" to start my project. At this point, Quest didn't succeed, but I could still see the Unity editor. Theoretically, it should have entered my VR application, but it seems that it didn't start successfully. However, when I unchecked the Meta XR Feature in open xr setting, Unity Editor run this application normally, but all the Meta XR functions were lost. The screen moves along with my head (head tracking fails), and it cannot detect any controllers or gestures. The software version of my Quest 3 is v0.83. The version of Meta Horizo n Link is 0.83/0.85 (both versions have been tested and the phenomenon is the same), and the version of Meta XR SDK has also been tested (0.83, 0.77, 0.76, 0.74). What caused this? I used the official sample scenario. I repeatedly checked all the configurations of Unity and everything was normal. Moreover, when I packaged and built it to run on the all-in-one machine, it also ran normally I was running the simplest scenario with only a camera. I also tried the sample scenario provided by the Meta XR SDK, and the phenomenon was the sameMy Left Controller won’t work the battery case won’t come out. What do I do?
After having a failing discussion with the meta support ai I’ve turned to the community. My left controller is charged 100% and won’t work with my meta quest three and neither of the controllers batteries will slide out after I’ve watched countless videos about it. I’m not sure what to do with my left controller as I’ve had it for only a year and the right one works fine. This randomly happened and I keep amazing care of it.
