Steps to reproduce:

1. This issue was found testing the 6000.0 openxr_samples_android samples generated on the 1.17.0 release candidate PR  [main] Update package version to 1.17.0-pre.1 by github-actions[bot] · Pull Request #1593 · unity/xr.sdk.openxr
2. Through the PR you obtain the .zipped samples here - #60876676 - Build Samples Android 6000.0 NoPlayers (main-version-update-1.17.0-pre.1).
3. Deploy and run the "OpenXR LatencyOptimization arm64_gles3" Android sample to a Quest HMD (I used Quest 3)

Actual results: 

"OpenXR LatencyOptimization arm64_gles3" Android sample FAIL due to rendering issue with the balls that act as hands in the sample - slack thread with video here.

Expected results: 

During the last OpenXR release (1.16.1) this sample looked / behaved fine. This rendering glitches seen in the video I attached in the shiproom slack threadhttps://unity.slack.com/archives/C07K1NSHZA9/p1766171525505079 is a new regression in that OpenXR  sample.

Reproducible with versions: 

OpenXR package 1.17.0-pre.1 - samples built with 6000.0.64f1

Not reproducible with versions: 

Did not reproduce in OpenXR package1.16.1 - samples 6000.2 samples testing performed with that release.

Can’t test with versions: 

Have not yet tested with other versions of OpenXR or editor combinations. This issue could be bisected / tested with further editor & OpenXR combinations to try and pinpoint a specific change for root cause, and the scope of the problem - if it happens across all current editor versions besides 6000.0.64f1.

Tested on (OS): 

Windows 11

Notes:

• I had to choose 1.16.1 - OpenXR Plugin as the Affects Versions field - 1.17.0 is not in the list yet.