UE5.3: Roomscale and stationary boundaries break my Player Start! Why?
Hello, I'm having some strange problems. While I try out my test level with the Meta Quest at my workplace and in the Unreal Engine, everything works fine. Now I have created an APK file and installed it on the quest and have the following problem (see also the picture): 1. in the editor "PlayerStart" is at the position and rotation as shown in the picture (see number 1 in the picture). This also works when I test it in the engine and with Meta Quest. 2. However, if I start the level natively on the quest (at a different place in my room), then I start somewhere else in the level and not at the set "PlayerStart" (see number 2 in the picture). And my triggers etc. no longer work. If I reset the position ingame (via menu button), then the player jumps back to the spawnpoint set in the editor (see number 3 in the picture), but the triggers etc. do not work either. If I start the "game" on my workplace, then the spawn position is correct and everything else also works. The spawn point should always be the same, no matter where I start the game from. I don't know why this won't work. New Update: I have found that when I have a stationary boundary (3x3 feet), it works as it should. But as soon as I set Roomscale (or when I am standing), I have the behavior as described above. I'm trying to create a game like "Moss", for example. I have a stationary VR character (first person) where I can interact with my hands and at the same time I control a 3rd person character. And with triggers etc. I then "teleport" the VR character to a different position. This works, but not as soon as I stand or activate Roomscale. And if I'm not in the center of the stationary boundary, then the rotation and position where I "teleport" the VR character is no longer correct. Does anyone have any idea?
Meta Movement Package: Code error in RetargetingLayer.cs [fixed]
I installed Meta's Movement package and immediately hit an error: Library\PackageCache\com.meta.movement@3224be0f12\Runtime\Scripts\AnimationRigging\RetargetingLayer.cs(329,33): error CS0115: 'RetargetingLayer.InitializeBindPose()': no suitable method found to override FWIW, I'm running Unity 2022.3.33f1 on Android, package version is 6.0.0, and I imported the project via git in the package manager: `https://github.com/oculus-samples/Unity-Movement.git` UPDATE Resolved: I upgraded Meta XR Core SDK from 65.0.0 to 68.0.2 😅 Note to self: RTFM
Which input system to use with Movement SDK
I'd like to experiment with the Movement SDK. The readme indicates Oculus Integration is a prerequisite.and that package uses the new input system (UnityEngine.InputSystem). The Movement SDK, however, is uses the old input system (UnityEngine.Input). Which system should I use?Walking through walls in VR with Oculus Integration Package and XR Toolkit combination setup
Hello all, I am trying to use a combination of the XR Ray Interactor to interact with UI and the Oculus Custom hands to grab objects.. When I use the XROrigin with ray interactor and XR Grab Interactable I am to view the ray as well as grab objects (very laggy/glitchy though).. One major issue with the XROrigin setup is that they movement in VR is passing thorough the environments walls and objects.. I have tried applying Physics by adding Rigidbody components but it isn't very smooth and it is slightly uncomfortable when viewing in the headset.. So I am trying to use the OVRPlayerController with OVRGrab functionality as well as the XR Ray Interactor but the rays don't show up. I am not sure If I am missing anything.. any help on this would be very much appreciated... Thanks in Advance Platform: Android Unity version: 2020.3.27f1 XR Toolkit Version: 2.0.1 Oculus Integration Package version: 37.0
