I’m experiencing the same with the latest 1.19.9, not as much with the prior version. The latest WMR/OXR Dev Preview seems a little better as well than the prior dev preview regarding this.
Usually when these are happening it is most likely the motion smoothing is taking just too much enough, in addition to the frame render time, to overflow the threshold (44ms / 22.5fps) and cause a hiccup. The next frame, motion smoothing will be disabled and there will be enough render time but it will show without motion smoothing. The next frame, motion smoothing will kick in again and overflow etc… until both render time + motion smoothing time stabilize under 44ms again.
There doesn’t seem to be any setting you can tune for adjusting the threshold detection logic, except a few registry values whose names are telling they might be related but I’ve not experimented with:
-
Is this one allowing to motion smooth more than 4:1 in WMR (like up to 6:1 with SteamVR)?
.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Spectrum\HeadPredictionAmountFrames -
Otherwise these are most likely for 2D full screen WDM compositor:
.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm\ExtendedComposition\ExclusiveModeFramerateAveragingPeriodMs
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm\ExtendedComposition\ExclusiveModeFramerateThresholdPercent
PS: I concur SteamVR OXR → WMR for SteamVR is not better than WMR OXR directly now (but it used to be!)
PS: the most impactful setting when you’re at the motion smoothing threshold is Clouds. Just going from HIGH->MED or MED->LOW changes a lot the experience (both in terms of motion smoothing but unfortunately visually as well). This is usually the first one I change and with my settings on my test system, nearly the only one I have to change on ground, which I can revert back once airborne.