PTC v63 Release Thread
Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v62 and the solutions for some have shipped, while others are on the way! The Public Test Channel (PTC) for Quest v63 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. If you're seeing an issue or bug after updating to PTC v63 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v63" to the thread and in the title. This way everyone can look for just PTC v63 issues too. It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!182KViews41likes321CommentsConflict with ManualResetValueTaskSourceCore<TResult> in latest Oculus XR SDK (com.meta.xr.sdk.core)
I'm encountering a type conflict error ("CS0433 The type 'ManualResetValueTaskSourceCore<TResult>' exists in both...") when using the latest version of the Oculus XR SDK package (com.meta.xr.sdk.core). This conflict seems to be between the Oculus SDK's internal use of ManualResetValueTaskSourceCore<TResult> and the version provided by the .NET framework (or another package). What I've Tried: I've ensured I'm using the latest version of the com.meta.xr.sdk.core package through the Unity Package Manager. I attempted to resolve the conflict by adding a compiler argument specifying the location of the desired Microsoft.Bcl.AsyncInterfaces.dll file within Unity project preferences, but it didn't work. I've explored alternative solutions like namespace aliasing, but unfortunately, modifying the Oculus SDK files directly is not an option as it's a package managed by Unity. I also tried the solution as mentioned in this thread, which solves the error in the editor, but upon APK build it breaks and spits out the same error again. Impact on Builds: This conflict with ManualResetValueTaskSourceCore<TResult> prevents successful builds within Unity. The error message "CS0433: The type 'ManualResetValueTaskSourceCore<TResult>' exists in both..." halts the build process entirely. Someone please help solve this issue... I believe it may be a bug in the most recent SDK release. Thanks!Solved2.6KViews1like5CommentsRecent Oculus v63 update generates warnings in Unreal about dbgeng.dll / StackWalk2
Using Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361) we are now seeing repeated warnings when loading an Unreal application (or even just the Unreal Editor). The Unreal application copies a version of dbghelp.dll across to the ThirdParty binaries folder, but this was always the case, and the warnings did not appear before the Oculus update. If the Oculus app is uninstalled, these warnings do not appear. Are any Oculus developers looking into this? Thanks. Possibly related to https://communityforums.atmeta.com/t5/OpenXR-Development/OpenXR-hand-body-tracking-extensions-not-working-over-AirLink-in/m-p/1155017#M7256.4KViews5likes23CommentsMake your voices heard and save modding!
The latest public test channel update PTC V63 locks scoped storage meaning those who mod games like bonelab will be unable to manually mod their games. While some games are starting to work on built in mod managers it still doesn't make meta locking scoped storage okay! Worst thing is multiple games have experienced save data loss. I stand with modders and the dev of mobile vr station against this update. Please for the sake of all modders far and wide stand up and make your voices heard! Show meta your unhappy with this update rather it be posting your anger on twitter facebook or anything else. Do something because if this update rolls out with this feature still preventing people from modding. then it may aswell be the end of modding all together.623Views1like0Comments