Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Movement SDK Sample - Livelink Skelmesh Jittery/Inconsistent #3

Open
fisj opened this issue May 23, 2024 · 1 comment
Open

Movement SDK Sample - Livelink Skelmesh Jittery/Inconsistent #3

fisj opened this issue May 23, 2024 · 1 comment

Comments

@fisj
Copy link

fisj commented May 23, 2024

I'm testing the movement sample, and have noticed the Skelmesh movement is jittery and inconsistent on Quest3. Not just a little, but enough to cause discomfort. As it stands this feature is not usable.

  • Its not a framerate issue. Framerate in my tests is solid 72fps.
  • I've restarted my Quest3
  • I have v65 of the UnrealMetaXRPlugin and UnrealPlatformSDKPlugin, Vanilla Unreal 5.3.2. Quest OS v65
  • I've tested someone else's APK built from the movement sample. Same skelmesh jitter/inconsistency
  • I've built my own version of livelink body retargeting (via the docs) and see the same issue, even more pronounced, even.
  • It happens on all characters in the sample.

I decided to take a closer peek at the raw transform data coming from the livelink, by drawing the joints as instanced static meshes and found the livelink data itself is jittery and choppy. In contrast, the joints from the OculusXRBodyState are smooth and flawless.

image

Also posted to forums about this:
https://communityforums.atmeta.com/t5/Unreal-VR-Development/Movement-SDK-Sample-Livelink-Skelmesh-Jittery-Inconsistent/td-p/1196607

@0xGhost
Copy link

0xGhost commented Nov 4, 2024

Hi, I noticed the movement SDK update rate dropped to almost one frame per second after I removed my headset and put it back on. I am using MetaXRPlugin v64 and Unreal 5.3.2. Have you found any solution to this issue? Or is this an issue that only appears in Unreal 5.3.2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants