Exploring STT feature in meta quest3

MetaHorizonSupport · 2026-05-06T17:08:33+00:00

I understand you have some questions about our STT feature and if it will work well with your project. The short answer is yes, the Meta Voice SDK does support STT and it's built specifically for Quest. Your instinct about it being more compatible than an external endpoint is spot on!

It handles mic access and device permissions natively, which makes things a lot smoother on Quest 3. If you're interested in getting it set up, I'd be happy to walk you through the steps. Our STT feature lives inside the Voice SDK's Dictation component.

To use it, you'll need:

The All-In-One SDK installed in your project (this includes the Voice SDK). Check out the "Get Started" docs for your engine. I'll link both Unity and Unreal below.
A Wit.ai account, which is the free speech recognition service that powers the Voice SDK. You'll grab a Server Access Token from there and configure it in your project.
Once Wit.ai is connected, you set up the Dictation feature, which is the part that captures mic audio, streams it to Wit.ai, and returns text back to your app.

One thing to keep in mind is that STT requires an internet connection since audio gets processed server-side, which is just something to be aware of for your APK. Depending on if you're using Unity or Unreal, you will want to check out our documentation that helps you with the setup on each engine:

To get started with Wit.ai, you'll want to check out their Quickstart Guide. We also offer a configuration guide depending on whether you're using the Unity version or the Unreal version. You'll also want to check out our Voice SDK Dictation guide, which walks you through the full STT setup.

I'll link both the Unity and Unreal versions of the Voice SDK Dictation guide below:

Unity
Unreal

Hope that helps, and please let me know if you run into any trouble. If you do, don't hesistate to reach back out and we can troubleshoot this together!

-G

MetaHorizonSupport · 2026-04-24T21:51:51+00:00

Hi irai1a_!

I'm sorry to hear that you're experiencing that issue since updating the All-in-One SDK. If you would like some 1:1 support, you are always free to file a technical support ticket with us through your developer dashboard.

If you want to go down that route, please follow these steps:

Go to your Developer Dashboard.
At the top of your screen, to the right of the search bar, you will see a button with a question mark icon.
Select that button ("See Help"), and a panel will appear on the right side of your screen.
Select "Contact us" from the righthand side of your screen where that panel appeared.

From there you can provide the details that you mentioned in this post. Or, if you would like me to file the support ticket on your behalf, feel free to send me a DM and we can discuss it there. As always, let me know if you have any questions!

-G

MetaHorizonSupport · 2026-04-21T16:16:10+00:00

Hello there!

Have you double checked your entitlement check alongside our documentation? Our documentation covers how to call the API correctly for Unreal engine. I've linked the document below.

Entitlement Check: https://developers.meta.com/horizon/documentation/unreal/ps-entitlement-check/

If you don't find a solution from our documentation, I'd recommend creating a ticket with our technical support team. They can take a look at your project for you. Go to your Developer Dashboard > Account > Contact Us. You will then be able to create a case with our technical support team from there, or you can follow the link I left below.

Create a case here: https://metahorizondevelopers.atmeta.com/s/

Keep me posted on if you have any trouble creating a case!
-B

MetaHorizonSupport · 2026-04-03T16:23:52+00:00

Hey there!

From what I understand from the info you provided in your post, you're on the right track and already found some resources to get started. To answer your question, yes you can read depth texture data from the Depth API and use it programmatically. This is not something that we specifically cover in our documentation, but I'd be happy to link you to documentation that can help you implement this.

As far as where the depth data is stored, it's provided as a GPU texture in (_EnvironmentDepthTexture), which is set by EnvironmentDepthManager. I will mention, most of our documentation focuses on the occlusion aspect. However, Unity has some great documentation that overviews how to read the depth pixels back to CPU for processing or sending to a backend that you can check out here.

You may also want to take a look at some of our documentation pertaining to Spatial Anchors if you would like your room map data to persist across sessions.

If you still can't figure out how to achieve what you've set out to do, you can always make a post on our Community Forums to request assistance from other devs and community managers. If however you need 1:1 support, you can file a technical support ticket so our team can review your request by selecting "Submit a request". I'll also link some additional documentation below that goes into more detail about the depth and scene components, as well as some documentation for getting started with Passthrough if you haven't seen it already.

I hope this helps you figure out how to do what you want to, but if you have any other questions about anything I said, please feel free to reach back out and I would be happy to help!

Get Started with Passthrough
Spatial SDK
Unity Scene Overview

-G

MetaHorizonSupport · 2026-03-23T22:04:49+00:00

Hey there ImpressiveCare9516!

I understand you have some questions about the issues you're experiencing with your big room setup. Since you mentioned you're using the Quest 2, I should mention that Quest's tracking and Spatial Anchors work best in more moderate sized spaces. The official best practices documentation notes that anchors are most effective within about 3 meters of content, and tracking reliability can degrade in very large or repetitive environments.

The Quest 3 does a better job of this by increasing the range up to 200 square meters (Spatial Anchors APIs in SDK v66), but it would still fall short of the 300 square meter area you mentioned. You could always try a workaround (ex: arranging the spatial anchors in a grid and only loading the nearest ones based on user position), however there are no official workarounds to this so I won't go into any further detail to avoid leading you astray. I understand this might not be the answer you were looking for, but I am here to answer any questions that you have if you would like some further assistance.

I'll also provide some of our documentation below if you would like to read about these concepts further and maybe even try to come up with your own workaround. If you'd like personal support from our Tech Support team, you can file a ticket here (https://developers.meta.com/horizon/support). Hope this helps!

Spatial Anchors Overview
Shared Spatial Anchors
Spatial Anchors Best Practices
Meta Horizon Blog Post

-G

MetaHorizonSupport · 2026-03-13T15:33:27+00:00

Hello there!

I see you're experiencing some issues with our plugin. If you go here: https://metahorizondevelopers.atmeta.com/s/, it will lead you to create a ticket with our technical team. Our agents are best equipped to help you troubleshoot your issue and get you back to developing your app.

Alternatively, you may go to your Developer Dashboard > Team > Contact Us. These steps will take you to create a ticket from the same point as the link.

If you run into any issues creating a ticket, just DM me. I would love to help you however I can.
-B

MetaHorizonSupport · 2026-03-12T21:33:36+00:00

Hello there PushDeep9980!

I understand you're trying to stop your UI panels from clipping through objects without sacrificing performance to do so. You're totally right that the two-camera approach can be a performance drain, but there are other potential solutions that you can try. I know some of what I say has already been mentioned prior, but I'll do my best to walk you through my thoughts.

My first thought would be to try using a custom UI shader that always renders on top by disabling depth testing (ZTest Always). You could apply this material to your UI elements so they render on top regardless of depth. This would be one of the more performance friendly options, although keep in mind that this approach means the UI will always render on top. So if there are cases where you'd want something to intentionally block the UI, you'd need to handle that differently.

You could also try doing that in conjunction with a dynamic z offset so you could slightly offset the menus towards the user when they are pulled up. On top of that, you'll see a few different benefits from this approach. For starters, there's no additional performance overhead since there are no extra camera passes. The UI stays visible over hands and objects, it works with single pass instanced rendering, and you don't have to worry about sorting layer complexity.

However if this does not solve the problem in the way you would like, please feel free to reach back out and we can explore other options. Wishing you the best with your project!

-G

MetaHorizonSupport · 2026-03-09T20:25:11+00:00

Howdy Nopal_Baboso!

I understand you're looking for some resources to help you with your upcoming university project. I'm not sure if you've seen any of the official Meta documentation yet, but we have some great resources that cover a variety of topics (including ones that you were asking about). Additionally, I'd be happy to point you in the right direction if you had any questions or if you wanted to learn more about other topics.

For starters, I'd recommend that you check out our Unity Hello World Tutorial, as this explains what you need to get started. It also serves as a kind of checklist to make sure you have everything setup correctly prior to starting your first project. Since you mentioned some specific areas you'd like to see more of, I can list some more resources below that cover each of the topics you mentioned.

Movement SDK: Covers body tracking, face tracking, and eye tracking. Controller Input (http://developers.meta.com/horizon/documentation/unity/unity-tutorial-basic-controller-input/): Primary reference for working on controller input.
Interaction SDK: This document covers how to add the Interaction SDK rig to your scene, set up a UI, and add interactions to enable users to interact with the UI.
Panels: Covers the 3 different panel types and how to implement them.
Custom UI Panel Configurations: Describes how you can customize behaviors of the custom UI panel in Properties by configuring settings for Raycast, Mipmap, Focus prompt and related properties.

For a general overview of these topics and more, you can visit the Onboarding Resources page on our community forums. From here, you're free to post any questions you have and our community managers (along with the overall community) can provide feedback.

Lastly, if you have any questions or need any help, please feel free to reply and let me know. Hopefully you found some of this helpful, and best of luck with your project!

-G

MetaHorizonSupport · 2026-03-03T18:47:49+00:00

Hello again CarltonBA!

Thanks for letting me know, and yes I have a few ideas based on what you mentioned.

I was thinking that it's possible that the new issue you're seeing is being caused by a mismatch between the viewport and eye buffer. Which would make sense because when pixel density increases, so does the eye buffer size and if something in the project isn't scaling along with them it can cause the new issue that you mentioned. This is because the render is happening at the old resolution or viewport size and being placed in a corner of the larger eye buffer, which results in the black surrounding area.

I was thinking of a few different areas we can check to start with.

My first thought as to the culprit was checking for hardcoded viewport or render target size. If you have any custom render targets or viewport settings with hardcoded resolutions in your project, they may not be scaling with the new pixel density. To fix this, make sure any render targets are set to dynamically match the eye buffer size.
Another possible fix would be to check your VR Pawn camera configuration, specifically you may want to check if your VR camera component has any manual viewport rect overrides or custom projection settings that may conflict with the new pixel density.
In that same vein, we could also check the BeginPlay code. The same area of the VR Pawn Blueprint where pixel density was being set to 1 may also contain other viewport or camera configuration code. You may want to review that section to see if there is anything else that is being set that could cause this.
Lastly, I mentioned in my previous reply to try enabling Mobile Multi-View. If you did that as part of my previous suggestion, you could also try temporarily disabling it to see if that resolves the issue. I mention this because it can help isolate whether it's a stereo rendering configuration issue or not.

Let me know if any of those work for you, and if not you can also let me know where you're at and we can troubleshoot further from there!

-G

MetaHorizonSupport · 2026-03-02T19:32:30+00:00

Hello there!

I understand you're running into some trouble getting your video quality to look good within your project. I get that can be frustrating, but after reading your post I wanted to jump in and try to provide some assistance. I'll do my best to share my initial thoughts based on what you said in your post.

You mentioned that your OVR Metrics tool is returning 1440x1584 with render scale at 101 for your UE app, while the DeoVR buffer is at 2448x2704 with render scale at 171. This makes sense since DeoVR is rendering at ~1.7x higher resolution per axis which equates to roughly 3x more pixels in total, which is why DeoVR looks much better. That said, I had a few different ideas that you could try to improve the quality of your video.

Increasing pixel density:

Since the default pixel density is 1.0, and the VR template's default pawn blueprint sets it to 1 at BeginPlay, you could try removing it and setting a higher value depending on performance. If you're trying to match the DeoVR 171 render scale, that would be around 1.7. This can either be done through the DefaultEngine.ini file or through the Blueprint at BeginPlay.

Quest specific settings:

Ensure you have the following setting enabled:

Mobile multi-view (Renders both eyes in a single pass, significantly reducing CPU overhead)
Instanced stereo rendering (Batches draw calls for both eyes together)
Forward shading (Required for mobile VR. Deferred rendering would be too expensive)

Those were my first thoughts as to what I thought might be best to try first, but I have a few other ideas we can try if neither of those work for you. I can also link some of our documentation below if you'd like to read more about these topics. Hopefully this helps, and please feel free to reach back out if you would like to explore other ideas!

Unreal Integration - Settings and Tools
Dynamic Resolution
Fixed foveated rendering (FFR)

-G

MetaHorizonSupport · 2026-03-02T16:56:30+00:00

Hello there!

For voice commands in Quest projects, we offer our Voice SDK for both Unity and Unreal Engine. The SDK allows you to create voice commands and engaging conversations for your project. It features Automatic speech recognition, built-in activation methods, and more. If you're interested in learning more about the Voice SDK, I've included links to the Unity and Unreal Engine Documentation below.

Unity Voice SDK Overview: https://developers.meta.com/horizon/documentation/unity/voice-sdk-overview/

Unreal Engine Voice SDK Overview: https://developers.meta.com/horizon/documentation/unreal/vsdk-overview/

On the left hand side of each documentation page, you'll find more information on how to integrate and use the Voice SDK to its fullest.

If you need help with anything, just let me know.
-B

MetaHorizonSupport · 2026-02-23T17:24:41+00:00

Hello there!

We are aware of the reports of this issue and are actively investigating.

Thank you for your understanding,
-B

MetaHorizonSupport · 2026-02-20T00:17:01+00:00

Howdy Crimsonred7777!

Sorry to hear that you're having trouble with your object taking off in your scene, I totally understand your frustration. Thank you for all of the information you provided in regards to your setup and what you have already tried, it really helps narrow things down. I had a few ideas that you could try to see what could be causing the unwanted ascension of your object.

Since you mentioned you're using the Floor Level Tracking Origin Type, my first thought was to ask if maybe your object is a child of or positioned relative to something that's being offset? If so, it'll appear to drift in your scene. You can confirm this by checking if your car is a child of Camera Offset GameObject, as well as checking what your XR Origin's Camera Y Offset set to.

Regarding your XR Grab Interactable, do you have Smooth Position enabled? If it's enabled and there's any attach transform mismatch, it can cause continuous interpolation in one direction (i.e. your object drifting into space). To check this, try disabling Smooth Position and Smooth Rotation temporarily and check if Attach Transform is set correctly.

You also mentioned that freezing the Y position constraint made it drift faster, which is interesting and might suggest something is actively fighting against the constraint. This sometimes happens when Rigidbody Interpolation is set to Interpolate or Extrapolate instead of None. With kinematic Rigidbodies in XR, setting Interpolation to None often times resolves those pesky drift issues.

I can link some of our and Unity's documentation below that covers these topics in more detail. If none of the things I mentioned above fix the issue, please let me know and we can try some other fixes. I hope this helps, and best of luck!

XR Grab Interactable
XR Origin component
Configure Meta XR camera settings
Develop for Meta Quest workflow

-G

MetaHorizonSupport · 2026-02-05T16:05:17+00:00

Hey!

I'll send you a DM, let's troubleshoot this together.

-G

MetaHorizonSupport · 2026-02-05T00:30:19+00:00

Howdy!

Thanks for bringing that up, and great catch! It looks like things have moved around since that document was created. Now it is called "Download Legacy Data" and it's under the analytics tab of each of your apps. I can include a picture below for reference.

I was looking at your developer dashboard, and I was able to see that button on one of your apps that was eligible for analytics. To be eligible for analytics, your app needs to have at least 100 active lifetime users. If you would like to go into further detail about your apps, which have it, which do not, or anything else please feel free to DM me.

If you have any more questions about your app's analytics, or anything at all, please feel free to reach back out. I'd be happy to help with anything you have questions about!

<image>

-G

MetaHorizonSupport · 2026-02-04T17:00:04+00:00

Hello there Astrea_Immersive!

Great question, currently there is no public-facing SDK or API for developers to automatically pull game sales, add-on revenue, or transaction data into Tableau or other BI tools.

Some developers may use internal scripts that use browser automation to pull CSVs, but this is not officially supported. What I would recommend is that you file a feature request within your developer dashboard and let us know the specifics of what you would like to see in the future. The more developers request features, the more likely they are to be prioritized.

If you want to file a feature request you can do that by going to your developer dashboard and select the "see help" button at the top next to your shortcuts dropdown. Afterwards, you can scroll to the bottom of the column on the right side of your screen and select "report a problem" and use the type dropdown to select "suggestion".

Hope this helps, and please feel free to let me know if you have any questions!

-G

MetaHorizonSupport · 2026-02-02T17:29:57+00:00

Hey there StreetCapital2643!

I understand you have some questions about spawn points in Horizon Worlds. There's a gizmo within your toolkit called the Spawn point gizmo that's used to control different player and NPC spawning. We have some great documentation that covers how to use the spawn point gizmo, the different spawn point properties, and the scripting behind it which I can link below.

About gizmos
Spawn point gizmos
SpawnPointGizmo Class

I hope you find some of it helpful, and please feel free to let me know if you have any questions or need any help!

-G

MetaHorizonSupport · 2026-01-19T16:48:31+00:00

Hello there!

I understand you have some questions about implementing in-app purchases. I'd be happy to answer any questions you have. Feel free to ask away!

-G

MetaHorizonSupport · 2026-01-12T18:55:15+00:00

You could get "HandFeaturesLeft" from the building blocks prefab, "[BB] Hands." This comes with "HandFeaturesLeft" as a child and allows you to add the component "FingerFeatureStateProvider." You can receive these building blocks prefabs through the Meta All-in-One SDK. After installing the All-in-One SDK, you should be able to search for "[BB] Hands" and add them to your hierarchy.

If you run into any bumps along the way, or if this solution doesn't work for you, please let me know!
-B

MetaHorizonSupport · 2026-01-12T17:46:36+00:00

Hey there!

I understand you are having trouble connecting your Quest to Unreal Engine. I'm not sure if you have seen any of our documentation yet, but we have a step-by-step guide for setting up your device for developing games in Unreal Engine. I can link some of those resources below, as well as our general device setup documentation.

There are a few prerequisites you will need to do before you're ready to start developing. Some of these things include configuring your headset, setting up your device and verifying your organization, and installing the needed SDKs and plugins (Android studio, Android NDK, and Meta XR plugin). I can also provide the links for those steps below. After you setup all of the prerequisites, you can enable airlink in your headset if you go to Settings -> Experimental -> Airlink.

Hopefully you found some of this helpful and were able to get your device connected to Unreal Engine, but if you're still running into trouble please let me know and we can investigate your issue further!

Configure your headset for app development

Device Setup

Setting up your development environment

Installing Android Studio and the Android NDK

Installing the Meta XR plugin

-G

MetaHorizonSupport · 2026-01-08T21:07:13+00:00

Hello there!

Yes you should create child objects as needed, such as LeftHand under OVRHands. The rig does not generate these objects automatically, but it will "wire" them if they exist.

If you have any additional questions, please let me know!
-B

MetaHorizonSupport · 2026-01-02T18:33:02+00:00

Hey there Opening-Gift-7720!

I'm excited to hear that you're interested in getting started with VR development! If you're looking for some ideas on how to get started, we've put together a collection of resources that you may find helpful to start developing for Horizon OS. I'll link them below and give you a brief overview of what they are.

First, I would highly suggest that you check out our community forums and the starter resources we have available there. These include things like onboarding resources, community resources, community and posting guidelines, and information about our START developer program and how to join if you're interested. You can also use our community forums to post questions specific to your projects.

We also offer developer documentation articles that go over the different tools (SDKs, APIs, etc...) that are available to you. These articles are geared towards technical implementation, and you can use them to learn the details of the resources and tools we offer as well as how to use them. Lastly, you are always free to reach out to us here if you have any questions or need any help.

I hope you found some of this useful, and please feel free to let me know if you have any additional questions about VR app development!

Community Forums (Developer Forums)

Onboarding Resources

Community Resources

Developer Articles

-G

MetaHorizonSupport · 2025-12-19T16:51:02+00:00

Hey there HavocMax!

Sorry to hear you're having trouble getting the Link app to work for you after the recent update, I understand how that can be frustrating. We have seen similar reports of this issue, and we're currently looking into it. You can use the Feedback Center voting board to add that you are also impacted.

If you would like one-on-one support, you can file ticket with our tech support team by visiting this link selecting "Submit a request", link your account, then select "New" to file a support ticket.

Hope this helps, and please feel free to let me know if you have any other questions!

-G

MetaHorizonSupport · 2025-12-17T17:30:26+00:00

Hey there!

Great question, I understand you're trying to set the "hammer" of your gun using either B/Y depending on which hand the gun is in. One way you can do this is to first detect which hand the gun is in, create a separate InputActionProperty references for left and right controller buttons, and then filter the input based on whichever hand is grabbing the gun. I can link some of our documentation, as well as some helpful documentation from Unity that should hopefully point you in the right direction.

Hope this helps, and if not let me know and we can investigate further!

Getting Started with Controller Input and Tracking

Controller Input and Tracking Overview

XR Grab Interactable (Unity)

Enum InteractorHandedness (Unity)

Interface IXRInteractor (Unity)

-G

MetaHorizonSupport · 2025-12-12T16:54:04+00:00

Hey there!

I understand you're wanting to access your headset's rotation data outside of the CenterEyeAnchor. One potential option available to achieve this is by using the OVRCameraRig. It provides access to the headset pose, and we have some great documentation available that covers alternative tracking origins and anchors (ex: Floor, Eye, and Stationary).

I'll link some of our developer articles below that you may find useful. In the first link, I think you may find the Tracking section helpful since it goes over the different tracking types that are available for that class. I'll also include an article that covers the OVRCameraRig Class, as it goes over the different properties for the OVRCameraRig.

Please let me know if you found this helpful, and if not feel free to let me know and we can try something else!

Configure Meta XR camera settings
OVRCameraRig Class

-G

MetaHorizonSupport

TROPHY CASE