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.App Lab "Preview App" Download location
I am needing to share preview builds of an App Lab app via Oculus' preview app feature. I have added another user via Release Channels -> Builds -> Add Users. My users have accepted the invitation and can see the app in the preview apps section of their Account settings on the web browser Oculus.com site. We cannot see the app in the preview apps section on the Mobile App nor can we see the app in the headset. Is there a new location where these preview apps reside?
Attaching Local Avatar to Player Controller in Unity
I have a problem attaching the avatar prefab for touch controls to the player controller prefab from oculus SDK. I have tried making both prefabs as children of an empty parent object. I tried to make the local avatar a child of player controller and it works fine until I move and my hands stay in the same spot while the body moves. I tried looking for a solution and cannot find one. Is there another way of doing this? Thank you.Oculus Touch quick start guide - plus free skinned hand models
Hey, so you just got Touch? Fantastic. I thought I'd make a quick list of points to help you get going with Unity integration. This might be obvious stuff to others but I thought with the number of additional devs receiving Touch kits and Oculus continuing to hand them out this might benefit some. And Cyber [or anyone else], please correct me if I'm wrong about the following stuff: 1.First up, grab the latest Oculus Unity Utilities and Touch integration. This stuff is still evolving so to avoid errors and snags, make sure you're up to date. See the ReadMe file in the OvrTouch folder for these points and more info. 2.In your project, once the Touch sample package is imported, bring in the Touch prefabs and connect up the right and left hand anchors. You can find the prefabs in the OvrTouch/Content/Hands/ folder. Select the prefabs one at a time and drag the appropriate HandAnchor transform to the Touch Anchor field on the prefab. 3. To prevent odd movement glitches and update issues, it's recommended that you parent the hand prefabs into the PlayerController hierarchy, preferably under the camera coordinate space. Under the TrackingSpace node seems to work well for me. 4. Set: Edit->Project Settings->Time->Fixed Timestep = 0.01111111 to reduce judder and hand tracking latency. 5. Don't forget to try the sample scenes in the OvrTouch/Content folder. OvrTouchDemo and TapeMeasure in particular for a taste of the haptics capability. 6. Now to the fun stuff. I think Oculus prefer that we not use the blue sample hands in projects we distribute or show to others. I skinned up a pair of replacement hands you're welcome to use if you like. They're a bit higher resolution than the samples [and let's face it they're a pair of white male hands which may not suit you or your project!] but you can at least get going with them if you want to move away from the blue ones. They look like this: Get them from my dropbox here: https://www.dropbox.com/s/v71kr0p5ooaxvhz/HumanHands.zip?dl=0 In the zip file you should find the following items: r_hand_skeletal.fbx <-- replace the identical item in your OvrTouch/Content/Hands/Models/ folder with this l_hand_skeletal.fbx <-- replace the identical item in your OvrTouch/Content/Hands/Models/ folder with this humanHand_3D_COLOR.jpg <-- put this wherever you prefer to keep textures humanHand_3D_NRM.jpg <-- put this wherever you prefer to keep textures humanHandSkin.mat <-- put this wherever you prefer to keep materials These hands come from a blender model created by SuperDasil: http://www.blendswap.com/blends/view/81285 licensed under the Creative Commons. I have remodeled them a bit to match the Oculus touch sample joint proportions and capped the ends to be a little more pleasing to the eye. Should updated Oculus Touch samples come along with significant changes I can update these to match. 7. Finally you'll want to grab things in your own project huh. Items you wish to interact with need to be rigidBody physics objects which means you'll want to setup the usual components required for that. This may also mean you need to set up colliders etc so your objects don't fall through the floor when you put them down [or throw them for fun]. Simply add the supplied Grabbable.cs script [OvrTouch/Script/Hands/] to your object and you should be good to go. That should get you up and running. If anyone else has useful info to share please do, the more the merrier. -julian
Using Oculus Quest controller for clicking on Buttons
Hi folks, I'm currently building a prototype for a project (using unity 2019.4.0f1). That means it doesn't have to be perfect and there are just a few functions involved. So far I created the environment and added a dialogue system, which pops up when the button is hit. This is working absolutely fine when I'm in Unity and try it on play mode. But when I try it out on my Oculus Quest, everything is shown correctly but I'm not able to click the button (as I did in play mode with the mouse). I'm using the custom hands and are able to grab things - but it seems I'm too stupid to click buttons. My brain tells me that there is a simple solution, but right now I'm more than desperate. I hope there's someone out there, who can help me. Btw I'm a newbie and try my best - be kind. Thank you in advance! I don't know if it helps but here are my Hierarchy... The button in the inspector ...and the button in gameWhy 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)? MetaStoreHelp
Customers 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.
