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
- Typos in High Definition 3D sample tutorials
- “Handles.Repaint called outside an editor OnGUI" error is thrown in the Console when creating a new Tile Palette from the Tile Palette Overlay in Scene view
- Shader Graph window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
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