Android SDK 12l causing crashing for development builds
Recently I've been trying to update my project's android api from 29 to 32, so it can comply with the new requirements for Quest 2. After the update attempting to launch a non-distribution build causes the following crash during the initial splash screen: Initially I thought this was down to lack of permissions. MANAGE_EXTERNAL_STORAGE was added in api 30 without which access to $Storage/obb, where non-distribution obbs are stored on device, would have been denied. However adding this to the extra permissions and ensuring it has been requested on game start has not fixed the issue. Below are the android packaging settings. I also tried editing the automation script to have the obbs appear in the $storage/android/obb folder, while this did fix the initial crashing it lead to other side effects (such as no logs being recorded and instability) & ultimately feels like a step in the wrong direction. Has there been anyone else run into this issue? If so did you find a solution? Any suggestions or troubleshooting thoughts would be deeply appreciated.
Get Motion Controller Data lags behind when actor is moving
I have discovered a bug when using the "Get Motion Controller Data" function. I am using Unreal Engine version 4.27.0. I have yet to test this in the latest version of the engine. The bug occurs when moving the actor around. The data found in XRMotionControllerData which is given by the function "Get Motion Controller Data" gives position and rotation data for the motion controllers which doesn't seem to be up to date with exactly where the actor has moved. In my testing project, I added code which simply draws this data as a red beam. I also added code which moves the actor. The red beam and the teleport beam both appear to be lagging behind the actor. The bug also occurs when rotating the actor. It does not occur when moving the motion controller around, it only seems to occur when moving the actor around. When using the location and forward vector of the MotionControllerComponent World Location as a scene component, the issue does not occur. All of these effects have been observed both from VR Preview via oculus link with the Quest 2, and a version launched to the Quest 2. I have verified this in a fresh VR Template project. The bug is present without any modifications. Here's a drive folder with some recordings of the issue, and some screenshots of some code. The videos are labeled with what's happening, and in what environment. https://drive.google.com/drive/folders/17ExfnqBW2rH_rx2OSSZfiqHlOupmeeTz?usp=sharing
