Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
 Mamadou Babaei
|
524aa1cd4e
|
||
|
Mamadou Babaei
|
602f8b4470
|
||
|
Mamadou Babaei
|
519e00755c
|
||
|
Mamadou Babaei
|
b32491811d
|
@@ -68,6 +68,7 @@ Welcom to the SenseGlove Unreal Engine Handbook!
|
||||
- [Third-Party Tutorials](misc/android-standalone-deployment/third-party-tutorials/README.md)
|
||||
- [Upgrade Guide](misc/upgrade-guide/README.md)
|
||||
- [Optimizing for Higher FPS](misc/optimize-higher-fps/README.md)
|
||||
- [Third-Party Tutorials](misc/optimize-higher-fps/third-party-tutorials/README.md)
|
||||
|
||||
# 🛠️ Advanced Topics
|
||||
|
||||
@@ -79,6 +80,7 @@ Welcom to the SenseGlove Unreal Engine Handbook!
|
||||
- [Consuming FXRMotionControllerData](advanced-topics/openxr/consuming-fxrmotioncontrollerdata/README.md)
|
||||
- [Blueprint](advanced-topics/openxr/consuming-fxrmotioncontrollerdata/blueprint.md)
|
||||
- [C++](advanced-topics/openxr/consuming-fxrmotioncontrollerdata/cpp.md)
|
||||
- [Third-Party Integrations](advanced-topics/openxr/third-party-integrations/README.md)
|
||||
- [Third-Party Tutorials](advanced-topics/openxr/third-party-tutorials/README.md)
|
||||
|
||||
# 🔌 Low-Level API
|
||||
|
||||
@@ -0,0 +1,265 @@
|
||||
# Third-Party OpenXR Integrations
|
||||
|
||||
The **SenseGlove Unreal Engine Plugin** registers itself as an `OpenXRHandTracking` provider, making it a fully compatible, drop-in replacement for Epic’s own **OpenXRHandTracking** plugin in Unreal Engine. This allows it to integrate seamlessly with any third-party system or plugin that can consume OpenXR hand-tracking data.
|
||||
|
||||
One notable example is the open-source, MIT-licensed [VR Expansion Plugin (VRE)](#vr-expansion-plugin).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> As explained in the
|
||||
> [Third-Party Tutorials: Consuming OpenXR Hand-Tracking Data](../third-party-tutorials/)
|
||||
> section, it’s entirely possible to build your own custom hand interaction
|
||||
> system without relying on
|
||||
> [SGPawn](../../../getting-started/setup-senseglove-default-classes/sgpawn.html)
|
||||
> or any third-party OpenXR-compatible interaction plugin altogether.
|
||||
>
|
||||
> If your project requires finer-grained control than what these solutions
|
||||
> offer, the tutorials in that section will guide you through understanding the
|
||||
> OpenXR hand-tracking data format in Unreal Engine and help you implement a
|
||||
> fully tailored interaction system from the ground up in a few hours.
|
||||
|
||||
As the SenseGlove Unreal Engine Plugin is fully OpenXR-compliant, it provides OpenXR hand-tracking data in the expected format and takes over as the active provider within Unreal. If your existing interaction system (e.g. VRE plugin) already uses OpenXR hand-tracking, SenseGlove will function as a direct tracking source instead of a real hand.
|
||||
|
||||
> [!NOTE]
|
||||
> Since most hand-tracking systems are not capable of haptics feedback,
|
||||
> integrating SenseGlove's haptic feedback requires a small amount of additional
|
||||
> effort.
|
||||
>
|
||||
> The SenseGlove API is fully exposed to Unreal Engine via C++ and Blueprint,
|
||||
> so triggering haptic feedback is as simple as calling a function.
|
||||
> For more information, refer to the [Blueprint Changes](#blueprint-changes)
|
||||
> section below.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you're using a third-party OpenXR hand interaction system, configuring the
|
||||
> [Wrist-Tracker Hardware Settings](../../../getting-started/setup-wrist-tracking-hardware/)
|
||||
> will likely have no effect, and your hand offsets may appear at the incorrect
|
||||
> location in the scene.
|
||||
>
|
||||
> This is because those settings are only recognized by SenseGlove’s native
|
||||
> actors and components such as `SGPawn`, `SGWristTrackerComponent`, etc.
|
||||
> Most third-party plugins are unaware of these settings. As a result, you'll
|
||||
> need to figure out how to manually apply the appropriate offsets within your
|
||||
> chosen OpenXR hand interaction system.
|
||||
>
|
||||
> For example, the VRE plugin provide similar configurations in their plugin's
|
||||
> settings section. For more information refer to the
|
||||
> [Changing Wrist-Tracker Offsets](#changing-wrist-tracker-offsets) section
|
||||
> below.
|
||||
|
||||
## Comparison of Supported OpenXR Hand-Interaction Systems
|
||||
|
||||
| | **Built-in?** | **Works out of the box?** | **Beginner-friendly?** | **Learning Curve** | **Featureful** | **Customizable?** | **Supports Custom Gestures?** |
|
||||
|-------------------------------------|---------------|------------------------------------|--------------------------------------------------|-----------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
|
||||
| **SGPawn** | ✅ Yes | ✅ Yes | ✅ Most beginer-friendly | ✅ Very easy | ⚠️ Very basic | ⚠️ Very limited | ❌ Not yet, maybe added in the future |
|
||||
| **SenseGlove OpenXR** | ✅ Yes | ❌ Requires Blueprint or C++ coding | ✅ Requires a few hours of watching tutotrials | ✅ Moderate | ❌ You need to develop your own features and functionalities from scratch | ✅ Your imagination, creativity, and skill level are your limits | ✅ You have to implement your own recognition logic; example pinch detection algorithm is taught in the tutorial series |
|
||||
| **VR Expansion Plugin** | ❌ No | ⚠️ Partially – requires setup | ❌ Best suited for intermediate or advanced users | ⚠️ Steep | ✅ Diverse features and functionalities | ✅ Highly customizable | ✅ Via custom logic |
|
||||
| **Other OpenXR-compatible Plugins** | ❌ No | ❓ Check their documentation | ❓ Check their documentation | ❓ Check their documentation | ❓ Check their documentation | ❓ Check their documentation | ❓ Check their documentation |
|
||||
|
||||
## VR Expansion Plugin
|
||||
|
||||
The [**VR Expansion Plugin (VRE)**](https://vreue4.com/) is a robust, community-driven plugin for Unreal Engine that focuses on advanced VR interaction and gameplay mechanics. It is open-source (MIT licensed), actively maintained, and has received support from Epic via the [MegaGrants program](https://www.unrealengine.com/en-US/megagrants).
|
||||
|
||||
Designed to extend Unreal’s capabilities for virtual reality, VRE offers a modular set of tools covering:
|
||||
|
||||
- Multiplayer and networking
|
||||
- Locomotion systems
|
||||
- Object gripping and interaction
|
||||
- Custom movement and physics handling
|
||||
|
||||
The plugin is particularly useful for teams building sophisticated VR experiences. While it's beginner-friendly to an extent, its depth and flexibility are **best suited for intermediate to advanced Unreal Engine developers**. Whether you're prototyping with built-in features or extracting specific systems for your own framework, VRE offers a rich foundation for VR development.
|
||||
|
||||
> [!NOTE]
|
||||
> For support and assistance with the VRE plugin, you can join
|
||||
> [its active and welcoming Discord community](https://discord.gg/P4V7TY8BQy),
|
||||
> known for being responsive and supportive.
|
||||
|
||||
### SGVRETemplate Demo Scene
|
||||
|
||||
To showcase how SenseGlove can be integrated with OpenXR-compatible third-party interaction systems, SenseGlove provides a ready-to-use [VR Expansion Plugin Integration Demo for Unreal Engine 5.4](https://dev.azure.com/SenseGlove/_git/SGVRETemplate).
|
||||
|
||||
This repository includes UE `5.4`–compatible versions of both the **SenseGlove** and **VR Expansion** plugins, with all necessary setup and configuration already in place. Simply download the project and it should run out of the box, allowing you to explore the integration without additional setup.
|
||||
|
||||
> [!NOTE]
|
||||
> SenseGlove provides this demo to demonstrate the potential for integrating
|
||||
> with third-party OpenXR-based hand interaction systems.
|
||||
> Please note that the **VR Expansion Plugin** is a third-party solution, and as
|
||||
> such, **we do not offer official support for it**.
|
||||
>
|
||||
> For help with the VRE plugin, refer to its documentation at
|
||||
> [**vreue4.com**](https://vreue4.com/) and consider joining the
|
||||
> [**official VRE Discord community**](https://discord.gg/P4V7TY8BQy),
|
||||
> which is active, supportive, and very responsive.
|
||||
|
||||
### SGVRETemplate Modifications
|
||||
|
||||
The [**SGVRETemplate**](https://dev.azure.com/SenseGlove/_git/SGVRETemplate) is built on top of the [VR Expansion Plugin Example Template](https://github.com/mordentral/VRExpPluginExample). However, since the original template is not directly compatible with SenseGlove, several adjustments were necessary.
|
||||
|
||||
In addition, a few known issues with OpenXR support in the VR Expansion Plugin for Unreal Engine `5.4` required us to modify the plugin itself to ensure smooth integration.
|
||||
|
||||
Below is an overview of the key modifications made to both the project template and this version of the VRE plugin.
|
||||
|
||||
#### Blueprint Changes
|
||||
|
||||
- **Content/VRE/Core/Character/BP_VRCharacter**: Four functions were added: `SendVibration`, `SendFFB`, `SendSqueeze`, and `ResetHaptics`. These functions retrieve the glove instance and send the appropriate haptic command to it. In the `OnPossessed` event, `Load Controller by Name` was added along with a string uproperty `Tracking Offset`, which is used to load the correct tracking offsets based on the selected profile.
|
||||
|
||||
> [!NOTE]
|
||||
> If you'd like to implement your own haptic functions, the most convenient
|
||||
> approach is to
|
||||
> [safely acquire a glove instance](../../../advanced-topics/safe-glove-access-blueprint/).
|
||||
> Once you have the glove instance, applying haptic feedback is as simple as
|
||||
> calling the appropriate function.
|
||||
>
|
||||
> SenseGlove supports three types of haptics: Vibrations, Force-feedback, and
|
||||
> Wrist-squeeze.
|
||||
>
|
||||
> - Using `Send Custom Waveform`, you can send vibrations to the glove instance.
|
||||
> - Using `Queue Command Force Feedback Levels`, you can send force-feedback.
|
||||
> - Using `Queue Command Wrist Squeeze`, you can send a wrist-squeeze command to
|
||||
> the glove.
|
||||
>
|
||||
> Each of these functions can be called directly on the glove instance to
|
||||
> trigger the desired haptic feedback.
|
||||
|
||||
- **Content/VRE/Core/GraspingHands/GraspingHandManny**: In the `SetupFingerAnimations` function, replace the hardcoded check for `HandType == Left` with a string comparison: convert the enum to a string and check if it contains `"Left"`. This allows compatibility with alternative tracking sources such as `"Left Foot"`.
|
||||
|
||||
#### C++ Changes
|
||||
|
||||
- **Plugins/VRExpansionPlugin/Source/VRExpansionPlugin/Public/Grippables/HandSocketComponent.h**: The following line was added as a public `UPROPERTY` in the header file:
|
||||
|
||||
```cpp
|
||||
UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "Hand Animation")
|
||||
float HandAnimationProgress = 0.0f;
|
||||
```
|
||||
|
||||
- **Plugins/VRExpansionPlugin/Source/VRExpansionPlugin/Private/Grippables/HandSocketComponent.cpp**: In the function `bool UHandSocketComponent::GetBlendedPoseSnapShot(FPoseSnapshot& PoseSnapShot, USkeletalMeshComponent* TargetMesh, bool bSkipRootBone, bool bFlipHand)`, the `TrackLocation` calculation was modified from:
|
||||
|
||||
|
||||
```cpp
|
||||
if (TrackIndex != INDEX_NONE && (!bSkipRootBone || TrackIndex != 0))
|
||||
{
|
||||
double TrackLocation = 0.0f;
|
||||
HandTargetAnimation->GetBoneTransform(LocalTransform, FSkeletonPoseBoneIndex(TrackMap[TrackIndex].BoneTreeIndex), TrackLocation, false);
|
||||
}
|
||||
else
|
||||
{
|
||||
```
|
||||
|
||||
To:
|
||||
|
||||
```cpp
|
||||
if (TrackIndex != INDEX_NONE && (!bSkipRootBone || TrackIndex != 0))
|
||||
{
|
||||
double TrackLocation = HandTargetAnimation->GetPlayLength() * HandAnimationProgress;
|
||||
HandTargetAnimation->GetBoneTransform(LocalTransform, FSkeletonPoseBoneIndex(TrackMap[TrackIndex].BoneTreeIndex), TrackLocation, false);
|
||||
}
|
||||
else
|
||||
{
|
||||
```
|
||||
|
||||
- **Plugins/VRExpansionPlugin/Source/VRExpansionPlugin/Private/GripMotionControllerComponent.cpp**: In the function `void UGripMotionControllerComponent::GetCurrentProfileTransform(bool bBindToNoticationDelegate)`, the following logic was updated from:
|
||||
|
||||
```cpp
|
||||
if (HandType == EControllerHand::Left || HandType == EControllerHand::AnyHand || !VRSettings->bUseSeperateHandTransforms)
|
||||
{
|
||||
NewControllerProfileTransform = VRSettings->CurrentControllerProfileTransform;
|
||||
}
|
||||
else if (HandType == EControllerHand::Right)
|
||||
{
|
||||
NewControllerProfileTransform = VRSettings->CurrentControllerProfileTransformRight;
|
||||
}
|
||||
```
|
||||
|
||||
To:
|
||||
|
||||
```cpp
|
||||
if (UEnum::GetDisplayValueAsText(HandType).ToString().Contains("Left") || HandType == EControllerHand::AnyHand || !VRSettings->bUseSeperateHandTransforms)
|
||||
{
|
||||
NewControllerProfileTransform = VRSettings->CurrentControllerProfileTransform;
|
||||
}
|
||||
else if (UEnum::GetDisplayValueAsText(HandType).ToString().Contains("Right"))
|
||||
{
|
||||
NewControllerProfileTransform = VRSettings->CurrentControllerProfileTransformRight;
|
||||
}
|
||||
```
|
||||
|
||||
The following function was also updated; from:
|
||||
|
||||
```cpp
|
||||
void UGripMotionControllerComponent::GetHandType(EControllerHand& Hand)
|
||||
{
|
||||
if (!IMotionController::GetHandEnumForSourceName(MotionSource, Hand))
|
||||
{
|
||||
// Check if the palm motion source extension is being used
|
||||
// I assume eventually epic will handle this case
|
||||
if (MotionSource.Compare(FName(TEXT("RightPalm"))) == 0 || MotionSource.Compare(FName(TEXT("RightWrist"))) == 0)
|
||||
{
|
||||
Hand = EControllerHand::Right;
|
||||
}
|
||||
// Could skip this and default to left now but would rather check
|
||||
else if (MotionSource.Compare(FName(TEXT("LeftPalm"))) == 0 || MotionSource.Compare(FName(TEXT("LeftWrist"))) == 0)
|
||||
{
|
||||
Hand = EControllerHand::Left;
|
||||
}
|
||||
else
|
||||
{
|
||||
Hand = EControllerHand::Left;
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
To:
|
||||
|
||||
```cpp
|
||||
void UGripMotionControllerComponent::GetHandType(EControllerHand& Hand)
|
||||
{
|
||||
if (!IMotionController::GetHandEnumForSourceName(MotionSource, Hand))
|
||||
{
|
||||
// Check if the palm motion source extension is being used
|
||||
// I assume eventually epic will handle this case
|
||||
if (MotionSource.Compare(FName(TEXT("RightPalm"))) == 0 || MotionSource.Compare(FName(TEXT("RightWrist"))) == 0 || MotionSource.ToString().Contains("Right"))
|
||||
{
|
||||
Hand = EControllerHand::Right;
|
||||
}
|
||||
// Could skip this and default to left now but would rather check
|
||||
else if (MotionSource.Compare(FName(TEXT("LeftPalm"))) == 0 || MotionSource.Compare(FName(TEXT("LeftWrist"))) == 0 || MotionSource.ToString().Contains("Left"))
|
||||
{
|
||||
Hand = EControllerHand::Left;
|
||||
}
|
||||
else
|
||||
{
|
||||
Hand = EControllerHand::Left;
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
#### Changing Wrist-Tracker Offsets
|
||||
|
||||
If you are using wrist-tracking hardware supported by the SenseGlove plugin, you can change the offsets inside `BP_VRCharacter` using the uproperty `Tracking Offset` typing or copying any of the following, depending on your hardware:
|
||||
|
||||
- **SenseGlove_Quest3**: The wrist-tracking controller profile for for Meta Quest3.
|
||||
|
||||
- **SenseGlove_ViveWristTrackers**: The wrist-tracking controller profile for HTC VIVE wrist trackers.
|
||||
|
||||
#### Changing Motion Source
|
||||
|
||||
In `BP_VRCharacter`, you can change the wrist-tracking motion source for each hand. This is required depending on which tracker you are using.
|
||||
|
||||
#### Adding More Gestures
|
||||
|
||||
In the `GraspingHandManny` Blueprint, we’ve created a simple function called `SaveHandPose`. If you press the `Space Bar` while the game is running, it will save the current pose of the corresponding hand. The pose is stored in a gestures database located under `Content/SenseGlove` with the default name `NewHandPose`. You should rename the pose to something meaningful when you intend to use it.
|
||||
|
||||
It’s helpful to add an Event Dispatcher to the `GraspingHandManny` Blueprint, which is triggered in the Event Graph by the `On New Gesture Detected` event from the `OpenXRHandPose` component. This system is index-based rather than name-based, so keep that in mind when adding more dispatchers. By default, we’ve included examples for `Teleport`, `Grab`, `Release`, and `Use`.
|
||||
|
||||
#### Video Summary
|
||||
|
||||
This short video provides an overview of some of the key changes and modifications behind the SGVRETemplate demo scene, mentioned above.
|
||||
|
||||
<div style="margin: 0 auto; width: 560px;">
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/6uTu4T10mjU" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
### SGVRETemplate Demo Calibration Scene
|
||||
|
||||
The SGVRETemplate includes a basic Calibration Scene located at `Content/SenseGlove/Maps/Calibration`. Inside this level, you’ll find a copy of `Content/SenseGlove/Blueprints/Calibration/BP_Calibrator` Blueprint responsible for transitioning to your desired target map after the calibration process is complete. You can configure the target map directly within this Blueprint by adjusting the `Level to Load` uproperty.
|
||||
@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
|
||||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
||||
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
||||
|
||||
## [2.6.3] - 2025-06-27
|
||||
|
||||
This patch release contains no changes to the plugin code. It includes only documentation updates and improvements.
|
||||
|
||||
### Documentation
|
||||
|
||||
- Added a new section to the handbook titled [Third-Party OpenXR Integrations](../advanced-topics/openxr/third-party-integrations/) section.
|
||||
- Additional minor fixes and improvements that may not be listed here.
|
||||
|
||||
## [2.6.2] - 2025-06-10
|
||||
|
||||
This patch release contains no changes to the plugin code. It includes only documentation updates and improvements.
|
||||
|
||||
### Documentation
|
||||
|
||||
- Added [a third-party tutorial to the Optimizing Your Project for Higher FPS](../misc/optimize-higher-fps/third-party-tutorials/) section.
|
||||
|
||||
## [2.6.1] - 2025-06-05
|
||||
|
||||
This patch release addresses several critical build and linking issues.
|
||||
|
||||
@@ -9,9 +9,10 @@ There are various resources available for older versions of the SenseGlove Unrea
|
||||
- [Example C++ API Project (only compatible with early v1.x.x releases)](https://dev.azure.com/SenseGlove/_git/SenseGlove-Unreal-SGPlaygroundCpp)
|
||||
- [Example Blueprint API Project (only compatible with early v1.x.x releases)](https://dev.azure.com/SenseGlove/_git/SenseGlove-Unreal-SGPlaygroundBP)
|
||||
|
||||
### OpenXR Integration Demos
|
||||
### Third-Party OpenXR Integration Demos
|
||||
|
||||
- [A VRExpansionPlugin Integration Demo for UE `5.4`](https://dev.azure.com/SenseGlove/_git/SGVRETemplate)
|
||||
- [Documentation](../advanced-topics/openxr/third-party-integrations/)
|
||||
|
||||
## Tutorials
|
||||
|
||||
@@ -43,3 +44,7 @@ There are various resources available for older versions of the SenseGlove Unrea
|
||||
|
||||
- [Build & Deploy Unreal Engine 5.5 Projects APK to Android & Meta Quest 3S/3/Pro/2 in Standalone Mode](https://youtu.be/EClbEbNcl4k)
|
||||
- [Unreal Engine OpenXR Hand-Tracking on Android with Meta XR (Quest 3S/3/Pro/2) and HTC VIVE OpenXR (Focus Vision/XR Elite/Focus 3) Plugins](https://youtu.be/BWd3MwtfTJE)
|
||||
|
||||
### VR Optimization
|
||||
|
||||
- [Optimizing Unreal Engine VR Projects for Higher Framerates (Meta Quest, HTC VIVE, FFR, ETFR, NVIDIA DLSS, AMD FSR, and Intel XeSS Tips Included!)](https://youtu.be/67CZqMrAOns)
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
|
||||
| | **Windows (MSVC 2017)** | **Windows (MSVC 2019)** | **Windows (MSVC 2022)** | **Linux x86-64 (Native Toolchain)** | **Linux AArch64 (Native Toolchain)** | **Meta Quest Standalone (Android NDK)** | **HTC VIVE Standalone (Android NDK)** | **Fab** | **Azure DevOps Version** |
|
||||
|:--------:|-------------------------|-------------------------|-------------------------|:-----------------------------------:|:------------------------------------:|:---------------------------------------:|:-------------------------------------:|:--------:|:------------------------:|
|
||||
| **5.6** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ❓ | ✅ v2.6.1 | ✅ v2.6.1 |
|
||||
| **5.5** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ❓ | ✅ v2.6.1 | ✅ v2.6.1 |
|
||||
| **5.4** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ✅ v2.6.x (r25b) | ✅ v2.6.1 | ✅ v2.6.1 |
|
||||
| **5.3** | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ✅ v2.6.x (r25b) | ✅ v2.6.1 | ✅ v2.6.1 |
|
||||
| **5.6** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ❓ | ✅ v2.6.3 | ✅ v2.6.3 |
|
||||
| **5.5** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ❓ | ✅ v2.6.3 | ✅ v2.6.3 |
|
||||
| **5.4** | ❌ | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ✅ v2.6.x (r25b) | ✅ v2.6.3 | ✅ v2.6.3 |
|
||||
| **5.3** | ❌ | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x | ✅ v2.6.x (r25b) | ✅ v2.6.x (r25b) | ✅ v2.6.3 | ✅ v2.6.3 |
|
||||
| **5.2** | ❌ | ⚠️ v2.4.x | ⚠️ v2.4.x | ⚠️ v2.4.x | ⚠️ v2.4.x | ⚠️ v2.4.x (r25b) | ❓ | ⚠️ v2.4.2 | ⚠️ v2.4.2 |
|
||||
| **5.1** | ❌ | ⚠️ v2.0.x | ⚠️ v2.0.x | ⚠️ v2.0.x | ⚠️ v2.0.x | ⚠️ v2.0.x (r25b) | ❓ | ⚠️ v2.0.0 | ⚠️ v2.0.2 |
|
||||
| **5.0** | ❌ | ⚠️ v1.6.x | ⚠️ v1.6.x | ⚠️ v1.6.x | ⚠️ v1.6.x | ⚠️ v1.6.x (r21e) | ❓ | ⚠️ v1.6.1 | ⚠️ v1.6.1 |
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
# Third-Party Tutorials: Optimizing Your Project for Higher FPS
|
||||
|
||||
## Optimizing Unreal Engine VR Projects for Higher Framerates (Meta Quest, HTC VIVE, FFR, ETFR, NVIDIA DLSS, AMD FSR, and Intel XeSS Tips Included!)
|
||||
|
||||
This beginner-friendly tutorial, covers how to significantly boost the performance of your Unreal Engine VR projects, whether you're building for standalone (mobile) or PCVR (desktop) on devices such as Meta Quest, HTC VIVE, Varjo, or Valve Index.
|
||||
|
||||
It covers step-by-step how to:
|
||||
|
||||
- Convert a regular project into a VR-ready experience.
|
||||
- Optimize for both standalone (Android) and PCVR (Windows) platforms.
|
||||
- Tweak key rendering, lighting, and texture settings for smoother gameplay.
|
||||
- Configure Meta XR and HTC VIVE OpenXR plugins to fine-tune settings for the best performance possible.
|
||||
- Utilize and fine-tune engine scalability settings.
|
||||
- Explore powerful optimization features like DLSS, FSR, XeSS, and Foveated Rendering
|
||||
|
||||
Even if you’re new to VR development, this guide breaks it down with visuals, clear examples, and actionable tips to take your framerate from sluggish to silky smooth.
|
||||
|
||||
<div style="margin: 0 auto; width: 560px;">
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/67CZqMrAOns" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
@@ -68,6 +68,7 @@ Toipcs that do not fall under any specific category:
|
||||
- [Third-Party Tutorials](../misc/android-standalone-deployment/third-party-tutorials/)
|
||||
- [Upgrade Guide](../misc/upgrade-guide/)
|
||||
- [Optimizing for Higher FPS](../misc/optimize-higher-fps/)
|
||||
- [Third-Party Tutorials](../misc/optimize-higher-fps/third-party-tutorials/)
|
||||
|
||||
## 🛠️ Advanced Topics
|
||||
|
||||
@@ -81,6 +82,7 @@ For users familiar with the basics, this section explores advanced features of t
|
||||
- [Consuming FXRMotionControllerData](../advanced-topics/openxr/consuming-fxrmotioncontrollerdata/)
|
||||
- [Blueprint](../advanced-topics/openxr/consuming-fxrmotioncontrollerdata/blueprint.md)
|
||||
- [C++](../advanced-topics/openxr/consuming-fxrmotioncontrollerdata/cpp.md)
|
||||
- [Third-Party Integrations](../advanced-topics/openxr/third-party-integrations/)
|
||||
- [Third-Party Tutorials](../advanced-topics/openxr/third-party-tutorials/)
|
||||
|
||||
## 🔌 Low-Level API
|
||||
|
||||
+1
-1
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"FileVersion": 3,
|
||||
"Version": 1,
|
||||
"VersionName": "2.6.1",
|
||||
"VersionName": "2.6.3",
|
||||
"FriendlyName": "SenseGlove",
|
||||
"Description": "Integrating the SenseGlove haptic controller into Unreal Engine",
|
||||
"Category": "Virtual Reality",
|
||||
|
||||
Reference in New Issue
Block a user