SteamVR, Valve Index, 1080Ti, NVidia driver.. err
(checks) 536.23: No ghosting.
What seems odd, is that it only affects one isolated graphical element, and not the whole screen; Otherwise one might have suspected tracking-, or reprojection issues.
I have previously (...only in Elite Dangerous...) seen the whole screen do this... hmm... let's call it... uhm..: "temporally jumbled interleaved frames" juddering thing, when using a widescreen Pimax headset, and pretty high render resolution... Not sure whether to attribute that to the low frame rate wreaking havoc with motion prediction; Dodgy tracking on Pimax's part; Elite's apparent
own keeping track of the player's head -- relative-, apart-, and sourced-but-disconnected from the absolute room-tracking of the VR runtime; Or any combination thereof...
...although, I kind of suspect one performance trick that might be used by the game, could be spreading subdivisions of jobs, beyond what you might expect, out over several frames; Some of you may remember during Odyssey beta, how the jump assist pack rocket flames would draw at a position several frames behind the backpack itself, disconnecting them from it, which looked rather silly. :7
I am wondering if similar things could be responsible for the occasional sets of objects sitting sunk into the floors and walls in orbital stations and outposts; Like if coordinate origins for groups of objects and colliders were taken from the same moving parent, but from subsequent frames, instead of sharing one snapshot, and not getting the translation/transformation deltas right for some reason, possibly exacerbated by floating point precision limitations...
