Can I connect my Quest 3 controllers to my Quest 2?
I have Quest Pro Controllers that I have been using on my Quest 2 (Great!!) I purchased a Quest 3 and will be moving the Quest Pro Controllers to it. I would like/prefer to pair my Quest 3 Controllers to my Quest 2 Headset. Currently this is not an option to select in the App. Are there any plans to allow Quest 3 Controllers to work on a Quest 2 (similar to how the Pro Controllers work on Q2)? What would be the reason to not allow/support it? Thank You! MrTasselhof YouTube (MrTasselhof) Twitch (MrTasselhof)
The Windows SDK version 10.0.10586.0 was not found
I was following the PC SDK getting started guide, and progressed relatively smoothly until I tried to run the demos in the samples file Samples/Projects/Windows/VS2015/Samples.sln in Visual studio 2015. I encountered the error "The windows sdk version 10.0.10586.0 was not found." I followed the steps to correct it in the guide as well: I followed the instructions: edit Project Properties → General → Target Platform Version and changed the version to 10.0.15063.0, which was the windows 10 SDK on my computer. However, with this, the same exact error remained, "The windows sdk version 10.0.10586.0 was not found." So I went even farther, going into the Windows10SDKPaths.props file, and changed all 6 instances of 10.0.10586 to 10.0.15063. However, the same exact error popped up once again. I've tried closing Visual studio and restarting my laptop between steps, however, the result is still the same. Can you please advise on how to fix this? Thanks in advance.
Linux Support???
I'm really disappointed that I wasted $400 on a Rift S just for it to become a paper-weight since I don't want to use Windows on my computer. I have no clue why a multi-billion dollar company can't afford to support more than one operating system. I'm by no means expecting perfect support with no performance issues or hiccups on the less popular OS's, but having the headset be COMPLETELY UNUSABLE is not at all excusable. Just let me use the headset, and I'll do the optimizing myself. It's pretty embarrassing that Valve, a company valued at $8 billion, can comfortably support Linux and Windows almost flawlessly on their headsets, but Oculus, which is owned by Meta, a company valued at $572 billion can only support Windows. I understand the tone may seem harsh, but as someone who spent $400 dollars on the thing, I should have the right to use it on whatever computer I see fit even with less than desirable performance.
Why is Oculus Developer Support so bad?
This isn't supposed to be a rant thread, but I am genuinely surprised about how bad the experience has been for us so far developing for the oculus platform in terms of available resources and support. On the end-user side, oculus/Meta seems to do a really good job in providing resources and quick support, but it seems to be quite the contrary on the developer side and it just puzzles me why this is the case. There are hardly any answers from oculus engineers on this forum, support tickets take forever and don't yield any actual help and SDK documentation is often seriously lacking. Given that Meta is so dedicated in pushing the Metaverse, I'm genuinely surprised about the way they treat developers that dedicate their time and resources building experiences for their platform, and thus I wonder whether they maybe internally have the stance that developing polished VR experiences is something rather difficult that they don't expect independent developers to come up with and thus focus their resources on providing direct support channels to the big studios instead? I'd be interested to hear about the experience of other devs on here and also what place you go to when you have problems or questions (because the official developer forum doesn't seem to yield any results for any non-trivial questions/problems)? MetaStoreHelpCustomers cannot "GET" our app (App Lab)
From what I can understand, a Quest App is available by the app id link before being reviewed. This allows users to install the app from a direct URL rather than the AppStore. Our app is viewable on PC by the App Id link, and everything looks fine, except there is no GET button. Also, when the same URL is viewed on the Quest, a 404 error is displayed. Is the App Lab broken, or am I missing a setting somewhere? Now that the App is in a review state, there are no settings available to us for change. Strangely, the URL is viewable on PC but not the Quest. We want our app to be available to our users, precisely many schools anxiously waiting to use our app. Our previous app worked with Google Cardboard, and now the schools are migrating to the Quest. We are unable to give them our app because of this issue. We need to have our app used by students before the school year is complete. By not having this app available to students, this delay is robbing children of an educational experience that could shape their future with a career in technology.
Cannot Create a Meta for Developers account
I opened a case, 6774076, with Meta support and they directed me to these forums and closed the ticket. Although, the case is not resolved. On page https://developers.facebook.com/async/registration/dialog/ , Contact info, Error: "Email cannot be sent. Please try later" This has been an issue for approximately 4 days now, and I do not know what to do.
