DeoVR busted again with new update
I for the longest time thought that DeoVR was to blame, but since the firmware update a few days ago, I realize it's been the Quest firmware updates hysterically tinkering with head tracking the whole time. I'm on Quest 3, but i had the same issue on Quest 2 - suddenly and without warning, the 6ofD head tracking and dome scaling just becomes "wrong" out of nowhere. E.G., tracking your head forwards or backwards will zoom appropriately, but every other dimension will translate WAY too much as a result, making the video you're watching hypersensitive to tiny little micro motions you don't even realize you're making with your head, rendering almost anything with video or passthrough completely useless. Previous firmware it was calibrated better, it almost seems like it goes normal>bad>normal>bad, with each update. You're basically having to choose between things looking wrong in one way, or looking wrong in a different way. From update to update, It's never consistently wrong, and it's not the app. I keep several versions of the app on hand to jump between whenever this happens, even though it usually doesn't fix anything. It makes more sense now that I know it's not DeoVR, because sometimes I'd be on the same exact version and turn the headset on and just feel like everything suddenly looked horrible where it didn't just hours prior. The color grading gets weird, the passthrough feed and the video clash colors forcing me to turn up night mode so everything is an analogous orange, but which totally defeats the purpose of having color passthrough at all. I guess my question is, why are we messing with the head tracking and color grading at all, when clearly we know that we know what looks good and what doesn't since every alternating update gets it right? It's almost like I'm being pranked, or like I'm being manipulated into engaging here on the forums, or being baited into getting upset and doing unwitting advertising by complaining online, or something. Why is the meta for our updates snip snapping between the normal product I paid for and an insane clown world version with no explanation? This most recent update the tracking is so bad I get motion sickness just IN THE MENU without even opening an app or game at all. How much the passthrough feed moves relative to the very slightly translating HUD menu I'm trying to read makes me feel like I need to immediately rip the headset off and find a bowl to puke in, and I've almost never gotten motion sickness in my entire life. Anyway, really hope we can fix it, thanks for your time.
App Lab, VRC.Quest.Functional.5, The app appears to only support 3DOF, Using OVRCameraRig
Hi, So I have had my app fail to publish to App Lab with the error: 'The app appears to only support 3DOF. Apps on the Quest platform must support 6DOF and respond to the HMD's positional tracking as well as orientation.' error: VRC.Quest.Functional.5 Firstly the I have uploaded 3 apps to App Lab using exactly the same build from Unity just changing the cube map renders, all other uploads have been fine. I am running Unity 2019.4.13f1, using the OVRCameraRig as I need to use per eye skyboxes for my stereoscopic renders, (I have tried using the new XR camera but I need to use per eye unique skyboxes). Everything functions great within the app, I only need 3DOF, and I presume my app is 6DOF with developing for quest, just un-noticeable due to being a camera viewing skyboxes and only physical 3D geometry clickable buttons? NOTE: If I turn on Position tracking in the camera the app feels rubbish, with buttons moving slightly. Is there another setting I have missed? Is this a recent test that other apps have passed before? Or is this just a random test fail and I need to just re-submit with a note saying I only need 3DOF for the client? I have had apps fail before due to icon pixel size and had to add a note saying it is exactly what is required then it gets passed!! Please could anyone give some guidance.Character Camera Constraint not working properly
In Unity for as long as I can remember there has always required a "Character Camera Constraint" component attached to the "OVRPlayerController" game object in order to keep the OVRPlayerController game object following the player camera utilizing the 6dof of the Oculus Quest . Ever since Oculus Intigration 12.0 was released It seems like they have changed how the Character Camera Constraint component works as it now required several other components to function without throwing any errors. Even with all of these components (Capsule Collider, Rigidbody, Simple Capsule with Stick Movement) the OVRPlayerController only rotates with the player camera, the position never changes. Does anyone know how to fix this problem/ how to get this to work, or does Oculus have to patch it?
Quest: Does Unity support surface shader tessellation for Android / OpenGL ES
I'd asked this on the Unity3D reddit, but haven't got a clear answer wrt the Quest. I'm not a coder at all (a filmmaker) using Unity and creating stereoscopic VR video, and now looking at depthmap driven - for pseudo 6dof- video on the Quest. I've not been able to get a definite answer on if Unity supports surface tessellation shaders on android/Quest. The reason I ask is, because I'd like to convert the below shader (taken from github) which works perfectly on the Quest, to a tessellation based shader so in theory (in my thinking) I can use a lower triangle count sphere and still get smoother displacement. Currently I'm using a 1million triangle sphere with video mapped on it (top half 2d, bottom half grayscale depth map) for doing simulated 6dof vr video. Any help and insights, I'll be very grateful. Kind Regards. Shader "PointCloud/Displacer/Spherical_OU"{ Properties{ _MainTex ("Texture", 2D) = "black" {} _Displacement ("Displacement", float) = 0.1 _Maximum("Maximum", float) = 99.0 _BaselineLength("Baseline Length", float) = 0.5 _SphericalAngle("Spherical Angle", float) = 10.0 _FocalLength("Focal Length", float) = 90.0 } SubShader{ Tags { "RenderType"="Opaque" } Cull Back Lighting Off LOD 300 CGPROGRAM #pragma surface surf Lambert vertex:disp nolightmap // #pragma target 3.0 #pragma target 4.6 sampler2D _MainTex; float _Displacement; float _BaselineLength; float _SphericalAngle; float _FocalLength; float _Maximum; struct Input{ float2 uv_MainTex; }; inline float getDepthSpherical(float d) { return asin(_BaselineLength * sin(_SphericalAngle)) / asin(d); } inline float getDepthFlat(float d) { return (_FocalLength / -100.0) * _BaselineLength / d; } void disp (inout appdata_full v){ v.vertex.xyz = v.normal * clamp(getDepthSpherical(tex2Dlod(_MainTex, float4(v.texcoord.xy * float2(1, 0.5), 0, 0)).r), -_Maximum, 0) * _Displacement; } void surf(Input IN, inout SurfaceOutput o){ fixed4 mainTex = tex2D(_MainTex, IN.uv_MainTex * float2(1, 0.5) + float2(0, 0.5)); //o.Emission = mainTex.rgb; o.Albedo = mainTex.rgb; } ENDCG } FallBack "Diffuse" }Educational VR - Need testers for Alpha version (Monkey Walk) Oculus Rift + Touch
Hey there, I'm a solo dev assembling various prototypes into the final version of my first game to be published. I'm focusing my career as a vr developer on educational content. I really find VR as an alternative for all the people who ever day-dreamed during class. I'm on a long road until I build my dream app, one that can teach various subjects and be credited in high school or college. But for now, I hope you can help me build this Demo. Monkey Walk is an explore-to-learn game. This demo (fruit and articles) places the user in a climbing scenario where one may learn Spanish and German vocabulary. This mission's main goal is to teach you a basic understanding of singular articles (like "the" and "a/an") along with some fruits' names and their proper gender. Spanish learning path includes voice recognition to practice pronunciation since day one on your learning path. At the moment the Alpha version is focused on testing locomotion, comfort and setting the mood. It is quite simple and could take no more than 5 minutes to go through the introduction; it includes a simple speech recognition game only for Spanish. Educational content will be tested on the Beta version along with the second level, where users decide which language they want to focus on, a video-lecture explaining the lesson (teaching) and way more vocabulary to learn. I will be doing Beta version test probably this weekend, but I would love to add some of the feedback you guys can provide. Requires Oculus Rift + touch and windows 10 for speech recognition to work. -How comfortable was the experience for you? -Was it easy to climb through the path? -How hard is it to grab the path? -How many times did you fall? / Was it hard to get back up into the path? -How would you describe the mood and ambient? -How many different fruits did you eat? -How many fruits could you spawn through speech? (Speech recognition is not a must answer as there is no audio guidance on pronunciation, still you can read the fruits name and try saying it; tip: try different pronunciations, even fluent Spanish speakers have a hard time, specially with banana and orange as it is a machine and not a human processing your words.) I live in a small city where I'm the only person I know that uses VR. I have had friends come over and help me make decisions as I test them, but what I really need is you, people who are used to playing VR and understand what can be improved. I still have MUCH to learn and to improve. If you want to contribute and be included in the Alpha Channel, please send your e-mail to AbstraktAwareness@gmail.com or post it here if you don't mind. I really appreciate your feedback and time, and so will the future vr learners!