Search Issue Tracker
Fixed
Fixed in 3.2.0
Votes
0
Found in [Package]
3.0.7
3.1.1
3.2.0-pre.1
Issue ID
XRIT-255
Regression
Yes
Initial camera position is logged in "TeleportationProvider_endLocomotion" when teleporting
Reproduction steps:
1. Open the attached project “ReproProject“
2. Open scene “Sample/XR Interaction Toolkit/3.1.1/Starter Assets/DemoScene.unity“
3. Make sure VR headset is connected
4. Enter Play Mode
5. Using the controller’s right stick, target a teleport position somewhere
6. Release right stick to teleport to the marked location
7. Observe the result in the Console
Expected result: The first log (TeleportationProvider_startLocomotion) shows the initial position of the camera before teleportation occured. The second log (TeleportationProvider_endLocomotion) shows the camera position after the teleportation occured
Actual result: The two logs display the same camera position (before teleportation)
Reproducible in: 3.0.0-pre.1 (2023.3.0a19), 3.1.1 (2022.3.60, 6000.0.43f1, 6000.1.0b12, 6000.2.0a7)
Not reproducible in: 2.6.4 (2023.3.0a19, 2022.3.60f1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 3.2.0):
Changed the timing of when several locomotion events and methods are called within a frame. The primary motivation of these changes is to allow the `LocomotionProvider.locomotionEnded` event to invoke after a teleport has actually been applied to the XR Origin rather than after the transformation has merely been queued but not yet applied. This restores similar timing to that event as the deprecated `LocomotionProvider.endLocomotion` when the deprecated `LocomotionSystem` was used, fixing a regression introduced with version 3.0.0-pre.1