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?
Unreal 5.3.2 OculusXRInput crash caused by haptics
Hey, I've been having an issue with using haptics. I upgraded from unreal 5.1 to 5.3.2 and updated the MetaXR integration package to V60.0. After the upgrade, using "Set Haptics By Value" or "Play Curve Haptic Effect" both cause a crash in Editor and in the Meta Quest 2&3. When removing these from my BP, the crash does not occur. Did something change to the haptic functionality? Am i missing something? Sincerely, Raymond
Still Don't See Hands in any versions of Unreal, What Am I missing? 5.3 using updated metaxr plugin.
1. set up developer account and turn on all the developer stuff 2. download and add metaxr to engine 5.3 3. Create a VR Template 4. make sure metaxr plugin is on ( if openxr is on or off, it doesn't make a difference I think ) 5. in settings, meta xr, make sure Hand Tracking Support is set to Crontrollers and Hands or just Hands 6. create a new BP_VRPawn 7. add a camera, motioncontrollers and oculusXRHands while making sure both skelton and mesh type are set to hand left or hand right accordingly 8. change game mode default pawn class to BP_VRPawn after doing all this, i get the same result as I do using quest link desktop - no hands but I see the palm buttons and everything tracks accordingly. Where are my hand meshes? this is the error i get LogOVRPlugin: Error: [XRCMD][failure] [XR_ERROR_HANDLE_INVALID]: xrGetHandMeshFB(handTracker, &xrMesh), arvr\projects\integrations\OVRPlugin\Src\Util\CompositorOpenXR.cpp:7513 (arvr\projects\integrations\OVRPlugin\Src\Util\CompositorOpenXR.h:315)
