diff options
| author | Peter Kim <pk15950@gmail.com> | 2022-06-17 11:25:48 +0300 |
|---|---|---|
| committer | Peter Kim <pk15950@gmail.com> | 2022-06-17 11:25:48 +0300 |
| commit | 10981bc8c092dda48ed5228cc19108513035abf0 (patch) | |
| tree | edf643f5ad5d9b36af9e163e68981e42ae3fbbf0 /source/blender/nodes/geometry/nodes/node_geo_rotate_instances.cc | |
| parent | 18960c08fde76dcd839e323d60b5775101229937 (diff) | |
Fix T98944: Uninitialized XRFrameState can prevent VR/OpenXR viewing
This provides a workaround for the VR session stopping due to an error
in locating controller poses. The problem was that for the actions sync
on the first frame, the session's XrFrameState/predicted display time
had not been initialized yet, which led to an error in xrLocateSpace()
(the error was only observed for some OpenXR runtimes since the first
frame pose state would be inactive for other runtimes, skipping the
call to xrLocateSpace()).
The timing of action updates relative to frame state updates could be
reworked in the future, but for now simply check for a valid display
time to avoid an error on the first frame.
Diffstat (limited to 'source/blender/nodes/geometry/nodes/node_geo_rotate_instances.cc')
0 files changed, 0 insertions, 0 deletions