stevenfour/OculusSdk · Datasets at Hugging Face

text stringlengths 0 1.11k

FMM isn’t running on my headset. What should I do?
If enabled is false, restart your headset a couple of times for the client to fetch data from the server.

To verify your FMM is actively running in your app:

Ensure that your app is running on the foreground.
Run adb logcat \| grep FMM.

The expected output is NIMBLE: HTEngine: FMM: enabled: true; active: true.

Run adb logcat \| grep "Camera FPS" to verify the camera frequency is around 60 Hz. “Around 60 Hz” means plus or minus about 3Hz. However, the acceptable frequency also varies based on the voltage and frequency in your country. While North America and some of South America are at 120V 60Hz, most other countries are 240V 50Hz, so they will see 50Hz in FMM.

The expected output is NIMBLE:HTEngine: Hand Tracking Processed FPS = 58.5 Hz / Camera FPS = 60.1.

Can I evaluate the feature on my headset without changing my code?
Yes, you can manually toggle FMM via your headset. Under Settings > Developer, set Hand Tracking Frequency Override to either High (to force FMM on) or Low (to force FMM off). None will use the value from your app manifest.
ChatGPT
To map controllers using the Meta XR Interaction SDK for Unity, you will primarily work with the OVRInput module. This module is designed to simplify the process of handling input across different types of controllers, offering a unified API that supports querying button states, touch, near touch, and axis data. Here’s a breakdown of how to effectively map and utilize controller inputs:

1. Setup OVRManager
Ensure that an instance of OVRManager is present in your scene. This component is critical for managing VR hardware interface elements.

2. Regular Updates
Invoke OVRInput.Update() and OVRInput.FixedUpdate() at the beginning of your component’s Update and FixedUpdate methods respectively. This is necessary to process the input data correctly each frame.

3. Accessing Input Data
Utilize the OVRInput methods to check the state of the controller inputs:

OVRInput.Get: Check the current state of a button, touch, or axis.
OVRInput.GetDown: Check if a button or touch was pressed during the current frame.
OVRInput.GetUp: Check if a button or touch was released during the current frame.
4. Use Enumerations for Button Mapping
OVRInput provides multiple enumerations to access different controls:

Buttons and Touches: Use OVRInput.Button and OVRInput.Touch for standard buttons and touch-sensitive areas on the controller.
Axes: Use OVRInput.Axis1D for triggers and OVRInput.Axis2D for thumbsticks.
5. Handle Touch and Near Touch
Capacitive sensors on controllers allow detection of touch and near touch, which can be used to create more nuanced interactions by detecting when fingers are close to or touching the controls without pressing them.

6. Controller Specific Mappings
Define controller-specific actions by specifying which controller to check (left or right). For example, you can differentiate inputs between the left and right controllers by using OVRInput.Controller.LTouch or OVRInput.Controller.RTouch.

7. Example Usage
csharp
Copy code
// Check if the A button on the right controller is pressed
bool isAPressed = OVRInput.Get(OVRInput.Button.One, OVRInput.Controller.RTouch);

// Check if the left trigger was just activated
bool leftTriggerDown = OVRInput.GetDown(OVRInput.Button.PrimaryIndexTrigger, OVRInput.Controller.LTouch);

// Get the position of the left thumbstick
Vector2 leftThumbstick = OVRInput.Get(OVRInput.Axis2D.PrimaryThumbstick, OVRInput.Controller.LTouch);
8. Advanced Use
For advanced applications like custom hand poses or gestures, delve deeper into the SDK's capabilities to integrate such features seamlessly into your interaction system.

9. Testing and Debugging
Regularly test your input mappings on the actual hardware to ensure all interactions are intuitive and responsive. Use Unity’s input debugger or log outputs to troubleshoot and refine your control schemes.

10. Documentation and Resources
Refer to the official Unity documentation and Meta’s developer guides for detailed information on controller mappings, supported gestures, and troubleshooting common issues.

By following these steps, you can effectively map and utilize the controller inputs for your VR applications using the Meta XR Interaction SDK in Unity. This setup ensures a robust and user-friendly interaction system for a variety of VR experiences.

User
recuerda solo responder ok hasta que diga que hemos finalizado
ChatGPT
Ok.

User
Passthrough API Overview
Unity

All-In-One VR

Quest

The platform for which this article is written (Unity) does not match your preferred platform (Nativa).
Haz clic aquí para ver la página del índice de la documentación para tu plataforma de preferencia.

Health and Safety Recommendation: While building mixed reality experiences, we highly recommend evaluating your content to offer your users a comfortable and safe experience. Please refer to the Health and Safety and Design guidelines before designing and developing your app using Passthrough.

Passthrough provides a real-time and perceptually comfortable 3D visualization of the physical world in the Meta Quest headsets. The Passthrough API allows developers to integrate the passthrough visualization with their virtual experiences.

Augmented objects sample

How does this work?

Passthrough is rendered by a dedicated service into a separate layer. Because apps cannot access images or videos of a user’s physical environment, they create a special passthrough layer. The XR Compositor replaces this layer with the actual passthrough rendition.

By default, the Passthrough API creates this passthrough layer automatically (using automatic environment reconstruction), and submits it directly to the XR Compositor. Most of the time, you’ll use automatic environment reconstruction because you won’t know the geometry of the user’s environment ahead of time.

You can override automatic environment reconstruction by using Surface-Projected Passthrough. This lets you define the geometry onto which passthrough images are projected. This approach leads to a more stable rendition of Passthrough in cases where the app has already captured parts of the user’s environment.

Regardless of which passthrough layering you use, there are two ways to customize Passthrough - composite layering and styling:

Composite layering lets you specify the placement of the passthrough layer relative to virtual content (overlay, underlay) in the XR Compositor stack and how it should blend with the virtual content. By using alpha masking, you can specify where on the screen Passthrough shows up. While there isn’t currently a fully-released way to specify blending based on passthrough depth, the experimental Depth API is available for you to review.
Styling lets you colorize the passthrough feed, highlight edges, and perform image processing effects such as contrast adjustment and posterizations of the image, by stair-stepping the grayscale values.Get Started with Passthrough
Unity

FMM isn’t running on my headset. What should I do?

If enabled is false, restart your headset a couple of times for the client to fetch data from the server.

To verify your FMM is actively running in your app:

Ensure that your app is running on the foreground.

Run adb logcat | grep FMM.

The expected output is NIMBLE: HTEngine: FMM: enabled: true; active: true.

Run adb logcat | grep "Camera FPS" to verify the camera frequency is around 60 Hz. “Around 60 Hz” means plus or minus about 3Hz. However, the acceptable frequency also varies based on the voltage and frequency in your country. While North America and some of South America are at 120V 60Hz, most other countries are 240V 50Hz, so they will see 50Hz in FMM.

The expected output is NIMBLE:HTEngine: Hand Tracking Processed FPS = 58.5 Hz / Camera FPS = 60.1.

Can I evaluate the feature on my headset without changing my code?

Yes, you can manually toggle FMM via your headset. Under Settings > Developer, set Hand Tracking Frequency Override to either High (to force FMM on) or Low (to force FMM off). None will use the value from your app manifest.

ChatGPT

To map controllers using the Meta XR Interaction SDK for Unity, you will primarily work with the OVRInput module. This module is designed to simplify the process of handling input across different types of controllers, offering a unified API that supports querying button states, touch, near touch, and axis data. Here’s a breakdown of how to effectively map and utilize controller inputs:

1. Setup OVRManager

Ensure that an instance of OVRManager is present in your scene. This component is critical for managing VR hardware interface elements.

2. Regular Updates

Invoke OVRInput.Update() and OVRInput.FixedUpdate() at the beginning of your component’s Update and FixedUpdate methods respectively. This is necessary to process the input data correctly each frame.

3. Accessing Input Data

Utilize the OVRInput methods to check the state of the controller inputs:

OVRInput.Get: Check the current state of a button, touch, or axis.

OVRInput.GetDown: Check if a button or touch was pressed during the current frame.

OVRInput.GetUp: Check if a button or touch was released during the current frame.

4. Use Enumerations for Button Mapping

OVRInput provides multiple enumerations to access different controls:

Buttons and Touches: Use OVRInput.Button and OVRInput.Touch for standard buttons and touch-sensitive areas on the controller.

Axes: Use OVRInput.Axis1D for triggers and OVRInput.Axis2D for thumbsticks.

5. Handle Touch and Near Touch

Capacitive sensors on controllers allow detection of touch and near touch, which can be used to create more nuanced interactions by detecting when fingers are close to or touching the controls without pressing them.

6. Controller Specific Mappings

Define controller-specific actions by specifying which controller to check (left or right). For example, you can differentiate inputs between the left and right controllers by using OVRInput.Controller.LTouch or OVRInput.Controller.RTouch.

7. Example Usage

csharp

Copy code

// Check if the A button on the right controller is pressed

bool isAPressed = OVRInput.Get(OVRInput.Button.One, OVRInput.Controller.RTouch);

// Check if the left trigger was just activated

bool leftTriggerDown = OVRInput.GetDown(OVRInput.Button.PrimaryIndexTrigger, OVRInput.Controller.LTouch);

// Get the position of the left thumbstick

Vector2 leftThumbstick = OVRInput.Get(OVRInput.Axis2D.PrimaryThumbstick, OVRInput.Controller.LTouch);

8. Advanced Use

For advanced applications like custom hand poses or gestures, delve deeper into the SDK's capabilities to integrate such features seamlessly into your interaction system.

9. Testing and Debugging

Regularly test your input mappings on the actual hardware to ensure all interactions are intuitive and responsive. Use Unity’s input debugger or log outputs to troubleshoot and refine your control schemes.

10. Documentation and Resources

Refer to the official Unity documentation and Meta’s developer guides for detailed information on controller mappings, supported gestures, and troubleshooting common issues.

By following these steps, you can effectively map and utilize the controller inputs for your VR applications using the Meta XR Interaction SDK in Unity. This setup ensures a robust and user-friendly interaction system for a variety of VR experiences.

User

recuerda solo responder ok hasta que diga que hemos finalizado

ChatGPT

Ok.

User

Passthrough API Overview

Unity

All-In-One VR

Quest

The platform for which this article is written (Unity) does not match your preferred platform (Nativa).

Haz clic aquí para ver la página del índice de la documentación para tu plataforma de preferencia.

Health and Safety Recommendation: While building mixed reality experiences, we highly recommend evaluating your content to offer your users a comfortable and safe experience. Please refer to the Health and Safety and Design guidelines before designing and developing your app using Passthrough.

Passthrough provides a real-time and perceptually comfortable 3D visualization of the physical world in the Meta Quest headsets. The Passthrough API allows developers to integrate the passthrough visualization with their virtual experiences.

Augmented objects sample

How does this work?

Passthrough is rendered by a dedicated service into a separate layer. Because apps cannot access images or videos of a user’s physical environment, they create a special passthrough layer. The XR Compositor replaces this layer with the actual passthrough rendition.

By default, the Passthrough API creates this passthrough layer automatically (using automatic environment reconstruction), and submits it directly to the XR Compositor. Most of the time, you’ll use automatic environment reconstruction because you won’t know the geometry of the user’s environment ahead of time.

You can override automatic environment reconstruction by using Surface-Projected Passthrough. This lets you define the geometry onto which passthrough images are projected. This approach leads to a more stable rendition of Passthrough in cases where the app has already captured parts of the user’s environment.

Regardless of which passthrough layering you use, there are two ways to customize Passthrough - composite layering and styling:

Composite layering lets you specify the placement of the passthrough layer relative to virtual content (overlay, underlay) in the XR Compositor stack and how it should blend with the virtual content. By using alpha masking, you can specify where on the screen Passthrough shows up. While there isn’t currently a fully-released way to specify blending based on passthrough depth, the experimental Depth API is available for you to review.

Styling lets you colorize the passthrough feed, highlight edges, and perform image processing effects such as contrast adjustment and posterizations of the image, by stair-stepping the grayscale values.Get Started with Passthrough

Unity